Tuesday, 25 March 2008
- Re: [Bug 5156] 3.4.2 XML Representation of Complex Type Definitions
- Re: [Bug 5156] 3.4.2 XML Representation of Complex Type Definitions
Monday, 24 March 2008
Wednesday, 19 March 2008
Friday, 7 March 2008
Monday, 10 March 2008
Sunday, 9 March 2008
- [Bug 5062] what facets apply to union?
- [Bug 5062] what facets apply to union?
- [Bug 5550] references to fundamental facets
- [Bug 5549] datatypes not ·ordered·, but ordered {value} is partial
- [Bug 5062] what facets apply to union?
Saturday, 8 March 2008
- [Bug 1917] RQ-140: distinguish negative from positive zero in float and double (Requirement)
- [Bug 1913] RQ-120: use the term 'derived' consistently (Structures) (Desideratum)
- [Bug 2044] R-198: ensure that unions of unions retain union-level facets
- [Bug 5194] Editorial comments on section 3.4.2
- [Bug 5141] small editorial changes section 3.4-3.6
- [Bug 5144] small editorial changes section 3.8.6-3.15.1
- [Bug 5139] small editorial changes sections 3.0-3.2
- [Bug 5137] small editorial changes sections 0-2
- [Bug 4276] Namespace Constraint Property Record problems
- [Bug 5231] name xpath subset used in identity constraint selectors
- [Bug 3249] Constants
- [Bug 5286] Component constraints within XML representation constraints
Friday, 7 March 2008
Thursday, 6 March 2008
Wednesday, 5 March 2008
- [Bug 5535] Definition of [nil] is wrong
- [Bug 2337] Add {context} property to simple type definition in Datatypes
- [Bug 1929] RQ-141e: Make pattern value be a set of regexes, not one regex
- [Bug 1917] RQ-140: distinguish negative from positive zero in float and double (Requirement)
- [Bug 1912] RQ-31e: remove lexicalMappings facet
- [Bug 1907] RQ21: BNF, regex, etc for float and double
- [Bug 1853] RQ-141b define and use "ancestor" in mapping rules for simple type defns (Requirement)
- [Bug 1852] RQ-141b -- Changes to Part 2 to align with Part 1 (Requirement)
- [Bug 1843] RQ-141b: Editing intro paragraphs of Datatypes Sec 2 (Requirement)
- [Bug 1926] EP-14: define 'literal' and use it more consistently
- [Bug 1925] EP-01: clarify complex property values and component classes (Datatypes)
- [Bug 1919] RQ-150c: set minimum implementation reqs for precisionDecimal (Requirement)
- [Bug 1918] RQ-150b: set minimum implementation reqs for decimal (Requirement)
- [Bug 1903] RQ21: BNF, regex, etc for boolean
- [Bug 1902] RQ21: BNF, regex, etc for string
- [Bug 1836] RQ-100 define canonical form for language type, update RFC reference
- [Bug 5162] wildcard notQname=defined
- [Bug 5161] all model group min/maxoccurs confusing
- [Bug 5160] all group info in odd place
Tuesday, 4 March 2008
- [Bug 5281] Why allow an element to be valid against a declaration with the wrong name?
- [Bug 5273] xpathDefaultNamespace on identity constraints
- [Bug 5282] UPA and overlapping substitution groups
Monday, 3 March 2008
Friday, 29 February 2008
- [Bug 4764] delete words appropriate for leap-seconds
- [Bug 5322] Nonterminal "Char" has two productions
- [Bug 3224] Inequality
- [Bug 5229] Definition of xs:double
- [Bug 3950] {fixed} is redundant for length
- [Bug 5157] 3.4.2 example unclear
- [Bug 5512] Definition of valid schema document is incomplete
Thursday, 28 February 2008
Wednesday, 27 February 2008
- [Bug 5507] Symbol spaces need clearer description
- [Bug 5322] Nonterminal "Char" has two productions
- [Bug 3950] {fixed} is redundant for length
- [Bug 4764] delete words appropriate for leap-seconds
- [Bug 5229] Definition of xs:double
- [Bug 3224] Inequality
- [Bug 4764] delete words appropriate for leap-seconds
- [Bug 5229] Definition of xs:double
Tuesday, 26 February 2008
Thursday, 21 February 2008
- [Bug 3892] 3.4.1 ambiguous/erroneous wording - prohib. subst. relation to elem. decl.
- [Bug 3891] 3.14.6 wording - missing/unclear antecedent
- [Bug 3889] 3.3.1 incorrect use of "respectively" (editorial)
Wednesday, 20 February 2008
Tuesday, 19 February 2008
- [Bug 3220] Terminology: "must"
- [Bug 5003] Applicability of <alternative> element to xml:lang
- [Bug 5200] Not ##defined. Use ##definedSibling
Monday, 18 February 2008
- [Bug 5487] Special status of namespaces xs, xsi, xml etc
- [Bug 5487] Special status of namespaces xs, xsi, xml etc
Saturday, 16 February 2008
- [Bug 5486] Regex: Names of Unicode code blocks
- [Bug 5486] Regex: Names of Unicode code blocks
- [Bug 5486] Regex: Names of Unicode code blocks
Friday, 15 February 2008
- [Bug 5164] validation vs assessment
- [Bug 5162] wildcard notQname=defined
- [Bug 5161] all model group min/maxoccurs confusing
- [Bug 5160] all group info in odd place
- [Bug 5157] 3.4.2 example unclear
- [Bug 5152] tableau presentation difficult to understand
- [Bug 5146] small editorial changes missing blanks multiple sections
- [Bug 5142] small editorial changes section 3.8.4
- [Bug 5276] targetNamespace defined on xs:element
- [Bug 5276] targetNamespace defined on xs:element
Wednesday, 13 February 2008
- Re: [Bug 5476] xsi:schemaLocation should be a hint, should be MAY not SHOULD
- [Bug 5476] xsi:schemaLocation should be a hint, should be MAY not SHOULD
- [Bug 5476] xsi:schemaLocation should be a hint, should be MAY not SHOULD
- Re: [Bug 2218] R-226: Must the content of schemaLocation be a resolvable URL?
- [Bug 2218] R-226: Must the content of schemaLocation be a resolvable URL?
Tuesday, 12 February 2008
Sunday, 10 February 2008
- [Bug 5244] Move co-constraints into types
- [Bug 5079] Type tables and substitution groups
- [Bug 5077] Use of "le" in assertion test
- [Bug 5076] Comparator modification not apparent
- [Bug 5072] minor editorial issues
Saturday, 9 February 2008
- [Bug 5052] S4S: unresolved type for attributes test declared within "assertion" and "altType"
- [Bug 5053] S4S: Issues on the complex type definition "altType"
- [Bug 5004] 2007-08-30 WD: inconsistency between type keybase of S4S and Section 3.11.3 (icd representation)
- [Bug 5074] substitution groups not that strictly limited
Friday, 8 February 2008
- [Bug 5165] Editorial: numbering of rules and constraints
- [Bug 5263] Errors in the S4SD
- [Bug 5077] Use of "le" in assertion test
- [Bug 3892] 3.4.1 ambiguous/erroneous wording - prohib. subst. relation to elem. decl.
- [Bug 5470] 3.4.1 ambiguous/erroneous wording - prohib. subst. relation to elem. decl.
- [Bug 3589] Definitions of "schema document" draft proposal for bugs 2822 and 2846 PSVI and processor profiles
- [Bug 5274] Nomenclature: defaultXPathDefaultNamespace
- [Bug 4368] Editorial: what does "the appropriate case ... is true" mean?
- [Bug 5193] Validation Rule: Element Locally Valid (Complex Type)
- [Bug 2842] RQ-134 Origin of inherited portions of content model (scd-origin-inheritance)
- [Bug 5160] all group info in odd place
- [Bug 3724] Rule "Content type restricts" needs clarification
- [Bug 2195] R-202: How many components are there for complextype extensions?
- [Bug 5266] XSDL?
- [Bug 2811] align use of 'atomic' with part 2
- [Bug 4202] Add a note to clarify validity of partial "unique" values
- [Bug 5162] wildcard notQname=defined
- [Bug 2828] RQ-155 State prohibition of use attribute on top-level attributes more clearly (topleveluse)
- [Bug 4280] Add example(s) to show how idc references work
- [Bug 2309] Clarify identity of values across related simple types
- [Bug 5072] minor editorial issues
- [Bug 5076] Comparator modification not apparent
- [Bug 5469] substitution groups not that strictly limited
- [Bug 5469] substitution groups not that strictly limited
- [Bug 5074] substitution groups not that strictly limited
- [Bug 5074] substitution groups not that strictly limited
- [Bug 5468] 3.14.6 wording - missing/unclear antecedent
- [Bug 3891] 3.14.6 wording - missing/unclear antecedent
- [Bug 2947] Datatypes 2006-02-17 WD: what makes an order trivial?
- [Bug 3889] 3.3.1 incorrect use of "respectively" (editorial)
- [Bug 5467] 3.3.1 incorrect use of "respectively" (editorial)
- [Bug 5467] 3.3.1 incorrect use of "respectively" (editorial)
- [Bug 5466] Point out the cases where attribute prohibitions are pointless
- [Bug 2311] Point out the cases where attribute prohibitions are pointless
- [Bug 5146] small editorial changes missing blanks multiple sections
- [Bug 5052] S4S: unresolved type for attributes test declared within "assertion" and "altType"
- [Bug 5161] all model group min/maxoccurs confusing
- [Bug 5004] 2007-08-30 WD: inconsistency between type keybase of S4S and Section 3.11.3 (icd representation)
- [Bug 5059] XDM should be referenced normatively
- [Bug 2162] R-165: Clarification requested for statement in Appendix H of Structures
- [Bug 5053] S4S: Issues on the complex type definition "altType"
- [Bug 5265] Interchangeable use of "xs" and "xsd" prefixes
- [Bug 5142] small editorial changes section 3.8.4
- [Bug 5029] Editorial: repeated word
- [Bug 2218] R-226: Must the content of schemaLocation be a resolvable URL?
- [Bug 4398] XML declaration appears after DocType in appendix A
- [Bug 2082] R-092: Clarification required for group redefinition
- [Bug 3963] Editorial work on "Attribute Locally Valid (Use)"
- [Bug 4518] inaccurate description of PSVI in 3.16.5
- [Bug 5465] Bug in anchor for documentation of hexBinary type
- [Bug 4839] Bug in anchor for documentation of hexBinary type
- [Bug 4839] Bug in anchor for documentation of hexBinary type
- [Bug 2947] Datatypes 2006-02-17 WD: what makes an order trivial?
- [Bug 2947] Datatypes 2006-02-17 WD: what makes an order trivial?
- [Bug 3249] Constants
- [Bug 3266] "Current schema"
- [Bug 4912] Allow empty unions
- [Bug 4900] typo in 4.3.1.4 (need quantifier)
- [Bug 4089] Some RFCs in "normative references" are not used
- [Bug 3265] Length facet for QNames
- [Bug 3869] Annotation mapping for simple type and facets
- [Bug 3256] BC dates
- [Bug 4033] "(constraining) facets" section missing for "date"
- [Bug 4986] typo in "3.4.3 language" Note
- [Bug 3840] Mistaken id in appendix C.1: string.preserve
- [Bug 5276] targetNamespace defined on xs:element
- [Bug 5276] targetNamespace defined on xs:element
- [Bug 4368] Editorial: what does "the appropriate case ... is true" mean?
- [Bug 2842] RQ-134 Origin of inherited portions of content model (scd-origin-inheritance)
- [Bug 5263] Errors in the S4SD
- [Bug 5161] all model group min/maxoccurs confusing
- [Bug 5146] small editorial changes missing blanks multiple sections
- [Bug 5076] Comparator modification not apparent
- [Bug 5265] Interchangeable use of "xs" and "xsd" prefixes
- [Bug 5142] small editorial changes section 3.8.4
- [Bug 5077] Use of "le" in assertion test
- [Bug 5074] substitution groups not that strictly limited
- [Bug 5072] minor editorial issues
- [Bug 5059] XDM should be referenced normatively
- [Bug 5052] S4S: unresolved type for attributes test declared within "assertion" and "altType"
- [Bug 5053] S4S: Issues on the complex type definition "altType"
- [Bug 5029] Editorial: repeated word
- [Bug 5004] 2007-08-30 WD: inconsistency between type keybase of S4S and Section 3.11.3 (icd representation)
- [Bug 4518] inaccurate description of PSVI in 3.16.5
- [Bug 4398] XML declaration appears after DocType in appendix A
- [Bug 3892] 3.4.1 ambiguous/erroneous wording - prohib. subst. relation to elem. decl.
- [Bug 3963] Editorial work on "Attribute Locally Valid (Use)"
- [Bug 3891] 3.14.6 wording - missing/unclear antecedent
- [Bug 3889] 3.3.1 incorrect use of "respectively" (editorial)
- [Bug 2311] Point out the cases where attribute prohibitions are pointless
- [Bug 2218] R-226: Must the content of schemaLocation be a resolvable URL?
- [Bug 2162] R-165: Clarification requested for statement in Appendix H of Structures
- [Bug 2082] R-092: Clarification required for group redefinition
- [Bug 3892] 3.4.1 ambiguous/erroneous wording - prohib. subst. relation to elem. decl.
Tuesday, 5 February 2008
- [Bug 3232] Type versus Datatype
- [Bug 3232] Type versus Datatype
- [Bug 3232] Type versus Datatype
- [Bug 3232] Type versus Datatype
- [Bug 3232] Type versus Datatype
- [Bug 3232] Type versus Datatype
- [Bug 3589] Definitions of "schema document" draft proposal for bugs 2822 and 2846 PSVI and processor profiles
- [Bug 3232] Type versus Datatype
- [Bug 3256] BC dates
- [Bug 3869] Annotation mapping for simple type and facets
- [Bug 4089] Some RFCs in "normative references" are not used
- [Bug 2947] Datatypes 2006-02-17 WD: what makes an order trivial?
- [Bug 3265] Length facet for QNames
- [Bug 3840] Mistaken id in appendix C.1: string.preserve
- [Bug 4912] Allow empty unions
- [Bug 3266] "Current schema"
- [Bug 4986] typo in "3.4.3 language" Note
- [Bug 4033] "(constraining) facets" section missing for "date"
- [Bug 4900] typo in 4.3.1.4 (need quantifier)
- [Bug 4839] Bug in anchor for documentation of hexBinary type
- [Bug 3232] Type versus Datatype
- [Bug 5193] Validation Rule: Element Locally Valid (Complex Type)
- [Bug 5274] Nomenclature: defaultXPathDefaultNamespace
- [Bug 5266] XSDL?
- [Bug 5160] all group info in odd place
- [Bug 4280] Add example(s) to show how idc references work
- [Bug 3724] Rule "Content type restricts" needs clarification
- [Bug 4202] Add a note to clarify validity of partial "unique" values
- [Bug 3589] Definitions of "schema document" draft proposal for bugs 2822 and 2846 PSVI and processor profiles
- [Bug 2195] R-202: How many components are there for complextype extensions?
- [Bug 5162] wildcard notQname=defined
- [Bug 2828] RQ-155 State prohibition of use attribute on top-level attributes more clearly (topleveluse)
- [Bug 2811] align use of 'atomic' with part 2
- [Bug 2309] Clarify identity of values across related simple types
Monday, 4 February 2008
- [Bug 3232] Type versus Datatype
- [Bug 5003] Applicability of <alternative> element to xml:lang
- [Bug 5003] Applicability of <alternative> element to xml:lang
- [Bug 3963] Editorial work on "Attribute Locally Valid (Use)"
- [Bug 3891] 3.14.6 wording - missing/unclear antecedent
- [Bug 5160] all group info in odd place
- [Bug 5137] small editorial changes sections 0-2
- [Bug 5193] Validation Rule: Element Locally Valid (Complex Type)
- [Bug 5141] small editorial changes section 3.4-3.6
- [Bug 4398] XML declaration appears after DocType in appendix A
- [Bug 5167] misc editorial
- [Bug 5265] Interchangeable use of "xs" and "xsd" prefixes
- [Bug 5146] small editorial changes missing blanks multiple sections
- [Bug 3889] 3.3.1 incorrect use of "respectively" (editorial)
- [Bug 2311] Point out the cases where attribute prohibitions are pointless
- [Bug 4202] Add a note to clarify validity of partial "unique" values
- [Bug 4276] Namespace Constraint Property Record problems
- [Bug 5144] small editorial changes section 3.8.6-3.15.1
- [Bug 4518] inaccurate description of PSVI in 3.16.5
- [Bug 5162] wildcard notQname=defined
- [Bug 5029] Editorial: repeated word
- [Bug 5142] small editorial changes section 3.8.4
- [Bug 5139] small editorial changes sections 3.0-3.2
- [Bug 3589] Definitions of "schema document" draft proposal for bugs 2822 and 2846 PSVI and processor profiles
- [Bug 5004] 2007-08-30 WD: inconsistency between type keybase of S4S and Section 3.11.3 (icd representation)
- [Bug 5072] minor editorial issues
- [Bug 5262] Incorrect link to S4SD
- [Bug 5150] unclear if some prose is normative or non-normative
- [Bug 5059] XDM should be referenced normatively
- [Bug 5052] S4S: unresolved type for attributes test declared within "assertion" and "altType"
- [Bug 5194] Editorial comments on section 3.4.2
- [Bug 5274] Nomenclature: defaultXPathDefaultNamespace
- [Bug 5345] Split SCC: Derivation Valid (Extension) into 2 parts
- [Bug 5077] Use of "le" in assertion test
- [Bug 5195] Editorial comments on section 3.4.4
- [Bug 5145] small editorial changes section 4.2.4-5.2
- [Bug 5156] 3.4.2 XML Representation of Complex Type Definitions
- [Bug 5164] validation vs assessment
- [Bug 5003] Applicability of <alternative> element to xml:lang
- [Bug 5231] name xpath subset used in identity constraint selectors
- [Bug 5158] discuss general name/ref pattern up front
- [Bug 5273] xpathDefaultNamespace on identity constraints
- [Bug 5281] Why allow an element to be valid against a declaration with the wrong name?
- [Bug 5276] targetNamespace defined on xs:element
Wednesday, 30 January 2008
- [Bug 4850] Update of reference for language data type
- [Bug 2576] Clarify relation of language type to xml:lang
- [Bug 2576] Clarify relation of language type to xml:lang
- [Bug 2439] ChecK new RFC 3066 bis
- [Bug 3079] RFC3066 ref
- [Bug 4850] Update of reference for language data type
- [Bug 3244] Sets of lists
- [Bug 3228] Lists|Unions of Lists|Unions
- [Bug 3237] Relationship to programming language types
- [Bug 3244] Sets of lists
- [Bug 3230] Atomic = not decomposable?
- [Bug 3237] Relationship to programming language types
- [Bug 3230] Atomic = not decomposable?
- [Bug 3249] Constants
Tuesday, 29 January 2008
- [Bug 5436] Editorial: replace 'attributed to' with 'bound to' ?
- [Bug 5436] Editorial: replace 'attributed to' with 'bound to' ?
- [Bug 5165] Editorial: numbering of rules and constraints
Monday, 28 January 2008
- [Bug 5435] The term "valid schema" is used but not defined
- [Bug 5023] Relationship between identity constraints and assertions
Sunday, 27 January 2008
Saturday, 26 January 2008
- [Bug 5431] Normal characters, character references
- [Bug 5431] Normal characters, character references
- [Bug 5192] Terminology: "absent" (editorial)
Friday, 25 January 2008
- [Bug 5427] Primer materials within the Structures Rec
- [Bug 5426] Revisit whether or allow partial XPath implementation
- [Bug 5425] Revise Composition
- [Bug 5425] Revise Composition
- [Bug 2069] R-079: Ambiguity in statements about valid type derivation
- [Bug 4336] Another occurrence of nested modals
- [Bug 4336] Another occurrence of nested modals
- [Bug 3963] Editorial work on "Attribute Locally Valid (Use)"
- [Bug 4470] Editorial work in "Attribute Locally Valid (Use)"
- [Bug 3963] Editorial work on "Attribute Locally Valid (Use)"
- [Bug 5258] Garbled text (? or other problem?) in Str 3.5.4 Attribute locally valid (use)
- [Bug 5289] "##defined" in wildcards
- [Bug 5074] substitution groups not that strictly limited
- [Bug 5193] Validation Rule: Element Locally Valid (Complex Type)
- [Bug 5192] Terminology: "absent" (editorial)
- [Bug 5155] 3.3.2 XML Representation of Element Declaration Schema Components
- [Bug 5153] 3.2.2 XML Representation of Attribute Declaration Schema Components
- [Bug 5153] 3.2.2 XML Representation of Attribute Declaration Schema Components
- [Bug 5151] pseudo-normative qualifications used in apparently normative contexts
- [Bug 5149] normative format rfc2119 keywords used in non-normative notes
- [Bug 5157] 3.4.2 example unclear
- [Bug 5079] Type tables and substitution groups
- [Bug 5168] vc:maxVersion versioning
- [Bug 5168] vc:maxVersion versioning
- [Bug 5165] Editorial: numbering of rules and constraints
- [Bug 5127] Missing NOTATION component
- [Bug 5274] Nomenclature: defaultXPathDefaultNamespace
- [Bug 5150] unclear if some prose is normative or non-normative
- [Bug 5297] Drop restriction of assertions to down-pointing XPaths?
- [Bug 5244] Move co-constraints into types
- [Bug 5244] Move co-constraints into types
- [Bug 5293] Subsumption
- [Bug 5276] targetNamespace defined on xs:element
Thursday, 24 January 2008
- [Bug 5276] targetNamespace defined on xs:element
- [Bug 5286] Component constraints within XML representation constraints
- [Bug 5266] XSDL?
- [Bug 5200] Not ##defined. Use ##definedSibling
- [Bug 5163] schemalocation needs to be cleaned up and clarified
- [Bug 5078] define required components
- [Bug 5286] Component constraints within XML representation constraints
- [Bug 5164] validation vs assessment
- [Bug 5164] validation vs assessment
- [Bug 5281] Why allow an element to be valid against a declaration with the wrong name?
- [Bug 5281] Why allow an element to be valid against a declaration with the wrong name?
- [Bug 5282] UPA and overlapping substitution groups
- [Bug 5296] An oddity with substitution groups
- [Bug 5273] xpathDefaultNamespace on identity constraints
- [Bug 5003] Applicability of <alternative> element to xml:lang
- [Bug 5412] Is lax assessment required after "missing sub-component"?
Wednesday, 23 January 2008
- [Bug 5345] Split SCC: Derivation Valid (Extension) into 2 parts
- [Bug 5023] Relationship between identity constraints and assertions
- [Bug 5023] Relationship between identity constraints and assertions
- [Bug 5030] Assertions on simple types
- [Bug 5126] Assertions: usability
- [Bug 5412] Is lax assessment required after "missing sub-component"?
- [Bug 3251] how to introduce primitives
- [Bug 5003] Applicability of <alternative> element to xml:lang
Tuesday, 22 January 2008
Monday, 21 January 2008
- [Bug 5003] Applicability of <alternative> element to xml:lang
- [Bug 5003] Applicability of <alternative> element to xml:lang
Saturday, 19 January 2008
Friday, 18 January 2008
- Re: possible bug in XML Schema 1.1 Part 2: Datatypes (was Re: question about lexical and value spaces)
- RE: question about lexical and value spaces
- RE: question about lexical and value spaces
- possible bug in XML Schema 1.1 Part 2: Datatypes (was Re: question about lexical and value spaces)
- [Bug 5003] Applicability of <alternative> element to xml:lang
- RE: question about lexical and value spaces
- [Bug 5003] Applicability of <alternative> element to xml:lang
Thursday, 17 January 2008
- [Bug 5003] Applicability of <alternative> element to xml:lang
- [Bug 5003] Applicability of <alternative> element to xml:lang
- [Bug 4850] Update of reference for language data type
Tuesday, 15 January 2008
- [Bug 5378] [SCD] XML representation of schema components
- [Bug 5378] [SCD] XML representation of schema components
- [Bug 5377] Requirement for metadata querying
- [Bug 5377] Requirement for metadata querying
- [Bug 5376] [SCD] Richer extension story
- [Bug 5376] [SCD] Richer extension story
- [Bug 5375] [SCD] Regularize the grammar
- [Bug 5375] [SCD] Regularize the grammar
- [Bug 2824] RQ-151 Define schema composition (composition)
- [Bug 5374] [SCD] Crisp identity conditions
- [Bug 5374] [SCD] Crisp identity conditions
- [Bug 5373] [SCD] Define accessors
- [Bug 5373] [SCD] Define accessors
- [Bug 5372] Define bridge functions
- [Bug 5372] Define bridge functions
- [Bug 5371] [SCD] Eliminate notion of 'elided steps'
- [Bug 5371] [SCD] Eliminate notion of 'elided steps'
- [Bug 2660] lc-3: QA review of XML Schema: Component Designators
- [Bug 3677] [SCD] Numeric predicates confusing
- [Bug 2662] lc-5: Rule out default namespace
- [Bug 3682] [SCD] ModelGroupStep production error
- [Bug 2658] lc-1 : rfc2396bis
- [Bug 3681] [SCD] missing component::* from BNF
- [Bug 3683] [SCD] Allow for ./ in paths
- [Bug 3684] [SCD] // confusing
- [Bug 5320] [SCD] Rename element:: and attribute:: axes
- [Bug 4449] How do you write an empty namespace prefix?
- [Bug 3855] Use of "Default Axis" versus XPath
- [Bug 3685] [SCD] (Editorial) Origanize by axes
- [Bug 5003] Applicability of <alternative> element to xml:lang
- [Bug 5003] Applicability of <alternative> element to xml:lang
- [Bug 5003] Applicability of <alternative> element to xml:lang
Monday, 14 January 2008
- [Bug 5003] Applicability of <alternative> element to xml:lang
- [Bug 5003] Applicability of <alternative> element to xml:lang
Friday, 11 January 2008
- [Bug 5161] all model group min/maxoccurs confusing
- [Bug 5165] Editorial: numbering of rules and constraints
Thursday, 10 January 2008
- Re: question about lexical and value spaces
- RE: question about lexical and value spaces
- Re: question about lexical and value spaces
Wednesday, 9 January 2008
- Re: question about lexical and value spaces
- [Bug 5353] Do "path" etc. apply to model groups or particles or content models?
- Re: question about lexical and value spaces
- RE: question about lexical and value spaces
- question about lexical and value spaces
Tuesday, 8 January 2008
- [Bug 5238] Resolution to bug 2850 needs additional example - key/keyref
- [Bug 4280] Add example(s) to show how idc references work
- [Bug 2753] wd-27: Errors in component diagram
- [Bug 2753] wd-27: Errors in component diagram
Monday, 7 January 2008
Sunday, 6 January 2008
- [Bug 5321] REs are not production nonterminals
- [Bug 5165] Editorial: numbering of rules and constraints
- [Bug 5321] REs are not production nonterminals
- [Bug 5165] Editorial: numbering of rules and constraints
- [Bug 5321] REs are not production nonterminals
Friday, 4 January 2008
- [Bug 3251] need for precisionDecimal / how to introduce primitives
- [Bug 3251] need for precisionDecimal / how to introduce primitives
- [Bug 5345] Split SCC: Derivation Valid (Extension) into 2 parts
- [Bug 5165] Editorial: numbering of rules and constraints
- [Bug 5152] tableau presentation difficult to understand
- [Bug 5193] Validation Rule: Element Locally Valid (Complex Type)
- [Bug 5165] Editorial: numbering of rules and constraints
- [Bug 5195] Editorial comments on section 3.4.4
- [Bug 5193] Validation Rule: Element Locally Valid (Complex Type)
- [Bug 5192] Terminology: "absent" (editorial)
- [Bug 5168] vc:maxVersion versioning
- [Bug 5165] Editorial: numbering of rules and constraints
- [Bug 5157] 3.4.2 example unclear
Thursday, 3 January 2008
- RE: [Bug 5152] tableau presentation difficult to understand
- Re: [Bug 5152] tableau presentation difficult to understand
- RE: [Bug 5152] tableau presentation difficult to understand
- RE: Make more use of {base type definition}
- Re: [Bug 5152] tableau presentation difficult to understand
- Make more use of {base type definition}
- [Bug 5152] tableau presentation difficult to understand
- [Bug 5149] normative format rfc2119 keywords used in non-normative notes
- [Bug 5150] unclear if some prose is normative or non-normative
- [Bug 5149] normative format rfc2119 keywords used in non-normative notes
- [Bug 5074] substitution groups not that strictly limited
- [Bug 5074] substitution groups not that strictly limited
- [Bug 5074] substitution groups not that strictly limited