[
https://issues.apache.org/jira/browse/ANY23-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932896#comment-16932896
]
Lewis John McGibbney commented on ANY23-428:
--------------------------------------------
Hi [~davidcockbill]
bq. I'll need some advice on how to proceed. Presumably creating an issue on
the semarglproject, getting that fixed and merged, getting a new release, then
pulling in the new version into ANY23?
Yes that's how I would go ahead. I do however think that semargl intends to be
very strict with this type of thing so they might suggest that the fix happens
elsewhere... we will see. If you could, please cross post the semargl issue
link here once it exists. Thank you
> RDFa parse issue if vocab not defined with training slash
> ---------------------------------------------------------
>
> Key: ANY23-428
> URL: https://issues.apache.org/jira/browse/ANY23-428
> Project: Apache Any23
> Issue Type: Bug
> Components: extractors
> Affects Versions: 2.3
> Reporter: David Cockbill
> Priority: Minor
>
> If a RDFa vocab URL is missing a trailing forward slash, then the properties
> are not expanded correctly.
> For example:
>
> {code:java}
> <ol vocab="https://schema.org"; typeof="BreadcrumbList">
> {code}
> rather than:
>
> {code:java}
> <ol vocab="https://schema.org/"; typeof="BreadcrumbList">
> {code}
> produces properties that look (in nTriples) as follows:
>
>
> {code:java}
> <http://example.com> <http://www.w3.org/ns/rdfa#usesVocabulary>
> <http://schema.org> .
> _:n0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type>
> <http://schema.orgBreadcrumbList> .
> _:n1 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type>
> <http://schema.orgListItem> .
> {code}
>
>
> I'm sure the intention should be to join the properties and vocab with a
> forward slash.
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
