6902 2009-05-13 10:21:12 +0000 Note incompatibilities with RDF serializations 2010-10-04 14:47:57 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All VERIFIED FIXED NoReply P2 normal --- 1 hsivonen ian lholst mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 25132 0 hsivonen 2009-05-13 10:21:12 +0000 Please add a note saying that the conversion to RDF algorithm may produce statements that cannot be represented as RDF/XML (but can be represented in N-Triples/N3/Turtle). The issues are: 1) textContent in text/html may contain non-XML characters. 2) a property name may not be splittable into a QName in such a way that the local part is an NCName. See also: http://krijnhoetmer.nl/irc-logs/whatwg/20090512#l-735 Please note or make non-conforming property names that can't be serialized even as N-Triples/N3/Turtle. These include at least ">". 25139 1 lholst 2009-05-13 15:50:25 +0000 http://www.w3.org/TR/rdf-syntax-grammar/#section-Serialising CURIEs were invented to avoid this issue. 25148 2 hsivonen 2009-05-14 06:37:23 +0000 How could CURIEs expand the range of properties serializable in RDF/XML? 25151 3 lholst 2009-05-14 12:40:05 +0000 They don’t, they expand the range of properties serialisable in RDFa; originally RDFa used QNames, like RDF/XML. 25414 4 ian 2009-06-02 00:40:34 +0000 I tried to fix this by just %-escaping the values that go into IRIs, which should fix the n-triples problems. I haven't mentiond XML/RDF because (a) it seems like the RDF community is collectively trying to forget they ever invented RDF/XML, and (b) this is a general limitation of RDF/XML and not related to HTML5 per se. 33106 5 mjs 2010-03-14 14:48:09 +0000 This bug predates the HTML Working Group Decision Policy. If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.