Working in small technical committees on well-constrained problems can be really rewarding; the small group allows for a certain amount of fun in the meetings and everyone knows they have a role to play. I chair the OASIS Entity Resolution TC, which is working on XML Catalogs.
The idea of catalogs has been around for a long time, it was one of the first pieces of work to come out of SGML Open, the precursor to OASIS. We’ve updated them for XML and use on the Web and although we spend a lot of time explaining that entity resolution is not restricted to XML entitities and indeed we use the word “entity” in the more general sense of the word, i.e. we really mean “resource” in today’s terminology (see the FAQ for more on this), I think it’s a good piece of work. Mind you, having Norm edit it and write code to implement it does help immensely.
So now it’s time to vote! We need another 44 OASIS member companies to vote (we need to reach a total of 47 “Yes” votes to pass) — so please pass this on to any voting reps you know (yes, this is a shameless lobbying act for something I think is worthwhile). The ballot is at Approve XML Catalogs v1.1 as an OASIS Standard. Many thanks!
Some supporting information from the TC:
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.