[
https://issues.apache.org/jira/browse/ANY23-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17070598#comment-17070598
]
Hudson commented on ANY23-428:
------------------------------
SUCCESS: Integrated in Jenkins build Any23-trunk #1681 (See
[https://builds.apache.org/job/Any23-trunk/1681/])
ANY23-428 resolve rdfa vocabs more intelligently (hans: rev
6ee5d2485b28d3c92ac581620411259812b11c20)
* (edit)
core/src/test/java/org/apache/any23/extractor/rdfa/RDFa11ExtractorTest.java
* (add)
test-resources/src/test/resources/html/rdfa/vocab-without-trailing-slash.html
* (edit) core/src/main/java/org/apache/any23/extractor/rdfa/JsoupScanner.java
> RDFa parse issue if vocab not defined with trailing 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
> Assignee: Hans Brende
> Priority: Minor
> Fix For: 2.4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
