[Bug 8985] New: Inclear if requirement to ensure namespace well-formed fragments is separate from other transformation requirements

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8985

           Summary: Inclear if requirement to ensure namespace well-formed
                    fragments is separate from other transformation
                    requirements
           Product: HTML WG
           Version: unspecified
          Platform: PC
               URL: http://dev.w3.org/html5/rdfa/#invalid-xmlliteral-values
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML+RDFa (editor: Manu Sporny)
        AssignedTo: msporny@digitalbazaar.com
        ReportedBy: mjs@apple.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html@w3.org,
                    msporny@digitalbazaar.com


4.2Invalid XMLLiteral values

"If the input is not a namespace well-formed XML fragment, the processor must
transform the input text in a way that ensures the well-formedness rules
described in this section. If a sequence of characters cannot be transformed
into a namespace well-formed XML fragment, the triple containing the XMLLiteral
must not be generated.

An RDFa Processor that transforms the XML fragment must use the Coercing an
HTML DOM into an Infoset rules, as specified in the HTML5 specification, prior
to generating the triple containing the XMLLiteral. The serialization algorithm
that must be used for generating the XMLLiteral is normatively defined in the
Serializing XHTML Fragments section of the HTML5 specification."

Are these different ways of stating the same requirement, or a single
requirement? After an RDFa processor applies the "Coercing an HTML DOM into an
Infoset" rules, followed by the "Serializing XHTML Fragments" algorithm, is it
required to do any further transformations? If so, what are they?


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Sunday, 14 February 2010 07:01:52 UTC