[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Re: Are the publishing users happy? Why not?
Sure, but if you get the namespace support from the tool for free, why resort to the period hack (well known from the old Oster system)? My assumption based on the issue being XML design is that the designer has modularized the vocabularies for all the usual reasons, and now the tool reflects that in some way. The attribute version assumes the vocabulary is not modularized, or at least, not for that property. Of course, the attribute reflects the semantic (it is a manufacturer) and the namespace only reflects the vocabulary and assumes the user knows this is a sign for the manufacturer. len From: Bill de hOra [mailto:bill@d...] Gavin Thomas Nicol wrote: > There is an abvious difference here, but how about between > > <nikon:lens/> > > and > > <lens manufacturer="Nikon"/> > > ? > > The information content is the same right? I was about to offer: <nikon.lens> as I thought Len was talking about visual cues to users rather than information capture. But I like the attribute approach better. Fwiw, there seems to be more (explicit) information with the attribute (if you look at it in an RDFish way as <subject property="value"/>. There's also opportunity to do searches and sorts with such attributes.
|
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
|