W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > July 2007

Re: XProc Editors Draft 2007-07-19: Appendix A Introduction Comments

From: Jeni Tennison <jeni@jenitennison.com>
Date: Tue, 24 Jul 2007 11:40:18 +0100
Message-ID: <46A5D712.8010201@jenitennison.com>
To: public-xml-processing-model-wg@w3.org

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?

Jeni
-- 
Jeni Tennison
http://www.jenitennison.com
Received on Tuesday, 24 July 2007 11:05:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:53 GMT