[ https://issues.apache.org/jira/browse/ANY23-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16785045#comment-16785045 ]
Lewis John McGibbney commented on ANY23-428: -------------------------------------------- Yes, you are correct [~davidcockbill] can you provide a pull request and some tests if possible? > 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 (v7.6.3#76005)