Re: Fixing what's broke
Yes it is contrived. It's exaggerated to try and show a point. But it's no more contrived or exaggerated than your example of how short names can be! I did some analysis of the lengths of names used in various schemas on my system and came up with the following chart: http://codalogic.com/xmllite/name-frequency.png The x axis is the number of characters in the name. Each column is the sum of the percentage of that length name within each schema. 10 characters looks to make a peak. Add a namespace prefix to that and your looking at: <t:FaultNode>1</t:FaultNode> I still contend that for those who haven't been taking the medicine for a number of years, that's a really strange way to do things! Pete Cordell Codalogic Ltd Interface XML to C++ the easy way using C++ XML data binding to convert XSD schemas to C++ classes. Visit http://codalogic.com/lmx/ or http://www.xml2cpp.com for more info ----- Original Message ----- From: "Chris Burdess" <firstname.lastname@example.org> To: "Pete Cordell" <email@example.com> Cc: "Ramkumar Menon" <firstname.lastname@example.org>; <xml-dev@l...> Sent: Friday, December 10, 2010 2:45 PM Subject: Re: Fixing what's broke Pete Cordell wrote: > When I was first introduced to XML, very much with a data-oriented hat on > where you have lots of small values, my initial response to seeing > something like: > > <trajectory:initialVelocityVarianceCoefficient>1</trajectory:initialVelocityVarianceCoefficient> > > was "are you kidding? Next...". This is contrived, however. I have no idea what the ordinary usage term would be for this *in the pertinent domain*, however let us suppose that it is "IVVC". Note that abbreviating to an acronym here doesn't take away any of the readability or third-party semantics here, since there is very little of either in the first place (I'm not a physicist and I have no idea what "initial velocity variance coefficient" actually means, and I doubt many others do either). The point is that in the domain identified by the schema, workers in that field will have a very clear idea of what "IVVC" means, especially since it is nicely commented in the schema. It's the *normal case* for people to refer to verbosely named domain artifacts using acronyms. Likewise, we don't choose excessively verbose namespace prefixes since they're just a prefix and all we really need to do is disambiguate them from other namespace prefixes in the document. So let's choose a rather more reasonable prefix "t" for the trajectory schema. This results in something like <doc xmlns:t='http://weaponsofmassdestruction.com/missiles/trajectory'> ... <t:ivvc>1</t:ivvc> You see this all the time, it works and I don't see that there's anything broken about it. _______________________________________________________________________ XML-DEV is a publicly archived, unmoderated list hosted by OASIS to support XML implementation and development. To minimize spam in the archives, you must subscribe before posting. [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/ Or unsubscribe: email@example.com subscribe: firstname.lastname@example.org List archive: http://lists.xml.org/archives/xml-dev/ List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
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