- From: Alex Milowski <alex@milowski.org>
- Date: Tue, 24 Jul 2007 08:50:13 -0700
- To: public-xml-processing-model-wg@w3.org
On 7/24/07, Jeni Tennison <jeni@jenitennison.com> wrote: > > Alex Milowski wrote: > > On 7/23/07, Jeni Tennison <jeni@jenitennison.com> wrote: > >> Could we have a description of the semantics of the 'href' attribute on > >> <c:result>? What does it mean if both 'value' and 'href' are specified, > >> or is this impossible? > > > > Yes, I'll clarify that. > > > > The 'value' and 'href' attributes are mutually exclusive in their use by > > the steps. I'll clarify that in this section. > > Actually, looking through the places where this is used, why can't we > just have a <c:result> element whose *value* is the relevant value? The > advantage of this would be that it's easier (shorter XPath) to get to > the value: > > <p:count /> > <p:choose> > <p:when test="/p:result > 2"> > ... > </p:when> > <p:otherwise> > ... > </p:otherwise> > </p:choose> > > What do we gain by specially label those results that are URIs? I'm not sure what value we gain. I think we started with 'href' and then it expanded from there. I'm OK with making this the text value of the element. Any objections? -- --Alex Milowski "The excellence of grammar as a guide is proportional to the paucity of the inflexions, i.e. to the degree of analysis effected by the language considered." Bertrand Russell in a footnote of Principles of Mathematics
Received on Tuesday, 24 July 2007 15:50:17 UTC