[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Datatype and identity constraints proposal of the day (17 May)
Shall I list them as separate issues to the issue list? > 2. Should it be possible for parameter values to be context dependent? If > so, a parameter would be modelled as a <NCName, string, context> triple > instead of a <NCName, string> pair. Only if we can agree to get rid of QName. But that means we can't write RELAX NG grammar by RELAX NG, because it uses QName. Well, I hate QNames, so I'm happy to throw it away! But I doubt if it's practical. > 3. Should the value of a <param> be specified in the content or by with a > value attribute? Having a value as an attribute makes it possible for other applications to add their elements as a child of <param> like: <param name="minInclusive" value="08:00:00"> <xhtml:p> The store will be open 7:00AM in New Year's Eve. </xhtml:p> </param> -- Kohsuke KAWAGUCHI +1 650 786 0721 Sun Microsystems kohsuke.kawaguchi@eng.sun.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC