RE: FW: XInclude use case for Device Independence

Thanks Arnaud,

I did think of that, but then I thought: "what if I wanted to have
more than one attribute in a tag determined by an AVT?" So then I
thought of this:

 <xi:include
   sel:avt="href,parse"
   href="concat('/news.xyz?date=',fn:current-date())"
   parse="di:somewierdfunction()"
 />

where the sel:avt attribute is a comma separated list of other
attributes in the tag that must be evaluated. The processing model
is getting more and more complex as we go on. But the dialog does
suggest that there's sufficient interest in the ideas to perhaps
broaden the debate.

[As this is my last day in the office this year, I wish you all the
best and look forward to continuing to work with you next year.]

---Rotan.

-----Original Message-----
From: Arnaud Le Hors [mailto:lehors@us.ibm.com]
Sent: 23 December 2004 02:31
To: Rotan Hanrahan
Cc: public-xml-core-wg@w3.org; tvraman@almaden.ibm.com
Subject: RE: FW: XInclude use case for Device Independence


A more scalable approach would be to include the name of the attribute in
the value with something like:

 <object sel:avt="src=concat('/news.xyz?date=',fn:current-date())"/>

But you still have to address the processing model question.
--
Arnaud  Le Hors - IBM, On Demand Operating Environment Standards




Wednesday, December 22, 2004 4:41 AM
To: <daniel@veillard.com>, <tvraman@almaden.ibm.com>
cc: <Norman.Walsh@Sun.COM>, <public-xml-core-wg@w3.org>
From: "Rotan Hanrahan" <Rotan.Hanrahan@MobileAware.com>
Subject: RE: FW: XInclude use case for Device Independence




You will notice from DISelect [1] that we have introduced the idea of
"selid", which is a selection ID attribute that is transformed into
an actual ID attribute. The purpose of this is to provide a mechanism
that can generate IDs for tags in the selected content, especially if
alternative selections required the same IDs.

I can envisage an extension of this idea to permit generic attributes
whose value is calculated via AVTs. Here is a sample of the markup:

 <sel:when sel:expr="dc:cssmq-color() &gt; 16">
 <object sel:avtsrc="concat('/news.xyz?date=',fn:current-date())"/>
 </sel:when>

And:

 <sel:when sel:expr="dc:cssmq-color() &lt; 4">
 <xi:include sel:avthref="concat('/news.xyz?date=',fn:current-date())"/>
 </sel:when>

This would enable DISelect to support the creation of src and href
attribute values via AVT. Unfortunately this aproach doesn't scale up
very well. A more generic approach would need to be considered, though
it would certainly address the requirements of the dynamic content
aggregation use case we've been considering.

Thanks for all the feedback to date.

---Rotan.


[1] http://www.w3.org/TR/cselection/#sec-selid-attribute


-----Original Message-----
From: Daniel Veillard [mailto:daniel@veillard.com]
Sent: 22 December 2004 12:58
To: tvraman@almaden.ibm.com
Cc: Rotan Hanrahan; Norman.Walsh@Sun.COM; public-xml-core-wg@w3.org
Subject: Re: FW: XInclude use case for Device Independence


On Tue, Dec 21, 2004 at 08:23:17AM -0800, T. V. Raman wrote:
> In general, having the ability to use AVTs (Attribute Value
> Templates) anywhere in XML -- rather than just in XSLT would be a
> huge win for a lot of use cases.

  Hum, AVTs are an escaping meachnism. That would mean you need to
  define when/where that escaping need to be undone and define XPath for
  anywhere in the document, there is arbitrary set of informations
  (like the prefix mappings, variables, current node set, position, ...)
  that would need to be defined. It doesn't sound that easy to me :-)

Daniel

--
Daniel Veillard      | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
daniel@veillard.com  | Rpmfind RPM search engine http://rpmfind.net/
http://veillard.com/ |

Received on Thursday, 23 December 2004 09:43:06 UTC