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] | [List Home]

Subject: XML Catalogs v1.1 submitted for OASIS Standard

OASIS Members:

The OASIS Entity Resolution TC has submitted the following specification, which is an approved Committee Specification, to be
considered as an OASIS Standard:

XML Catalogs v1.1

The TC's submission is attached below.

In accordance with the OASIS Technical Committee Process, the specification has already gone through a 30 day public review period:
OASIS members now have until the 15th of September to familiarize themselves with the submission below. OASIS members should give
their input on this question to the voting representative of their organization.

By the 16th of the month we will send out a Call For Vote to the voting representatives of the OASIS member organizations, who will
have until the end of the month to cast their ballots on whether this Committee Specification should be approved as an OASIS

The normative TC Process for approval of Committee Specifications as OASIS Standards is found at

Any statements related to the IPR of this specification are posted at:


Mary P McRae
Manager of TC Administration, OASIS
email: mary.mcrae@oasis-open.org
phone: 603.232.9090


Submission for OASIS Standard Vote

   1. Links to the approved Committee Specification in the TC's document repository.


   2.  The editable version of all files that are part of the Committee Specification


   3.  Certification by the TC that all schema and XML instances included in the specification, whether by inclusion or reference,
including fragments of such, are well formed, and that all expressions are valid;

I certify on behalf of the Entity Resolution TC that all schema and XML instances in the specification are well-formed and all
expressions are valid.

   4. A clear English-language summary of the specification;

XML documents and data often reference other external resources.  Often the referencing information is not sufficient to locate the
desired resource unambiguously, or the resource is not accessible at the given location at the time it is required, or it is
preferable that an alternate resource be used in place of the referenced resource. 

For example:

- External identifiers may require resources that are not always available. For example, a system identifier that points to a
resource on another machine may be inaccessible if a network connection is not available. 

- External identifiers may require protocols that are not accessible to all of the tools on a single computer system. An external
identifier that is addressed with the FTP protocol, for example, is not accessible to a tool that does not support that protocol. 

- It is often convenient to access resources using system identifiers that point to local resources. Exchanging documents that refer
to local resources with other systems is problematic at best and impossible at worst. 

- Incoming XML documents may reference customized versions of standard XML schemas.  To protect your systems, it is necessary to
remap the schema references so that known, trusted copies of the schemas are used. 

Entity Resolution is the process by which these resource references can be mapped to another version of the reference that can be
found or that is preferred for other reasons.  To address these issues, the OASIS XML Catalog specification defines an
application-independent entity catalog that maps external identifiers and URI references to (other) URI references. 

Entity resolution catalogs have already been widely implemented in much deployed software.  Promoting the OASIS XML Catalog
specification to an OASIS Standard is crucial for continued interoperability of XML applications.

   5.  A statement regarding the relationship of this specification to similar work of other OASIS TCs or other standards developing

The Entity Resolution TC is not aware of any similar work being done by OASIS TCs or any other standards developing organizations.
The TC is also not aware of any IPR claims that impinge on the output of the TC.

   6.  Certification by at least three OASIS member organizations that they are successfully using the specification;

The certifications have been sent to the TC mailing list and are available at
Sun Microsystems: 

   7.  The beginning and ending dates of the public review(s), a pointer to the announcement of the public review(s), and a pointer
to an account of each of the comments/issues raised during the public review period(s), along with its resolution;

The public reviews were:
18 June, 2003 - 18 July, 2003
resolution: the typo was fixed.

1 April, 2005 - 30 April, 2005
resolved at
resolved at

The ER TC also took into account other comments received outside of the review periods, accepting some and responding to others.

   8.  An account of and results of the voting to approve the specification as a Committee Specification, including the date of the
ballot and a pointer to the ballot;
Opening 15 July, 2005, closing 22 July, 2005
Results: 7 members voted, all in favor.

   9.  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;

The TC has not previously attempted to standardize any specification.

  10.  A pointer to the publicly visible comments archive for the originating TC;


  11.  A pointer to any minority reports submitted by one or more Members who did not vote in favor of approving the Committee

All members voted in favor of approving the Committee Specification.

Lauren Wood
Chair, Entity Resolution TC

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