[Bug 27119] [XQX31] unnecessary nesting in array constructors

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27119

--- Comment #2 from Michael Dyck <jmdyck@ibiblio.org> ---
(In reply to C. M. Sperberg-McQueen from comment #1)
> The WG considered this issue in the face to face meeting today.  There was
> some sentiment on each side of the question,

That surprises me. In my original post, I gave supporting examples of how the
XQueryX schema has handled analogous situations in the past. Did the sentiment
on the other side of the question provide any reasoning for treating these new
cases differently?

> In general, an
> XML serialization of a context-free grammar can be designed to be as
> light-weight as is consistent with clarity, or to match the grammar as
> closely as possible, with each non-terminal turning into an element type.

Agreed.

> While XQueryX is not absolutely consistent in this regard, the general
> design approach is toward close alignment with the grammar.

If "close alignment with the grammar" is meant to refer to the second approach
described in the previous sentence, then I disagree that that's the general
approach used by XQueryX. I think it's actually closer to the first approach.
Can anyone give examples (aside from the constructs in question) of how it's
*not* "as light-weight as is consistent with clarity"? Because I can certainly
give lots of examples where it *doesn't* turn each non-terminal into an element
type.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 29 October 2014 05:42:36 UTC