W3C home > Mailing lists > Public > www-xml-xinclude-comments@w3.org > December 2002

RE: Architectural problems of the XInclude CR

From: David Orchard <dorchard@bea.com>
Date: Mon, 30 Dec 2002 11:35:45 -0800
To: "'Simon St.Laurent'" <simonstl@simonstl.com>
Cc: "'MURATA Makoto \(FAMILY Given\)'" <EB2M-MRT@asahi-net.or.jp>, "'Elliotte Rusty Harold'" <elharo@metalab.unc.edu>, <www-xml-xinclude-comments@w3.org>, <www-xml-linking-comments@w3.org>, <www-tag@w3.org>
Message-ID: <006301c2b03a$a6950150$d11ce8d8@beasys.com>

> -----Original Message-----
> From: www-tag-request@w3.org
> [mailto:www-tag-request@w3.org]On Behalf Of
> Simon St.Laurent
> Sent: Monday, December 30, 2002 10:17 AM
> To: David Orchard
> Cc: 'MURATA Makoto (FAMILY Given)'; 'Elliotte Rusty Harold';
> www-xml-xinclude-comments@w3.org; www-xml-linking-comments@w3.org;
> www-tag@w3.org
> Subject: RE: Architectural problems of the XInclude CR

> >And I think XInclude treads the ground carefully.
> XInclude doesn't begin to ask this range of questions, much
> less propose
> an answer.  That doesn't strike me as anywhere near careful.

It makes the cast, and the new "type" explicit.  After that, caveat emptor.
Much better than guessing or having default rules.  There's not much more
that XInclude per se could or should do.

Received on Monday, 30 December 2002 14:38:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:09:32 UTC