[Bug 8984] Invalid XMLLiteral definition of namesspace-well-formed XML fragments is too weak

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


Manu Sporny <msporny@digitalbazaar.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED




--- Comment #2 from Manu Sporny <msporny@digitalbazaar.com>  2010-05-04 03:56:28 ---
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: 

Reworded Invalid XMLLiteral values section, bullet item #2:

"""
* The XML fragment, when placed inside of a single root element, must retain
all active namespace information. The currently active attributes declared
using xmlns and xmlns: stored in the RDFa Processor's current evaluation
context in the list of URI mappings must be preserved in the generated
XMLLiteral. The PREFIX value for xmlns:PREFIX must be transformed to all
lower-case characters when preserving the value in the XMLLiteral. All active
namespaces declared via xmlns and xmlns: must be placed in each top-level
element in the generated XMLLiteral, taking care to not overwrite pre-existing
namespace values.
"""

and added an extra example:

"""
Similarly, compound document elements that reside in different namespaces must
have their namespaces declarations preserved:

<p xmlns:ex="http://example.org/vocab#"
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:fb="http://www.facebook.com/2008/fbml">
 This is how you markup a user in FBML:
 <span property="ex:markup" datatype="rdf:XMLLiteral">
&#8594;<p><fb:user uid="12345">The User</fb:user></p>
&#8594;</span>
The markup above should produce the following triple, which preserves the fb
namespace in the corresponding triple:

<>
   <http://example.org/vocab#markup>
      "<p xmlns:fb="http://www.facebook.com/2008/fbml">
&#8594;<fb:user uid="12345">
&#8594;</p>"^^http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral .
"""

Rationale:

The previous text did specify that all namespace declarations should be
preserved on the top-most element, thus ensuring a namespace-well-formed
XMLLiteral. Since the reader missed this, the text has been re-worded to make
this more clear as well as add the requirement that the xmlns prefix value
should be forced to lower-case to ensure compatibility between HTML and XHTML
documents.

-- 
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 Tuesday, 4 May 2010 03:56:31 UTC