|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Attributes with Intent (and namespaces)
what is the advantage to leaving the articulation (URI x local) part open in this interface? why isn't the parameter an opaque object? i'm not sure what the application concern is, but, for the relations which occurred to me, there are better ways to do that than having to broaden all name-related interfaces. if the issue is to "identify" symbols which, by prefix, reside in different regions of the articulated namespace, it could be done on a prefix to prefix basis or on a region to region basis - depending on whether the specification has a dynamic or an indefinite extent. if the issue is that one wants to do that on a name-by-name basis, there are better ways for that too. one could use a combination of importing and exporting names among regions. if the issue is that one whats to articulate the mapping per element, there are other ways to do that too, though i'm unclear why one would. MURATA Makoto wrote: > [re remarks from Peter Murray-Rust re attribute inheritance] > > Of course, this has to become namespace-aware. That is, the argument > of setInheritedAttribute should be a pair of URI and local part. > xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||

Cart








