second attempt.
----- Original Message -----
From: Norbert Schade
To: UPD group
Sent: Monday, January 12, 2004 12:22 PM
Subject: ClassifyingID
This is probably one of the most important changes we made lately.
The previous attributes Predefined_ID and Proprietary_ID have now been merged into a single attribute ClassifyingID.
This is not a unique attribute by definition, but will provide for a meaningful identification of a record.
We had to change the data types significantly to be able to do this. we now much more work with unions and patterns, which was a request earlier.
Element and attributes (other than the type definition) are not affected in any way by this change.
Advantage:
Now it's much easier to check a classifying ID, as it is only one.
In the design of the schemas it's easier to control the classifying identifiers.
As a developer filling in data into an instance you'll find it more convenient, as you will see a list of predefined values as a template to choose from, but in many cases can overwrite that with your proprietary value if required.
The reference to a classifying id in the command sequence instance is now straightforward. Before there was an implication that you can refer to a Predefined_ID, but expect the driver to check the related Proprietary_ID as well, if available.
Easier coding.
Regards
Norbert Schade
Norbert Schade
69 Prescott Drive
North Chelmsford
MA 01863
phone: 1-978-251-1017
email: norbertschade@comcast.net
This archive was generated by hypermail 2b29 : Tue Jan 13 2004 - 10:04:28 EST