Bug 12208 – [XDM30] How XDM nodes are created should be an implementation-defined item

Bug 12208 - [XDM30] How XDM nodes are created should be an implementation-defined item


Summary:	[XDM30] How XDM nodes are created should be an implementation-defined item

Status:	RESOLVED FIXED

Product:	XPath / XQuery / XSLT
Classification:	Unclassified
Component:	Data Model 3.0
Version:	Recommendation
Hardware:	PC All

Importance:	P2 normal
Target Milestone:	---
Assigned To:	Norman Walsh
QA Contact:	Mailing list for public feedback on specs from XSL and XML Query WGs

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-03-01 00:26 UTC by John Snelson
Modified:	2011-07-27 19:39 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description John Snelson 2011-03-01 00:26:42 UTC

The Data Model spec describes the creation of XDM nodes from an InfoSet, and from a PSVI. It also says that they may be created from other unspecified information.

I believe we should make it an implementation-defined feature how the XDM nodes are created and from what information.

Comment 1 Norman Walsh 2011-05-31 15:42:07 UTC

I changed the second paragraph after the bulleted list in section 3 to address this bug:

<p>An instance of the data model can also be constructed directly
through application APIs, or from non-XML sources such as relational
tables in a database.
Data model construction from sources other than
an Infoset or PSVI is implementation-defined.
Regardless of how an instance of the data model
is constructed, every node and atomic value in the data model must
have a typed-value that is consistent with its type.</p>

Comment 2 Jonathan Robie 2011-06-09 20:23:49 UTC

This should probably be mentioned in "7 Conformance" in the Data Model document.