[
Lists Home |
Date Index |
Thread Index
]
Title: RE: [xml-dev] XML Schema Versioning
Joseph,
Thanks for your suggested reading. Your presentation of the Core Component Types certainly provided a very useful summary. It has helped me to understand a fairly simple concept that I have struggled to understand from the documentation. I now realise how close it comes to all those corporate entity models that I have been involved with in the past but on a much more global scale.
I am going to have to read the ebXML 2.5 Registry Services Specification in some detail to see if this can solve some of the issues that I have. The ebXML registry is primarily designed for ebusiness with external partners; what we are going to do is provide internal services using SOA. However, providing an internal registry may have some advantages if the Life Cycle Management Service can provide Object versioning that was not in the v2.0 specification.
Not being part of a technology or software organisation it is probably going to be hard for me to justify membership of Oasis and any technical committees. Generally our organisation is not leading edge and we are happy to follow where others lead. Unfortunately, on my particular issue no one seems to be leading and giving a clear cut process to versioning. Various techniques have been suggested even W3C have produced "Versioning XML Languages" by David Orchard that shows how to use extensibility for forward compatibility.
Max Chappell's document probably expressed the solution I am likely to adopt with major and minor release versions. I am starting to think that maybe it's the management of the versioned Schemas that I require rather than the XML techniques.
Regards,
Jon
-----Original Message-----
From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
Sent: 04 December 2003 15:13
To: Barwell Jonathan
Cc: 'xml-dev@lists.xml.org'; regrep@lists.oasis-open.org; CCRev
Subject: Re: [xml-dev] XML Schema Versioning
[Copying OASIS/ebXML Registry TC and Core Components Review SC on this
XML-DEV response]
Jonathan,
I would like to propose a solution for you that is not solidified today,
but is in process. It is a combination of the following 2 items:
(1) A data modeling methodology called UN/CEFACT-ebXML Core Components
(which is very similar to your description)
(2) Use of an ebXML Registry
For more on (1), please see my recent XML-DEV posting [1] which includes
a URL to a presentation I gave earlier this year on Core Components. We
are in the process of writing an OASIS Technical Note for the
implementation of Core Components in an ebXML Registry.
For more on (2), please see the following recent links:
- ebXML Registry Brochure (start reading at top right):
http://xml.coverpages.org/EbizXMLRegistry200310.pdf
- New Production-Ready Release of Open Source ebXML Registry:
http://xml.coverpages.org/ni2003-09-17-a.html
- Release of OASIS/ebXML Registry 2.5 specifications:
http://xml.coverpages.org/ni2003-06-26-a.html
- Adobe acquisition of Yellow Dragon Software, an ebXML Registry vendor:
http://xml.coverpages.org/AdobeYellowDragon.html
And lastly: If you are an OASIS member (or would like to be), we would
be very happy to have you join the OASIS/ebXML Registry TC [2]. Please
feel free to contact me offline if you are interested.
Kind Regards,
Joe Chiusano
Booz | Allen | Hamilton
[1] http://lists.xml.org/archives/xml-dev/200311/msg00852.html
[2] http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=regrep
************************************************************************
DISCLAIMER
The information contained in this e-mail is confidential and is intended
for the recipient only.
If you have received it in error, please notify us immediately by reply
e-mail and then delete it from your system. Please do not copy it or
use it for any other purposes, or disclose the content of the e-mail
to any other person or store or copy the information in any medium.
The views contained in this e-mail are those of the author and not
necessarily those of Admenta UK Group.
************************************************************************
| 