ww: sameAs http://unhosted.org/
webr3: URI normalization issue in RDF(a) - see also http://webr3.org/urinorm/html for how your browser does it
webr3: pyRDFa also affected
webr3: and see: http://check.rdfa.info/check?url=http://webr3.org/urinorm/2&version=1.0 also affected
webr3: and see: http://sig.ma/search?q=http://webr3.org/urinorm/2 sigma also affected
webr3: and see http://linkeddata.uriburner.com/about/html/http/webr3.org/urinorm/2%01this URIBurner/virtuoso also affected
webr3: and see http://www.rdfabout.com/demo/validator/ - also affected, also arict all dot net /ms tooling is affected
webr3: basically, anything linked-data related or relying on third party components, or which has to follow your nose is affected by non-normalization
webr3: which by implication means all non-affected RDF implementations are incompatible with all web implementations which do normalize, and the web implementations are out of scope / can't be changed in many cases
webr3: also any HTML view of any RDF with non-normalized URIs is affected, just do <a href="HTTP://EXAMPLE.ORG/"> will produce a value of "http://example.org/"
webr3: nothing major though
DanC_pm: not clear that this is worth bothering over. how often does HTTP://EXAMPLE.ORG/ actually occur?
DanC_pm: and while RDF simple entailment is defined in terms of raw URI string comparison, there's nothing stopping an application from adopting rules from URI and HTTP specs...
DanC_pm: i.e. the URI spec says that HTTP://EXAMPLE.ORG/ owl:sameAs http://EXAMPLE.ORG/
DanC_pm: and the HTTP spec says that http://EXAMPLE.ORG/ owl:sameAs http://example.org/
DanC_pm: (HTTP and DNS, that is)
webr3: RDF, OWL, RIF and SPARQL all say non normalized string comparison - which is the issue, literal string comparison
webr3: pyRDFa also affected
webr3: and see: http://check.rdfa.info/check?url=http://webr3.org/urinorm/2&version=1.0 also affected
webr3: and see: http://sig.ma/search?q=http://webr3.org/urinorm/2 sigma also affected
webr3: and see http://linkeddata.uriburner.com/about/html/http/webr3.org/urinorm/2%01this URIBurner/virtuoso also affected
webr3: and see http://www.rdfabout.com/demo/validator/ - also affected, also arict all dot net /ms tooling is affected
webr3: basically, anything linked-data related or relying on third party components, or which has to follow your nose is affected by non-normalization
webr3: which by implication means all non-affected RDF implementations are incompatible with all web implementations which do normalize, and the web implementations are out of scope / can't be changed in many cases
webr3: also any HTML view of any RDF with non-normalized URIs is affected, just do <a href="HTTP://EXAMPLE.ORG/"> will produce a value of "http://example.org/"
webr3: nothing major though
DanC_pm: not clear that this is worth bothering over. how often does HTTP://EXAMPLE.ORG/ actually occur?
DanC_pm: and while RDF simple entailment is defined in terms of raw URI string comparison, there's nothing stopping an application from adopting rules from URI and HTTP specs...
DanC_pm: i.e. the URI spec says that HTTP://EXAMPLE.ORG/ owl:sameAs http://EXAMPLE.ORG/
DanC_pm: and the HTTP spec says that http://EXAMPLE.ORG/ owl:sameAs http://example.org/
DanC_pm: (HTTP and DNS, that is)
webr3: RDF, OWL, RIF and SPARQL all say non normalized string comparison - which is the issue, literal string comparison