[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?
Not exactly although I agree that when using XML as The GUI, it looks the same. The namespace should enable me to stay consistent with the driving schema. I can get it for free using the elementFormDefault switch, yes? Now, if the editor is aware of the namespace, I should be able to get it from the GUI too, yes? Right. That changeability thing is a bear. At least for XML Schemas, we do have online resources to suggest what the best practices are. That's a good start when using XML Schemas. How much of it relates to other schema languages, or to just markup in general is not something I've given much thought to. len -----Original Message----- From: Gavin Thomas Nicol [mailto:gtn@r...] On Tuesday 18 February 2003 02:34 pm, Bullard, Claude L (Len) wrote: > Then I ask you this question: can XML namespaces > be leveraged to help guide an author? I say it can. > > <nikon:lens> > > is better than > > <lens> There is an abvious difference here, but how about between <nikon:lens/> and <lens manufacturer="Nikon"/> ? The information content is the same right? > Assertion (unproven): complexity of content > and complexity of markup are about the same if one > drops HTML or other forms of presentation > markup. I'd agree with the assertion, except for all the other factors your brought up. Markup design is a compromise between purity and practicality, and the balance changes over time.
|
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
|