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


Help: OASIS Mailing Lists Help | MarkMail Help

ubl message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [ubl] WD9 schemas with Extensions

I've been looking at how to create thoroughly proper UBL 2 prd2
instances and found what may be a problem
with the version attributes. An NDRule (latest published version) states
[VER15]	Every UBL document schema MUST include a required element  
named "UBLVersion" as the first child of its root element. This  
element MUST have a default value that matches the value of the  
xsd:version attribute of its containing schema.
and the corresponding rules for the above-mentioned xsd:version
attribute state
[VER11]	Every UBL Schema and schema module major version committee  
draft MUST capture its version number in the xsd:version attribute of  
the xsd:schema element in the form
[VER12]	Every UBL Schema and schema module major version OASIS  
Standard MUST capture its version number in the xsd:version attribute  
of the xsd:schema element in the form

I mention this now because it may be the only opportunity to 'fix' it.
I'd like to be able to produce instances which can be distinguished
as prd2 instances rather than any future revision of UBL 2.
To do this it seems most practical to use the [revision] identifier
in the xsd:version and include this in the UBLVersion value.

The problem is our latest UBL 2 prd2 schema files have just '2' in the
xsd:version. What I think we might need is to use '2.0.2' where the
'.2' is the revision identifier - in conformance with the rule to use
integers as the identifiers

If this is correct then the schema files need changing in the content
of the xsd:version attributes, and the examples instances changed
accordingly in the UBLVersionID attributes - both to '2.0.2'.

If however there is to be no further change to the schema files before
standardisation then the above might mean that the schema files we
currently have are the final version but for that we would, I thought,
have to have been voted as cd, voted as prd, reviewed publicly,
voted as cd, then as cs then finally as specification. I would think all
these stages would warrant separate release identifiers, except at the
last stage after voting as specification. I would like to be able to
reflect all this in instances. Maybe it isn't advisable of course to
implement anything except the eventual committee specification(s) and
then specification. Even so we'd need to distinguish in instances between
cs revisions and between those and a specification version. Only the latter
would not need the revision identifier in an instance.

All the best


Quoting "G. Ken Holman" <gkholman@CraneSoftwrights.com>:

> Hi folks,
> At 2006-07-14 23:33 +0000, swebb@gefeg.com wrote:
>> The document revision named UBL 2.0 PRD2 Schema (UBL 2.0 wd9spec.zip) has
>> been submitted by Ms. Sylvia Webb to the OASIS Universal Business Language
>> (UBL) TC document repository.  This document is revision #6 of UBL
>> 2.0_WD5.zip.
>> Document Description:
>> Public Review Draft 2 Schema with missing ExtensionElementType and changes
>> from NDR document dated 12 July
> Many thanks to Sylvia for producing the raw schemas from the
> spreadsheet models, and many thanks to Alan for working on the
> spreadsheet models.
> I've applied the following changes to those XSD files:
>  - changed filenames of "-2.xsd" to be "-2.0.xsd"
>  - changed schemaLocation attributes of "-2.xsd" to be "-2.0.xsd"
>  - added reference to UBLExtensions to each document model
>  - added comment reflecting this is a modification from the files
>    supplied
>  - replaced all attributes containing "UUIDID" with "UUID"
>  - replaced
>        urn:oasis:names:specification:ubl:schema:xsd:CoreComponentParameters-2
>    with
>        urn:un:unece:uncefact:documentation:2
>    in common\UBL-*.xsd
> The modified files can be found in the ZIP at:
>   http://www.oasis-open.org/committees/document.php?document_id=19157
> As before there is a test directory demonstrating the successful
> processing of a set of files with and without extensions.
> This ZIP includes a candidate deliverable of the XSD files for our next
> release ... please bang on it as much as possible to look for any
> problems.
> Thanks for all your help!
> . . . . . . . . . Ken
> --
> Registration open for UBL training:    Montréal, Canada 2006-08-07
> Also for XSL-FO/XSLT training:    Minneapolis, MN 2006-07-31/08-04
> Also for UBL/XML/XSLT/XSL-FO training: Varo,Denmark 06-09-25/10-06
> World-wide corporate, govt. & user group UBL, XSL, & XML training.
> G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
> Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/o/
> Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
> Male Cancer Awareness Aug'05  http://www.CraneSoftwrights.com/o/bc
> Legal business disclaimers:  http://www.CraneSoftwrights.com/legal
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]