OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Low level versioning

[ Lists Home | Date Index | Thread Index ]
  • To: UBL-Dev <ubl-dev@lists.oasis-open.org>, "XML-Dev Mailing list" <xml-dev@lists.xml.org>
  • Subject: Low level versioning
  • From: "Fraser Goffin" <goffinf@googlemail.com>
  • Date: Wed, 17 May 2006 15:00:12 +0100
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=R2VPiUxVSIJWadpGsrSOvShtqJMBHF1eKg5DbKfmC+RD4EncTi3rvzH8aGISnqfRZBYIHN1zX3Pl9qoD7HWjAIA4CfP0OTScJdW6LN6iVLHNgs3QK17YOl83YeUh56Liw0aIqaZfR41snQcyRucuHSG3xBrAIRNT0CsQ8sN4jUQ=

There has been some recent discussion in my organisation as to whether
there is a need to provide verion information for each
element/aggregate in our standard data model.

Currently versioning is only visible to implementers on the business
transaction level schema (namespace), that is, individual parts are
not individually versioned.

Does UBL provide individual version information for each business
entity, and are each of these visible when entities are combined to
form a business transaction ?

I have a feeling that traceability to the core data model needs to
reflect version, but I remain to be convinced about whether it is
necessary at this level at run-time.

All opinions welcome.



News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS