1618 2005-07-15 01:07:52 +0000 the formal type notation for element is ambiguous 2005-09-27 08:41:25 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Formal Semantics 1.0 Last Call drafts PC Windows 2000 CLOSED FIXED P2 normal --- 1 fred.zemke simeon public-qt-comments oldest_to_newest 4694 0 fred.zemke 2005-07-15 01:07:52 +0000 2.4.2 Item types The following formal type notation is ambiguous: "element nillable of type foo:bar". Is this an element whose name is nillable and type is foo:bar (and not nillable), or is this an element of unspecified name whose type is foo:bar and nillable? One easy way to fix this would be to move the keyword "nillable" to a context where it cannot be mistaken for a name, for example, following TypeReference rather than preceding it. Thus rule [34 (Formal)] would be TypeSpecifier ::= TypeReference Nillable? Another way to fix it would be to say that ElementName must be quoted, ie, change rule [9 (Formal)] to ElementName ::= '"' QName '"' Or, following my suggestion that the grammar should have no defaults, make the element name mandatory (either a QName or an asterisk, say). 5040 1 simeon 2005-07-20 21:58:48 +0000 That is a good catch. We used to use an asterisk, so that might be the more natural choice: element * of type TypeName (: a wildcard element :) element * nillable of type TypeName (: a nillable wildcard element :) element nillable of type TypeName (: an element with name 'nillable' :) element nillable nillable of type TypeName (: a nillable element with name 'nillable :) - Jerome 5148 2 chamberl 2005-07-22 16:59:58 +0000 Fred, On July 22, 2005, the Query Working Group decided to resolve this comment by accepting Jerome's proposal to use an asterisk as a "wild card" for an element name. Since this was one of your suggested solutions, we assume that you will find this resolution acceptable. If you have any further input on this issue, you may reopen the comment. Regards, Don Chamberlin