OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tc-announce message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: [tc-announce] ebXML RS Committee Specification for consideration asOASIS Standard

OASIS members:

The OASIS ebXML Registry TC has submitted OASIS/ebXML Registry Services
Specification (RS) v2.0, which is an approved Committee Specification,
for review and consideration for approval by OASIS members to become an
OASIS Standard. In accordance with Section 2 of the OASIS Technical
Process (see http://oasis-open.org/committees/process.shtml) OASIS
members have one calender quarter to review this submission then 30 days
for voting. I will therefore call for a vote on 1 April 2002; each OASIS
member organization will have a single vote on the ballot.

[Note that there are two ebXML Registry specifications being submitted
to OASIS members: RIM and RS. While they are related to each other they
will be balloted separately.]

The OASIS TC has supplied the following required items for OASIS members
to review:

(a) a formal specification that is a valid member of its type

The OASIS/ebXML Registry Services Specification, v2.0, December 5, 2001
can be found at

The specification also includes the following ancillary documents, which
are referenced by the appendices of the Registry Services Specification.

Appendix A references:

Appendix B references:
  rim.xsd version
  query.xsd version
  rs.xsd version

Appendix D references:
  database.sql version 1.1
  storedProcedures.sql version 1.1

(b) appropriate documentation for the specification

The specification is self documenting; therefor no additional
documentation is required.

(c) a clear English-language summary of the specification

The ebXML Registry provides a stable store where information submitted
by a Submitting Organization is made persistent. Such information is
used to facilitate ebXML Business to Business partnerships and
transactions. Submitted content includes but is not limited to XML
schema and documents, process descriptions, ebXML Core Components,
context descriptions, UML models, information about organizations, and
software components. Metadata, used to describe the stored content, is
defined in a companion document, OASIS/ebXML Registry Information Model,
V2.0. the Registry Information Model. The interface to the Registry is
defined the OASIS/ebXML Registry Services Specfication, V2.0.

The Registry Services Specification provides a set of services that
define the communication messages between a registry server and its
client.  These services provide the support for the following

* movement through the life-cycle of a registered object (e.g., submit,
update, remove, depracate an object);
* the ability to query the metadata (and combinations) of object(s)
* the ability to manage the security policy of an object
* the definition of these services as an abstract web services in WSDL.

(d) certification by at least three OASIS member organizations that they
are successfully using the specification

See the following mail messages:

Information Technology Laboratory/National Institute of Standards and
Technology (US)
Sterling Commerce
Sun Microsystems

(e) an account of or pointer to votes and comments received in any
earlier attempts to standardize substantially the same specification,
together with the originating TC's response to each comment

This specification has not previously been submitted to OASIS
membership, so there are no previous votes or comments to respond to.

(f) a pointer to the publicly visible comments archive for the
originating TC

The archives of the TC mail list are available at
http://lists.oasis-open.org/archives/regrep/ TC meeting minutes are
available on the TC's web page at
http://oasis-open.org/committees/regrep/ To date, no comments have been
received through the public comment list for the Regitry TC; however,
some comments have been received through the ebXML-dev mailing list
which is archived at http://lists.ebxml.org/archives/ebxml-dev/

(g) a statement from the chair of the TC certifying that all members of
the TC have been provided with a copy of the OASIS IPR policy.

From Lisa Carnahan: "The TC chair certifies that all members have been
provided with a copy of the OASIS IPR policy. The mail message found at
http://lists.oasis-open.org/archives/regrep/200111/msg00087.html states
that all TC members must be made aware of the OASIS IPR policy and
directs them to the on-line version of the policy."

Karl F. Best
OASIS - Director, Technical Operations
978.667.5115 x206
karl.best@oasis-open.org  http://www.oasis-open.org

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC