This document is incomplete. It will be updated ASAP after the Nov
12 publication date of the 2nd Data Model Last Call Working Draft.
Material reproduced from comments has been marked up, and obvious
typos have been corrected. Postings and documents which raise several
substantively distinct points have been silently divided among several
comments. To consult the original postings, see the sources listed for
each comment.
Commentators are requested to review the entries for the comments they
have made, and to check to make sure we have correctly understood and
paraphrased their comment.
Not all postings to the comments mailing list have resulted in entries
in this list. For example, postings which ask for clarification and do
not result in any errata, are not necessarily included in this list.
The status of each issue is recorded in the table. The status may be:
“open” indicating that the issue has not been processed; “addressed” indicating
that the issue has been addressed; or “closed” indicating that the issue
is closed. Issues marked as “addressed” will be changed to “closed” as
the original submitters agree that the issues have been addressed to their
satisfaction.
Comment |
Status |
Class |
Summary |
DM-LC1-0001 |
addressed |
editorial |
XPath/XQuery/Data Model : Data Model Inconsistency? |
DM-LC1-0002 |
addressed |
editorial |
fn:base-uri($srcval) is still unclear |
DM-LC1-0003 |
addressed |
editorial |
Data Model: 3.2 Document order of fragments? |
DM-LC1-0004 |
addressed |
editorial |
Data Model : What is a "fragment"? |
DM-LC1-0005 |
addressed |
editorial |
Data Model 3.3 - "sequences of fragments and sequences of documents" |
DM-LC1-0006 |
addressed |
editorial |
Serialization / Data Model - make more clearly consistent |
DM-LC1-0007 |
addressed |
editorial |
Data Model: 4 - Nodes (and "root nodes") |
DM-LC1-0008 |
addressed |
editorial |
Data Model: 4.1.1 "uri" or "URI"? |
DM-LC1-0009 |
addressed |
editorial |
Data Model: 4.1.3 - "qualified name" or expanded-QName? |
DM-LC1-0010 |
addressed |
editorial |
Data Model: 4.1.4 Parent Accessor |
DM-LC1-0011 |
addressed |
editorial |
Data Model: 4.2.1 - "document" or "document node"? |
DM-LC1-0012 |
addressed |
editorial |
Data Model: 4.1.11 Typo |
DM-LC1-0013 |
addressed |
editorial |
Data Model: 4.2.3 |
DM-LC1-0014 |
addressed |
technical |
Related to DM-LC1-0030. |
DM-LC1-0015 |
addressed |
technical |
RE: /WD-xpath-datamodel-20030502/ |
DM-LC1-0016 |
addressed |
technical |
Addressed by DM-LC1-0015 |
DM-LC1-0017 |
addressed |
editorial |
DM: What is a "document"? |
DM-LC1-0018 |
addressed |
editorial |
DM: What is an "element"? |
DM-LC1-0019 |
addressed |
editorial |
DM: Imprecise Headings in 4.2 to 4.8 |
DM-LC1-0020 |
addressed |
editorial |
DM: 3.3 "sequences of documents" |
DM-LC1-0021 |
addressed |
editorial |
DM: 3.3 "inconsistent data models are forbidden" |
DM-LC1-0022 |
addressed |
editorial |
DM: Inconsistency between 3.4 and 4.1.7 |
DM-LC1-0023 |
addressed |
editorial |
[DM] 3.6 - What does this mean? |
DM-LC1-0024 |
addressed |
editorial |
[DM] 4.1.3 "qualified name" |
DM-LC1-0025 |
addressed |
editorial |
[DM] 4.1.3 What is an xsd:QName? |
DM-LC1-0026 |
addressed |
editorial |
[DM] 4.2.2 Table |
DM-LC1-0027 |
addressed |
editorial |
data model: parent of namespace nodes |
DM-LC1-0028 |
addressed |
editorial |
Data Model - 4.5.4 Data Model to Infoset Mapping |
DM-LC1-0029 |
addressed |
editorial |
data model - PSVI to DM mapping - parent of Element nodes |
DM-LC1-0030 |
addressed |
technical |
Related to DM-LC1-0014. |
DM-LC1-0031 |
addressed |
editorial |
copy/paste error |
DM-LC1-0032 |
closed |
editorial |
Resolving issue 526 will change the data model |
DM-LC1-0033 |
addressed |
technical-minor |
make datetime tuples real types |
DM-LC1-0034 |
addressed |
editorial |
implementation defined and implementation-dependent |
DM-LC1-0035 |
addressed |
editorial |
Data model spec issues |
DM-LC1-0036 |
addressed |
editorial |
Data model spec issues |
DM-LC1-0037 |
addressed |
editorial |
Data model spec issues |
DM-LC1-0038 |
addressed |
editorial |
Data model spec issues |
DM-LC1-0039 |
addressed |
editorial |
Data model spec issues |
DM-LC1-0040 |
addressed |
editorial |
Data model spec issues |
DM-LC1-0041 |
addressed |
editorial |
Data model spec issues |
DM-LC1-0042 |
addressed |
editorial |
Data model spec issues |
DM-LC1-0043 |
addressed |
editorial |
Data model spec issues |
DM-LC1-0044 |
addressed |
editorial |
SAG-DM-01; Mixed content |
DM-LC1-0045 |
addressed |
technical |
SAG-DM-02; Type hierarchy |
DM-LC1-0046 |
addressed |
technical |
SAG-DM-03; Document node metadata |
DM-LC1-0047 |
addressed |
editorial |
Improve definition of stable order |
DM-LC1-0048 |
addressed |
technical-minor |
Namespace nodes |
DM-LC1-0049 |
addressed |
editorial-major |
Documents are not internally/cross-document consistent |
DM-LC1-0050 |
addressed |
pending-clarification |
ORA-DM-DATASET |
DM-LC1-0051 |
addressed |
editorial |
clarify relationship between nodes and information items |
DM-LC1-0052 |
addressed |
editorial |
document nodes vs. root nodes |
DM-LC1-0053 |
addressed |
editorial |
Clarify |
DM-LC1-0054 |
addressed |
editorial |
ORA-DM-ANYTYPE-TYPED-VALUE |
DM-LC1-0055 |
addressed |
technical-minor |
Clarify rules for anonymous type names |
DM-LC1-0056 |
addressed |
editorial |
ORA-DM-SCHEMA-VALIDATED |
DM-LC1-0057 |
addressed |
editorial |
ORA-DM-SYNTHETIC |
DM-LC1-0058 |
addressed |
editorial |
ORA-DM-QNAME-FONT |
DM-LC1-0059 |
addressed |
editorial |
ORA-DM-UNTYPEDATOMIC |
DM-LC1-0060 |
addressed |
technical |
What should we do about the term "fragment" in the DM document? |
DM-LC1-0061 |
addressed |
editorial |
ORA-DM-CHILD |
DM-LC1-0062 |
addressed |
editorial |
Name is right; inform the commenter |
DM-LC1-0063 |
addressed |
editorial |
ORA-DM-TYPE-CONSISTENCY |
DM-LC1-0064 |
addressed |
editorial |
ORA-DM-NAMESPACE-PREFIXES |
DM-LC1-0065 |
addressed |
editorial |
Related to DM-LC1-0060. |
DM-LC1-0066 |
addressed |
editorial |
ORA-DM-A-LANGUAGE |
DM-LC1-0067 |
addressed |
editorial |
ORA-DM-VALUE |
DM-LC1-0068 |
addressed |
editorial |
Related to DM-LC1-0047 |
DM-LC1-0069 |
addressed |
editorial |
ORA-DM-A-ORDER |
DM-LC1-0070 |
addressed |
editorial |
ORA-DM-DOCORDER |
DM-LC1-0071 |
addressed |
editorial |
ORA-DM-ORDER-NODES |
DM-LC1-0072 |
addressed |
editorial |
ORA-DM-ORDERTOTAL |
DM-LC1-0073 |
addressed |
editorial |
ORA-DM-NOTXML |
DM-LC1-0074 |
addressed |
editorial |
ORA-DM-VALUES-NODES |
DM-LC1-0075 |
addressed |
editorial |
ORA-DM-TYPEITALICS |
DM-LC1-0076 |
addressed |
editorial |
ORA-DM-PARENT |
DM-LC1-0077 |
addressed |
editorial |
ORA-DM-NONEMPTY |
DM-LC1-0078 |
addressed |
editorial |
ORA-DM-PROPERTIES-BRACKETS |
DM-LC1-0079 |
addressed |
editorial |
ORA-DM-NODES-TREES |
DM-LC1-0080 |
addressed |
editorial |
ORA-DM-PROPERTIES-DOCUMENT |
DM-LC1-0081 |
addressed |
editorial |
ORA-DM-PROPERTIES-BASEURI |
DM-LC1-0082 |
addressed |
editorial |
ORA-DM-PROPERTIES-AMBIGUITY |
DM-LC1-0083 |
addressed |
technical |
ORA-DM-MAPPINGS-USE |
DM-LC1-0084 |
addressed |
technical |
ORA-DM-MAPPINGS-DOCUMENT |
DM-LC1-0085 |
addressed |
editorial |
ORA-DM-MAPPINGS-SETS |
DM-LC1-0086 |
addressed |
editorial |
References to the xsi:nil attribute are a mistake. |
DM-LC1-0087 |
addressed |
technical |
ORA-DM-MAPPINGS-ORDER |
DM-LC1-0088 |
addressed |
editorial |
ORA-DM-MAPPINGS-CHILDREN |
DM-LC1-0089 |
addressed |
editorial |
ORA-DM-ATOMIC-SINGULAR |
DM-LC1-0090 |
addressed |
editorial |
ORA-DM-MAPPINGS-SEQUENCE |
DM-LC1-0091 |
addressed |
editorial |
LC place holder for XML Core editorial comments |
DM-LC1-0092 |
addressed |
technical |
Expanded name terminology |
DM-LC1-0093 |
addressed |
technical |
Type mapping list incomplete |
DM-LC1-0094 |
addressed |
technical |
Atomic values list incomplete |
DM-LC1-0095 |
addressed |
technical |
Why are union values sequences? |
DM-LC1-0096 |
addressed |
editorial |
ORA-DM-MAPPING-FORMAT 4.2.3 PSVI to Data Model mapping |
DM-LC1-0097 |
addressed |
editorial |
ORA-DM-MAPPINGS-SEQUENCE2 4.2.4 Data model to Infoset mapping |
DM-LC1-0098 |
addressed |
editorial |
ORA-DM-CHILDPARENT 4.3.1 Overview |
DM-LC1-0099 |
addressed |
editorial |
ORA-DM-CHILDPARENT2 4.3.1 Overview |
DM-LC1-0100 |
addressed |
editorial |
ORA-DM-NSATT-ORDER 4.3.2 Accessors |
DM-LC1-0101 |
addressed |
editorial |
ORA-DM-OTHERWISE 4.4.3 PSVI to Data Model mapping |
DM-LC1-0102 |
addressed |
editorial |
ORA-DM-PI 4.6.1 Overview |
DM-LC1-0103 |
addressed |
editorial |
ORA-DM-FRAGMENT-TREE Appendix A, XML Information Set Conformance |
DM-LC1-0104 |
addressed |
technical |
ORA-DM-PARENT-ACCESSOR 4.1 Accessors |
DM-LC1-0105 |
addressed |
technical-minor |
ORA-DM-STRINGVALUE 4.1.5 string-value Accessor |
DM-LC1-0106 |
addressed |
technical-minor |
ORA-DM-COMMENTNODE 4.1.6 typed-value Accessor |
DM-LC1-0107 |
addressed |
technical-minor |
ORA-DM-NAMESPACENODE 4.1.6 typed-value Accessor |
DM-LC1-0108 |
addressed |
technical |
DOM WG: DOM1 |
DM-LC1-0109 |
addressed |
technical |
DOM WG: DOM2 |
DM-LC1-0110 |
addressed |
technical-minor |
DOM WG: DOM3 |
DM-LC1-0111 |
addressed |
technical |
DOM WG: DOM4 |
DM-LC1-0112 |
addressed |
technical |
DOM WG: DOM5 |
DM-LC1-0113 |
addressed |
technical |
DOM WG: DOM6 |
DM-LC1-0114 |
addressed |
technical |
DOM WG: DOM7 |
DM-LC1-0115 |
addressed |
technical |
DOM WG: DOM8 |
DM-LC1-0116 |
addressed |
editorial |
Comments for WD-xpath-datamodel-20030502 and WD-xpath-functions-20030502 |
DM-LC1-0117 |
addressed |
technical |
Additiaonl XML Core comment on XPath data model |
DM-LC1-0118 |
addressed |
editorial |
Holder for editorial comments from I18N |
DM-LC1-0119 |
addressed |
technical |
I18N [7]: extended data models: language associated with text nodes, for example |
DM-LC1-0120 |
addressed |
technical |
I18N [8]: improve support for inherited attributes |
DM-LC1-0121 |
addressed |
technical |
I18N [11]: anyType, anyAtomicType, etc. |
DM-LC1-0122 |
addressed |
technical |
I18N [12]: Date and time mappings |
DM-LC1-0123 |
addressed |
technical |
I18N [19]: Discrepancy between string value of element and string value of document |
DM-LC1-0124 |
addressed |
technical |
I18N [20]: Use of xs:string where xs:anyURI would be better |
DM-LC1-0125 |
addressed |
technical |
I18N [21]: DM to Infoset mapping issues |
DM-LC1-0126 |
addressed |
technical |
I18N [33]: Enumerate cases where lexical representation differs from XPath 1.0 |
DM-LC1-0127 |
addressed |
technical |
I18N [D]: Update the example |
DM-LC1-0128 |
addressed |
editorial |
Place holder for XML Schema WG editorial issues |
DM-LC1-0129 |
addressed |
technical |
2.1: timezone issues |
DM-LC1-0130 |
addressed |
technical |
2.2: anyAtomicType |
DM-LC1-0131 |
addressed |
technical |
2.3: untypedAtomic |
DM-LC1-0132 |
addressed |
technical |
2.6: Plans for CR/PR/REC |
DM-LC1-0133 |
addressed |
editorial |
Place holder for editorial comments from Don Chamberlin |
DM-LC1-0134 |
addressed |
technical |
[validity] = invalid |
DM-LC1-0135 |
addressed |
technical |
typed-value of elements with complex type |
DM-LC1-0136 |
addressed |
technical |
Prefixes for namespaces in the infoset mapping |
DM-LC1-0137 |
addressed |
technical |
type of typed-value of comment nodes |
DM-LC1-0138 |
addressed |
editorial |
Data model spec issues |
DM-LC1-0001: XPath/XQuery/Data Model : Data Model Inconsistency?