Re: [asap] Discussion on state datatype

["David RR Webber" <david@drrw.info>]

Keith,

 

Two things - an interesting list of states - but I think it would pay to

discuss this list with the BPSS team, ebMS team and also the BCM

team.

 

A common list would be more effective.

 

On the schema side - if you want to do extended value checking and

semantics - then you should look at creating an OASIS CAM template

for ASAP.  This would give you significantly better fine-grained control

of the content and structure - and also allow you to use context to

drive this.

 

Check out the CAM brochure from

http://www.oasis-open.org/committees/cam

 

The CAM team would be happy to work with you to develop a

CAM template for ASAP.

 

Thanks, DW

 

----- Original Message -----

From: Keith Swenson

To: ASAP (E-mail)

Sent: Sunday, February 29, 2004 12:07 AM

Subject: [asap] Discussion on state datatype

We have a datatype definition for "State" to be:

 

<xsd:simpleType name="stateType">
  <xsd:restriction base="xsd:string">
    <xsd:enumeration value="open.notrunning" />
    <xsd:enumeration value="open.notrunning.suspended" />
    <xsd:enumeration value="open.running" />
    <xsd:enumeration value="closed.completed" />
    <xsd:enumeration value="closed.abnormalCompleted" />
    <xsd:enumeration value="closed.abnormalCompleted.terminated" />
    <xsd:enumeration value="closed.abnormalCompleted.aborted" />
  </xsd:restriction>
</xsd:simpleType>

The purpose behind making states as a sequence of dot separate values is that individual implementation are supposed to be able to make extensions to this set.  For example, a company could make  "open.notrunning.beingBackedUp" or some such state.  This 'adds value' to the state.  A partner of their may be able to understand the nuance of beingBackedUp or might not.  Never the less, anyone will understand the beginning part  "open.notrunning".

 

Can a XML Schema be extended in this way?  How do I write the schema that says: "use those 7 values, and then add to them this new 8th value".   Do I need to define the entire set again, and call it "stateType2".  Can I say that stateType2 is stateType with an added value.

 

If we can not extend the state type in this way, then we may need to stay with state type being a simple string.

 

-Keith

Keith D Swenson, kswenson@us.fujitsu.com
Fujitsu Software Corporation
1250 E. Arques Avenue, Sunnyvale, CA 94085
(408) 746-6276   mobile: (408) 859-1005