Re: [entity-resolution] draft blurb for the vote

["Anthony B. Coates" <abcoates@londonmarketsystems.com>]

How about also having something like:

     X. 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, good copies of the schemas are used.

Cheers, Tony.

On Tue, 23 Aug 2005 23:18:20 +0100, Paul Grosso <pgrosso@ptc.com> wrote:

> XML documents and data often reference other external resources.  Often  
> the
> referencing information is not sufficient to locate unambiguously the
> desired resource, the resource is not accessible at the given location  
> at a
> given time, or it is preferable that an alternate resource be used in  
> place
> of the referenced resource.
>
> For example:
>
>    1. 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.
>
>    2. External identifiers may require protocols that are not accessible  
> to
> all of the vendors' 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.
>
>    3. 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.
>
> 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 fairly widely implemented in
> much deployed software.  Promoting the OASIS XML Catalog specification  
> to an
> OASIS Standard is crucial for continued interoperability of XML
> applications.

-- 
Anthony B. Coates
London Market Systems Limited
33 Throgmorton Street, London, EC2N 2BR, UK
http://www.londonmarketsystems.com/
mailto:abcoates@londonmarketsystems.com
Mobile/Cell: +44 (79) 0543 9026
[MDDL Editor (Market Data Definition Language), http://www.mddl.org/]
[FpML Arch WG Member (Financial Products Markup Language),  
http://www.fpml.org/]
-----------------------------------------------------------------------
This Email may contain confidential information and/or copyright material  
and is intended for the use of the addressee only.  Any unauthorised use  
may be unlawful. If you receive this Email by mistake please advise the  
sender immediately by using the reply  facility in your e-mail software.   
Email is not a secure method of communication and London Market Systems  
Limited cannot accept responsibility for the accuracy or completeness of  
this message or any attachment(s). Please examine this email for virus  
infection, for which London Market Systems Limited accepts no  
responsibility. If verification of this email is sought then please  
request a hard copy. Unless otherwise stated any views or opinions  
presented are solely those of the author and do not represent those of  
London Market Systems Limited.