Service contract definition

[marklittle]

On the premise that something is better than nothing, here's a proposal for an initial Service Contract Definition schema.

Contract definition information will be peculiar to the type of service. However, there will always be some commonality. Therefore, the basic contract information we need to maintain is:

- the type of the service
- the sub-type of the service
- the version of the service
- the protocols accepted by the service (essentially a list of EPRs, which can themselves contain additional information)
- protocol specific data (e.g., WSDL for Web Services EPRs)
- service specific contract information
- policies (e.g., is the service transactional, is it secure, etc. Some of this information may be duplicated elsewhere in the contract)
- meta-data (basically a catch-all bag for anything we may want to stick here for now, such as availability, performance, etc.)

Here's the proposed schema ...

<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.example.org/NewXMLSchema" xmlns:tns="http://www.example.org/NewXMLSchema">
<xs:complexType name="ContractDefinition">
<xs:sequence>
<xs:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="lax"/>
<xs:element name="serviceType" type="xs:anyURI"/>
<xs:element minOccurs="0" name="serviceSubType" type="xs:anyURI"/>
<xs:element minOccurs="0" name="version" type="xs:anyURI"/>
<xs:element minOccurs="0" name="protocols" type="ProtocolData"/>
<xs:element minOccurs="0" name="policies" type="wsp:Policy"/>
</xs:sequence>
<xs:attribute ref="wsu:Id" use="optional"/>
</xs:complexType>

<xs:complexType name="ProtocolData">
<xs:sequence>
<xs:element name="epr" type="EPR"/>
<xs:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="lax"/>
</xs:sequence>
</xs:complexType>

[arvinder]

Mark, w.r.t. the jms schemas and the one defined above, where abouts in svn do you want to put it ? Can you do this for the schema above so i can add the jms stuff into the same dir ?

[marklittle]

I was just going to create an xml dir. I'll do that later today.

[arvinder]

I've added some xsd's under the root/xml folder. If you go through the top level jms-epr.xsd, i have some comments at the bottom about the inclusion of other xsd's, which may fit together nicely. Anyway, when you havce some time take a look.

[arvinder]

Ack, I have just seen this has been allocated to "Aron Sogor", in anycase I have added a comment in jira and checked in the files anyway.

[marklittle]

Arvinder, I think you're comments are for something else and not specifically Contract Definition ;-)

Anyway, I'll check JIRA tomorrow when I'm in the office. I thought I'd selected you, but maybe my finger slipped.

[marklittle]

Looks fine to me. I'm updating the contract.xsd now.