W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2010

[Bug 8987] New: Processing requirements for attributes starting with xmlns: are undefined

From: <bugzilla@wiggum.w3.org>
Date: Sun, 14 Feb 2010 07:14:04 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-8987-2486@http.www.w3.org/Bugs/Public/>

           Summary: Processing requirements for attributes starting with
                    xmlns: are undefined
           Product: HTML WG
           Version: unspecified
          Platform: PC
               URL: http://dev.w3.org/html5/rdfa/#xmlns:-prefixed-attributes
        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,

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:

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

" 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:.

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:14:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:11 UTC