This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6902 - Note incompatibilities with RDF serializations
Summary: Note incompatibilities with RDF serializations
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NoReply
Depends on:
Reported: 2009-05-13 10:21 UTC by Henri Sivonen
Modified: 2010-10-04 14:47 UTC (History)
4 users (show)

See Also:


Description Henri Sivonen 2009-05-13 10:21:12 UTC
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:

Please note or make non-conforming property names that can't be serialized even as N-Triples/N3/Turtle. These include at least ">".
Comment 1 Laurens Holst 2009-05-13 15:50:25 UTC

CURIEs were invented to avoid this issue.
Comment 2 Henri Sivonen 2009-05-14 06:37:23 UTC
How could CURIEs expand the range of properties serializable in RDF/XML?
Comment 3 Laurens Holst 2009-05-14 12:40:05 UTC
They dont, they expand the range of properties serialisable in RDFa; originally RDFa used QNames, like RDF/XML.
Comment 4 Ian 'Hixie' Hickson 2009-06-02 00:40:34 UTC
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.
Comment 5 Maciej Stachowiak 2010-03-14 14:48:09 UTC
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:

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.