incubator-any23-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Companjen (Commented) (JIRA)" <>
Subject [jira] [Commented] (ANY23-65) Update to RDFa extraction stylesheet
Date Sat, 24 Mar 2012 15:34:25 GMT


Ben Companjen commented on ANY23-65:

Well, this is kind of embarrassing... I just had another look at the RDFa Core 1.1 doc and
saw that the CURIES are defined without spaces. That would mean the examples are wrong and
all the work I did was to support the wrong examples :S

It still works of course. I emailed two of the editors of the doc with my findings, so hopefully
it will be updated.
> Update to RDFa extraction stylesheet
> ------------------------------------
>                 Key: ANY23-65
>                 URL:
>             Project: Apache Any23
>          Issue Type: Improvement
>    Affects Versions: 0.7.0
>            Reporter: Ben Companjen
>              Labels: patch, xslt
>         Attachments: rdfa.xslt, stylesheet.patch, stylesheet3.patch
>   Original Estimate: 3h
>  Remaining Estimate: 3h
> The RDFa 1.1 Core specification requests namespace prefixes in HTML5 be put in a "prefix"
attribute like this: "ns1: ns2:"
> My sample HTML page has this, but Sindice, which uses Any23, didn't read my namespace
correctly. I narrowed it down to, and changed accordingly, the XSLT template "tokenize2" in
the rdfa.xslt stylesheet. The template expected "ns1: ns2:"
(no spaces between prefix and namespace URI) and did not normalize whitespace, like linebreaks
(although I'm not sure that broke the functionality).
> I use Any23 0.6.1 locally, but
shows that the template is the same in the trunk.
> A possible problem may be that the new template will not accept the non-spaced namespace
definitions, like you can find in the RDFa produced by Best Buy. A further improvement to
my template may be accepting both namespace definitions with spaces and the ones without.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message