This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
4.3 xmlns:-Prefixed Attributes says: "CURIE prefix mappings specified using attributes prepended with xmlns: must be processed using the rules specified in Section 5.4, CURIE and URI Processing, contained in the XHTML+RDFa specification." However, that section does not appear to define a processing model: http://www.w3.org/TR/rdfa-syntax/#s_curieprocessing Here are all the normative requirements for processors in section 5.4 of XHTML+RDFa and its subsections: "Since CURIE mappings are created by authors via the XML namespace syntax [XMLNS] an RDFa processor MUST take into account the hierarchical nature of prefix declarations." "However, since all URIs must be resolved relative to [base] before being used to create triples, the use of relative paths should not have any effect on processing." " In this case any value that is not a 'curie' according to the definition in the section CURIE Syntax Definition MUST be ignored; this means that not only will there be no error reporting, but also the RDFa processor should act as if the value simply did not exist." "If the value is surrounded by square brackets, then the inner content must conform to the 'curie' definiton, and as before, if it does not then the value MUST be ignored." "As described, any CURIEs expressed in the attribute must follow the format of a [safe CURIE]." " Instead, any value that matches an entry in the list of link types in the section The rel attribute, MUST be treated as if it was a URI within the XHTML vocabulary, and all other values must be CURIEs." "Note that only values in the link type list have this special behaviour, which means that any value that is not in the list and is not a valid CURIE MUST not generate triples in the [default graph] ." "If a subject or object is defined using a CURIE, and that CURIE explicitly names a [bnode], then a conforming parser MUST create the bnode when it is encountered during parsing." "The parser MUST also ensure that no bnodes created automatically (as a result of [chaining]) have names that collide with bnodes that are defined by explicit reference in a CURIE." None of these statements seems to define what specifically should be done with an attribute that starts with xmlns:.
RDFA-SPEC-SECTIONS [xmlns:-prefixed-attributes]
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, 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 Status: Fixed Change Description: Changed the reference to the RDFa Core specification and outlined the algorithm in the HTML+RDFa specification: http://dev.w3.org/cvsweb/html5/rdfa/drafts/ED-rdfa-in-html-20100504/Overview.html.diff?r1=1.3&r2=1.4&f=h """ CURIE prefix mappings specified using attributes prepended with xmlns: must be processed using the algorithm defined in section 4.4.1: Extracting URI Mappings from Infosets for Infoset-based processors, or section 4.5.1: Extracting URI Mappings from DOMs for DOM Level 2-based processors. For CURIE prefix mappings using the prefix attribute, Section 7.5: Sequence, step #4 should be used to process namespace values. """ Rationale: Processing step #2 (in rdfa-syntax) outlines how to process xmlns: values: http://www.w3.org/TR/rdfa-syntax/#sec_5.5. """ Mappings are provided by @xmlns. The value to be mapped is set by the XML namespace prefix, and the value to map is the value of the attributea URI. Note that the URI is not processed in any way; in particular if it is a relative path it is not resolved against the current [base]. Authors are advised to follow best practice for using namespaces, which includes not using relative paths. """ Processing step #4 (in rdfa-core) outlines how to process xmlns: values: http://www.w3.org/TR/rdfa-core/#sequence """ Mappings are defined via @prefix. For backward compatibility, some Host Languages may also permit the definition of mappings via @xmlns. In this case, the value to be mapped is set by the XML namespace prefix, and the value to map is the value of the attribute a URI. Regardless of how the mapping is declared, the value to be mapped must be converted to lower case, and the URI is not processed in any way; in particular if it is a relative path it is not resolved against the current base. Authors should not use relative paths as the URI. """ It has been clarified that the algorithm defined in HTML+RDFa MUST be used for extracting values from xmlns: and the algorithm defined in RDFa Core can be used to extract prefix values from @prefix.
mass-move component to LC1