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 8985 - Unclear if requirement to ensure namespace well-formed fragments is separate from other transformation requirements
Summary: Unclear if requirement to ensure namespace well-formed fragments is separate ...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML+RDFa (editor: Manu Sporny) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Manu Sporny
QA Contact: HTML WG Bugzilla archive list
URL: http://dev.w3.org/html5/rdfa/#invalid...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-14 07:01 UTC by Maciej Stachowiak
Modified: 2011-08-04 05:06 UTC (History)
4 users (show)

See Also:

Attachments

Description Maciej Stachowiak 2010-02-14 07:01:50 UTC 
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?
Comment 1 Manu Sporny 2010-02-16 04:25:05 UTC 
RDFA-SPEC-SECTIONS [invalid-xmlliteral-values]
Comment 2 Manu Sporny 2010-05-05 01:17:49 UTC 
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: 

Clarified that all that is required to ensure that XMLLiteral values are namespace well-formed is to:

1. Run the "Coercing an HTML DOM into an Infoset" algorithm.
2. Run the "Serializing XHTML Fragments" algorithm.



"""
An RDFa Processor that transforms the XML fragment must use the Coercing an HTML DOM into an Infoset algorithm, as specified in the HTML5 specification, followed by the algorithm defined in the Serializing XHTML Fragments section of the HTML5 specification. If an error or exception occurs at any point during the transformation, the triple containing the XMLLiteral must not be generated.
"""

Rationale:

The language that was specified before was overly complicated. Replaced with language that hopefully makes the point in a way that is more clear.
Comment 3 Michael[tm] Smith 2011-08-04 05:06:03 UTC 
mass-move component to LC1