I made some comments in-line. I put *
around my comments.
1.1 Rules for Versioning
[R 1]
Each namespace should have a
version.
*Each version should have a
namespace.*
[R 2]
Each minor version must be given a
separate namespace.
*I disagree. I suppose I
may be missing something regarding the polymorphic processing. But I think this
will become overly burdensome to maintain in a namespace and would prefer to see
it maintained as a dual function of a root version attribute and the schema
version attribute.*
[R 3]
Minor versioning must be limited to
declaring new constructs, extending existing constructs and refinement (XSD
normative definition).
*Minor versioning must be
limited to declaring new optional constructs and refinements of an optional
nature.*
[R 4]
Changes in minor versions must be
break semantic compatibility with prior versions.
*Changes in minor versions
must NOT break semantic compatibility
with prior versions.*
[R 5]
Minor version namespaces must
reference preceding minor version root schemas.
All changes in minor versions will be backwards compatible
to previous minors and its corresponding major.
-----Original Message-----
From: Lisa Seaburg
[mailto:]
Sent: Friday, November 29, 2002 10:08
AM
To: UBL-NDR
Subject: [ubl-ndrsc] Versioning
Notes
I am attaching the notes on Versioning pulled out
of our minutes at the Face to face. I have started to format as
rules. I included everything I could find, plus I am attaching a
Versioning paper that might help us. This will be discussed on the next
NDR teleconference next Wednesday. Thanks.
Lisa
++++++++++++++++++++++++++++++++++++++++++++++++++++
Lisa
Seaburg
AEON Consulting
Website: http://shell.gmi.net/~xmlgeek/
Email:
Alternative
Email:
Phone:
662-562-7676
Cellphone: 662-501-7676
"Remember that great love and great achievements
involve great
risk."
++++++++++++++++++++++++++++++++++++++++++++++++++++
