[
Lists Home |
Date Index |
Thread Index
]
- To: "David RR Webber (XML)" <david@drrw.info>
- Subject: Re: [ubl-dev] Low level versioning
- From: "Fraser Goffin" <goffinf@googlemail.com>
- Date: Wed, 17 May 2006 23:25:51 +0100
- Cc: UBL-Dev <ubl-dev@lists.oasis-open.org>, "XML-Dev Mailing list" <xml-dev@lists.xml.org>
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=aNqhLagu7aHqYQzn+Hx4UtzNnfrkyjhSodoUrI1t51ReXeLJw+GF8A8GOS7o2dkp5GaI/rm7InrrGeH3zGe2OuwPVWKwW9fRz2UjeAarVS68obQqSMw79R+CKr7pn4Is73dQTlyhk+jIu8Y/NLKta8Ni1QKOhq/hYEEY/QWpkKM=
- In-reply-to: <20060517071154.dc066b1d4d2e0a1a65719ae85a8071e6.52e4396803.wbe@email.secureserver.net>
- References: <20060517071154.dc066b1d4d2e0a1a65719ae85a8071e6.52e4396803.wbe@email.secureserver.net>
H'mm this CAM thing keeps coming up, I must make some time available
to look into it further. What is the best way to do this David ?
Is CAM a UBL only thing or is it adaptable to other XML vocabularies ?
Fraser.
On 17/05/06, David RR Webber (XML) <david@drrw.info> wrote:
> Fraser,
>
> I very much believe versioning is needed to the element/attribute level
> in an operational environment and using OASIS CAM this is very much
> attainable / essential.
>
> Therefore I'd pro-offer - if this is a key business need - then you
> can use CAM templates to overlay this fine level of detail over the
> base UBL schema between you are your partners.
>
> As for UBL itself - since the version only changes periodically -
> on a major release schedule - then the course grained ns approach
> is probably sufficient.
>
> DW
>
>
>
> -------- Original Message --------
> Subject: [ubl-dev] Low level versioning
> From: "Fraser Goffin" <goffinf@googlemail.com>
> Date: Wed, May 17, 2006 10:00 am
> To: UBL-Dev <ubl-dev@lists.oasis-open.org>, "XML-Dev Mailing list"
> <xml-dev@lists.xml.org>
>
> 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.
>
> Fraser.
>
> ---------------------------------------------------------------------
> This publicly archived list supports open discussion on implementing the
> UBL OASIS Standard. To minimize spam in the
> archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Alternately, using email: list-[un]subscribe@lists.oasis-open.org
> List archives: http://lists.oasis-open.org/archives/ubl-dev/
> Committee homepage: http://www.oasis-open.org/committees/ubl/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> Join OASIS: http://www.oasis-open.org/join/
>
>
> ---------------------------------------------------------------------
> This publicly archived list supports open discussion on implementing the UBL OASIS Standard. To minimize spam in the
> archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Alternately, using email: list-[un]subscribe@lists.oasis-open.org
> List archives: http://lists.oasis-open.org/archives/ubl-dev/
> Committee homepage: http://www.oasis-open.org/committees/ubl/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> Join OASIS: http://www.oasis-open.org/join/
>
>
|
