* Antone Roundy <[EMAIL PROTECTED]> [2005-08-29 19:00]: > More robust would be: > <ext:auto-download target="[EMAIL PROTECTED]'enclosure']" > default="false" /> > ...enabling extension elements to be named in @target without > requiring a list of @target values to be maintained anywhere.
Is it wise to require either XPath support in consumers or to formulate a hackneyed XPath subset specifically for this purpose? And what about namespaced elements? And what about intermediaries which transcribe the content into a document with different NS prefixes? I think sticking to just an @ext:auto-download attribute applicable to single elements is the wise thing to do. Of course, I wonder if we can’t simply use @xlink:type for the purpose… (I admit ignorance of the specifics of XLink, so this idea might be useless.) Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>
