Lists Home |
Date Index |
- From: Ronald Bourret <email@example.com>
- To: "firstname.lastname@example.org" <email@example.com>
- Date: Tue, 15 Dec 1998 11:01:14 +0100
Dean Roddey wrote:
> Just from a practical standpoint though, if you found an element that had
> say three notations. One said it was MIDI, one said it was Base64, and
> said it was zipped. Was it base64'd then zipped, or zipped then base
> How would one indicate the ordering of original transformations in such a
> situation, so that it could be untransformed correctly back?
Your application would need to know the order. Given that there are no
standard notations at the moment, this doesn't seem unreasonable, as the
application needs to know what the notations mean, anyway.
If people "standardize" notations, this is a fair question. One quick hack
would be a NMTOKENS attribute that contained the names of the notation
attributes (or notations) in the order in which they were to be applied.
Or course, that attribute would need to be "standardized", too.
-- Ron Bourret
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)