Chris Bizer wrote:
> Another comment: I think we don't need <contentAfter> or <contentLast> in
> the intermediate tree, just having a <content> element is enough because the
> before,after-stuff is determined by the relative position of the <content>
> element to the <value> element. So, we could change the example to:
>
> <inter:Property>
> <inter:uri>http://xmlns.com/foaf/0.1/mbox</inter:uri>
> <inter:label> Mailbox </inter:label>
> <inter:value> emmanuel_at_irina.org </inter:value>
> <inter:content>, <inter:content>
> <inter:value> emmanuel_at_w3.org </inter:value>
> <inter:content>.<inter:content>
> <inter:Property>
If you do it that way, yes. But that is not how I was seeing things. I
was more seeing the encoding of this knowledge as something more
abstract. To illustrate this I am using a more complex example based on
the previous one. You propose:
<inter:Property>
<inter:uri>
http://xmlns.com/foaf/0.1/mbox</inter:uri>
<inter:label> Mailbox </inter:label>
<inter:value> emmanuel.pietriga_at_inria.fr </inter:value>
<inter:content>, <inter:content>
<inter:value> emmanuel_at_w3.org </inter:value>
<inter:content>, <inter:content>
<inter:value> emmanuel.pietriga_at_lri.fr </inter:value>
<inter:content>, <inter:content>
<inter:value> epietriga_at_yahoo.fr </inter:value>
<inter:content>, <inter:content>
<inter:value> epietriga_at_gmail.com </inter:value>
<inter:content>.<inter:content>
<inter:Property>
whereas I was thinking about:
<inter:Property>
<inter:uri>
http://xmlns.com/foaf/0.1/mbox</inter:uri>
<inter:label> Mailbox </inter:label>
<inter:contentAfter>,</inter:contentAfter>
<inter:contentLast>.</inter:contentLast>
<inter:value> emmanuel.pietriga_at_inria.fr </inter:value>
<inter:value> emmanuel_at_w3.org </inter:value>
<inter:value> emmanuel.pietriga_at_lri.fr </inter:value>
<inter:value> epietriga_at_yahoo.fr </inter:value>
<inter:value> epietriga_at_gmail.com </inter:value>
<inter:Property>
> This would make it easier to write XSLT templates which copy the content to
> the final output.
Yes. So both have their advantages and drawbacks. Yours is easier to
manipulate by "dumb" tools such as XSLT processors because it is very
concrete. Mine is more abstract, thus less verbose and more
"presentation knowledge oriented", though this is a loose claim and I am
not sure it has any actual benefit.
--
Emmanuel Pietriga
INRIA Futurs - Projet In Situ tel : +33 1 69 15 34 66
Bat 490, Université Paris-Sud fax : +33 1 69 15 65 86
91405 ORSAY Cedex FRANCE http://www.lri.fr/~pietriga
Received on Wed May 04 2005 - 09:03:57 EDT