Lists Home |
Date Index |
- From: "Don Park" <firstname.lastname@example.org>
- To: "'XML Dev'" <email@example.com>
- Date: Thu, 25 Nov 1999 16:54:12 -0800
>> Written by somebody, I forget who (sorry):
>That was me.
>I think both of these are very good examples, but I think that the
>information you desire could not be in the fragment itself.
>The reason I used the example of returning one node in my
>previous message was because it raises the question "where
>would you put these restrictions?"
While some of the information could be part of the fragment,
encoded in an out-of-band namespace of sort, I think you are
right that remaining information will have to be stored
externally. At this point, I am thinking that a sort of
'connection' or 'glue' fragment which 'includes' the target
fragment could be used. This 'glue' fragment could be treated
exactly like the original and is an excellent place to fill-in,
override, translate some of the missing pieces in the target
fragment. Like putting blue rubber coating over wire to indicate
its capability and than putting it a bin that provides its
purpose... Hmm, that analogy was lacking something...
Don Park - mailto:firstname.lastname@example.org
Docuverse - http://www.docuverse.com
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)