Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Best Practice for adding a "standard data item" to pre-existingXML vocabularies?

From: Marcus Carr <mcarr@-------.---.-->
To: xml-dev@-----.---.---
Date: 4/1/2008 1:47:00 AM
Roger Costello wrote:

> Suppose that a number of different communities have already created
> their own unique XML vocabularies.  To promote cross-community
> interoperability (including mashups) the communities decide to
> standardize "When" information since they all have, in one form or
> another, "When" information.  What is best practice for incorporating
>  a standard information item (e.g. a "When" information item) into a
> diverse set of pre-existing XML vocabularies?

That assumes there is such a thing as a standard information item. Even 
if there seems to be one between two organisations today, there is no 
guarantee that there will be tomorrow. If one side changes and you've 
standardised it, how will you cope with change?

I prefer a model where you document the intersections between documents 
as a set of configuration items, providing somewhere for developers to 
find out how to manage passing data from one structure to another. 
Trying to cram vocabularies together is not scalable - at some point, it 
has to fall apart. Documenting intersections is scalable - if you want 
to add a new vocabulary, you add it, without any change to anything 
except your configuration item. I think that putting the information in 
the hands of the developers is more useful than trying to formalise 
vocabularies for the short term.


Marcus


transparent
Print
Mail
Like It
Disclaimer
.

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 www.altova.com/list/index.html. 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.

.
.

transparent

transparent