Altova Mailing List Archives

Re: [xml-dev] xml:href, xml:rel and xml:type

From: Michael Kay <mike@--------.--->
To: xml-dev@-----.---.---
Date: 4/16/2012 5:15:00 PM
>> If that's the case, then I'm sceptical about
>> whether this information belongs in the XML.
> Why are you sceptical?
Remember third normal form?

My postcode is RG4 7BS. That's a relationship, between me and where I 
live. If I want to record my postcode in an XML data file, that is the 
way I should record it. If someone wants to use that fact to get 
information about that postcode from a web service provide by the UK 
Post Office, or the Ordnance Survey, or Google, that's a matter for the 
user of the data and/or the application. The address of the web service 
and the domain name of its provider doesn't need to be stored 
redundantly with every postcode. To do so is simply bad normalization; 
and it violates the objectives of normalization, which is to maximize 
potential for change. If the application decides to get its information 
about postcodes from Google rather than from the PostOffice, why should 
that mean changing the address data for every customer?

Michael Kay


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:
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive:
List Guidelines:


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.