[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Current issue list.
> In the HTML it is confusing that the issues are not in numeric order > I would suggest in the TOC using different colors to distinguish > open/resolved issues (rather than a diffferent font size). I've got this XSL from XML Schema WG. I didn't like distinction by font size either. Here is the fixed version. I believe all the problems you've mentioned are fixed. -- Kohsuke KAWAGUCHI +1 650 786 0721 Sun Microsystems kohsuke.kawaguchi@eng.sun.comTitle: TREX Issues List
Issues
TREX issue list
jjc@jclark.com
Status: resolved
Voted unanimously to resolve this issue by allowing elements with no declared children tp have whitespace.
jjc@jclark.com
Status: open
"except" and "butNot" by jjc. TC is open to other suggestions.
jjc@jclark.com
Status: postponed
jjc@jclark.com
Status: open
the original post suggests to introduce syntax sugars to match frequently used wildcard patterns. Namely,
Some concerns that whether this was important enough to be worth a special syntactic abbreviation. No conclusion was reached.
jjc@jclark.com
Status: open
jjc@jclark.com
Status: open
jjc@jclark.com
Status: resolved
jjc@jclark.com
Status: open
(a) Put a version in the TREX namespace URI (by jjc)
(b) Use a version attribute on the root element (by jjc)
Input from Eric van der Vlist obtains:
He suggests to have both (a) and (b)
Input from John Cowan obtains:
He suggests to use FPI (kk: kind of URN?)
jjc@jclark.com
Status: open
Input from Josh Lubell obtains:
He wants to have this because of his own experiences
Input from Kohsuke Kawaguchi obtains:
He suggests that this feature can be provided outside of the core spec (as a pre-processor like tool).
TC is still not convinved whether this feature is imporant enough to be added.
jjc@jclark.com
Status: open
James Clark proposed to change attribute name to more sutaible one, but none is suggested by anyone.
John Cowan suggests adding optional "grammar" attribute to "ref" element and thereby introducing the ability to refer to any ancestor grammar.
kohsuke.kawaguchi@eng.sun.com
Status: open
no solid proposal is made yet.
jjc@jclark.com
Status: resolved
jjc@jclark.com
Status: resolved
mura034@attglobal.net
Status: open
Various people sugges various names (including, but not limited to, TRELAX, TryRELAX, RELAXED, RELEX, REFLEX, RELAX XML Schema, TREELAX, RELAX 2, EXLAX, etc, etc.
One of the concern is whether we should include "XML Schema" in the name.
mura034@attglobal.net
Status: open
The current spec already has several restrictions that prevents problematic situations.
Some argues that the current restrictions have something to be desired.
mura034@attglobal.net
Status: open
Currently, TREX allows patterns like
<attribute name="foo"><attribute name="..." /></attribute>
<attribute name="foo"><element name="..." /></attribute>
Should we explicitly prohibits them?
(original posts [1] [2] ).Those malformed patterns cannot accept anything: any TREX processors can safely replace those malformed patterns by <notAllowed /> without changing semantics.
So at least it doesn't confuse processors.
Murata-san suggests to prohibit them explicitly.
Some argues that such constraints are unnecessary.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC