RE: setting attributes in XML Inclusions (XInclude) Version 1.0 / W3C Working Draft 17-July-2000

The issue resolution (you can poke through the XML version to find it) says:


"The syntax is messy. Is it really a requirement to be able to "include
into" the value of an attribute? You can't do that with XML 1.0 and
(external) entity references. No clear use cases."

I think that including attributes or part/all of an attribute value is
difficult without introducing non-XML syntax.  XSLT's attribute value
templates are an example.  The syntactic complexity is immense, while the
benefits seem limited.  Simply a cost-benefit judgement call.

> -----Original Message-----
> From: Paul Grosso [mailto:pgrosso@arbortext.com]
> Sent: Wednesday, July 19, 2000 9:05 AM
> To: www-xml-xinclude-comments@w3.org
> Cc: Julian Reschke
> Subject: setting attributes in XML Inclusions (XInclude) Version 1.0 /
> W3C Working Draft 17-July-2000
> 
> 
> Julian,
> 
> Thank you for your comment on the XInclude draft.  
> 
> I am forwarding this message to the www-xml-xinclude-comments
> mailing list so that it gets properly recorded.
> 
> paul
> 
> >From: "Julian Reschke" <julian.reschke@gmx.de>
> >To: <www-xml-linking-comments@w3.org>
> >Date: Wed, 19 Jul 2000 11:10:33 +0200
> >Subject: setting attributes in XML Inclusions (XInclude) 
> Version 1.0 / W3C
> Working Draft 17-July-2000
> >
> >Hi,
> >
> >the previous draft included a suggestion for a mechanism 
> that would have
> >allowed to add the included resource as an attribute value:
> >
> >Issue (XInclude:32-include-attributes): Currently, it is not 
> possible to set
> >the value of an attribute through an include mechanism. This make it
> >difficult to generate XLinks for example. Should a mechanism 
> be developed to
> >include text as attribute values?
> >
> >I wonder why this wasn't added -- seems to be very useful 
> for instance if
> >one wants to XInclude the value of an XHTML href attribute...
> >
> >Julian
>

Received on Wednesday, 19 July 2000 13:01:22 UTC