[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Getting Back to Basics - How to describe Dates and Times andEvents?
> How does a URI pointer in lieu of a simple tag/data set facilitate > the requirement to support solutions appropriate for SME's? It identifies both ownership and value, together with an optional role (anything that exists between the first and last slash). One of the problems with coded values is that there is no concept of ownership of the value: 16 can mean one thing in one context and another in another. URIs can avoid this. The second important thing is that the URI is clearly a property of the element, and not a component of it. It is, therefore, easier to convince people that they do not need a substructure to their elements if you tell them that what you are defining is a pointer to the type rather than the type itself. Martin
Powered by eList eXpress LLC