Altova Mailing List Archives

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

From: Michael Kay <mike@--------.--->
To: xml-dev@-----.---.---
Date: 4/15/2012 6:08:00 PM

On 13/04/2012 13:36, Rushforth, Peter wrote:
> I am interested in RESTful applications, and in thinking about the space, I have come
> to think that XML, while wonderful for creating your own domain specific vocabulary,
> also suffers from that very strength:  too many re-inventions of the same thing (because
> its so easy to reinvent) leads to no standardization/interoperability at all.
So why reinvent XLink?

I've always had the view that data models generally consist of objects 
(elements), attributes, and relationships, and if XML allows you to 
dream up your own names for your elements and attributes then it should 
also allow you to use your own name for your relationships. Why should 
we use the same name for the relationship between a product and its 
manufacturer as we use for the relationship between a factory and its 
geographical location?

I think that's why XLink failed, and I don't see any difference in your 

Now, data typing is another matter: it would be nice if attributes 
containing dates, integers, or URIs were recognizable as such without 
recourse to a schema. But forcing all URIs to be called xlink:href is as 
crazy as forcing all dates to be called date.

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.