-----Original Message-----
From: Darran Rolls [mailto:Darran.Rolls@waveset.com]
Sent: Wednesday, August 27, 2003
5:53 PM
To: provision@lists.oasis-open.org
Subject: [provision] Doc for SPML
v1.0 OASIS vote
Folks
As discussed on last Monday's call, we need to submit the
following information for the OASIS voting process next month. Please
review. I'd like to send this out next Wednesday. We can discuss
any questions and issues on Mondays committee con-call.
Summary of specification
In late 2001, the OASIS Provisioning
Services Technical Committee (PSTC) was formed to define an XML-based framework
for exchanging user, resource, and service provisioning information. The
resulting specification defines the concepts, operations deployment and XML
schema for an XML based request and response protocol for provisioning.
This specification consists of three documents as follows:
- cs-pstc-spml-core-1.0.pdf - Core specification
document; contains both normative and non-normative description of the 1.0
specification
- cs-pstc-spml-bindings-1.0.pdf - Bindings document;
contains normative description of SOAP/HTTP & file based transport
bindings
- cs-pstc-spml-schema-1.0.xsd - XML Schema; contains the
definition of message and protocol formats for SPML V1.0
These three documents together form the SPML V1.0
specification and are available at [1], [2] and [3] respectively.
[1] http://www.oasis-open.org/committees/download.php/2395/cs-pstc-spml-core-1.0.pdf
[2] http://www.oasis-open.org/committees/download.php/2394/cs-pstc-spml-bindings-1.0.pdf
[3] http://www.oasis-open.org/committees/download.php/2396/cs-pstc-spml-schema-1.0.xsd
Certification of use in line with OASIS IPR
policy
So far, the following three vendors have certified their use
of the SPML V1.0 specification in accordance with the OASIS IPR policy. I
believe other members will want to go on record with the same assertion; the
following three meets the TC process requirement:
- Waveset Technologies at [4]
- Business Layers at [5]
- OpenNetwork Technologies [6]
- Computer Associates [6.1]
- BMC [6.2]
[4] http://www.oasis-open.org/archives/provision/200306/msg00009.html
[5] http://www.oasis-open.org/archives/provision/200306/msg00011.html
[6] http://www.oasis-open.org/archives/provision/200306/msg00012.html
[6.1] http://lists.oasis-open.org/archives/provision/200308/msg00008.html
[6.2] http://lists.oasis-open.org/archives/provision/200308/msg00014.html
Issues and Resolution
During the open OASSI wide review period we received no
comments from OASIS members outside the PS-TC. Internally there were
several issues raised during the adoption of CS status, the latter of thee are
identified in the table below with supporting draft/revision details. The
TC maintains an issues list at [7]. On 5/19/2003 the TC voted to table
the current outstanding issues list for the 1.1 specification process [8].
[7] http://www.oasis-open.org/committees/download.php/3183/pstc-issues-list-05.doc
[8] http://www.oasis-open.org/apps/org/workgroup/provision/download.php/2127/pstc-minute-05192003.htm
Comments Archive
A full list of comments and discussion has been maintained
throughout the process of generating the 1.0 specification. The TC held
four face-to-face meeting in the 1.0 specification process, each of which was
attended to quorum and recorded in verified minutes in accordance with TC
process. The comment archive and posting of minutes is available at [9].
[9] http://www.oasis-open.org/apps/org/workgroup/provision/email/archives/index.html
Certification on IPR Policy
As chair of the PS-TC I can certify that each contributing
member has been clearly provided with a link to the OASIS IPR Policy web page
at and to the best of my knowledge none has or intends to submit claims against
this specification.