Updated specification schema DTD

Attached are DTDs based on both of Cory's models. The "fewer boxes" makes
the DTD look a little cleaner, but doesn't effect the XML much. The other
effect of this model is that is changes the BusinessTransaction from having
RequestingBusinessActivity and RespondingBusinessActivity to having Request
and Response*.

On a separate topic, the attached DTDs begin to use ID and IDREF type
attributes. These are useful for a number of reasons 1. Provides primary key
for an element 2. Provides reference key for attributes of other elements.
3. Requires consistency among the names (e.g. Cant use an IDREF equal to
something that isn't an ID and cant have the same ID used twice). However,
there is one side affect, the ID and IDREF scope is the entire XML document
and therefore doesn't meet our stated criteria that an AuthorizedRole and
BusinessTransactionActivity are scoped by the BinaryCollaboration.


 <<ebXMLSpecificationDTD097.dtd>>  <<Simple_097.xml>>  
<<ebXMLSpecificationDTD097B.dtd>>  <<Simple_097B.xml>> 
________________________________________________________________
Kurt Kanaskie
Lucent Technologies
[email protected]
(610) 712-3096

 -----Original Message-----
From: 	Cory Casanave [mailto:[email protected]] 
Sent:	Tuesday, March 13, 2001 5:59 PM
To:	[email protected]; [email protected]
Subject:	Updated specification schema model

 << File: Spec097.pdf >> << File: Spec097b.pdf >> The enclosed "Spec097"
represents the model as I think consensus has evolved
over the last couple of meetings for discussion at the next MM phone
meeting.  Just to keep things lively, I have also included a version that
can represent the same model with fewer boxes by putting the "activities"
and "document transfer " together.   (Spec097b)

  <<Spec097.pdf>>  <<Spec097b.pdf>> 

ebXMLSpecificationDTD097.dtd

Simple_097.xml

ebXMLSpecificationDTD097B.dtd

Simple_097B.xml