[Fwd: [sdo] SDO-55 - Create an EntityResolver like concept for resolvingimported/included schemas]

[Blaise Doughan <blaise.doughan@oracle.com>]

Hello All,

Attached is the proposal for SDO-55.

SDO Core Spec:  4.13.4 - XSDHelper Interface

• Add the options parameter to the define methods.

SDO Java Spec:  2.17.2 - XSDHelper Interface

• Add the options parameter to the define methods.
• Add a section on SchemaInputResolver
  

-Blaise

sdo-java-3.0-spec-cd03-issue55.doc

SchemaInputResolver.zip

--- Begin Message ---

• From: Blaise Doughan <blaise.doughan@oracle.com>
• To: "sdo@lists.oasis-open.org" <sdo@lists.oasis-open.org>
• Date: Tue, 13 Jul 2010 10:22:55 -0400

Hello All,

Attached is the updated proposal.  The proposal does not contain the corresponding SchemaOutputResolver, as I have been advised there could be some IP issues due to my involvement in the JAXB spec.

-Blaise

Blaise Doughan wrote:

Hello All,

Attached are the proposed source changes.  I have renamed SchemaResolver to SchemaInputResolver as we may want to have a SchemaOutputResolver as well.  Of course we could have a SchemaResolver that does both input & output, thoughts?

-Blaise

Blaise Doughan wrote:

Hello All,

As discussed last week, most SDO implementations have some means of resolving System URIs.  There a couple of use cases for which this is useful:

• The user is loading there XML schema using a non-standard URI (i.e. pointing to somewhere on there class path).
• The user is specifying imported/included XML schemas using a relative path.

In the EclipseLink SDO implementation we have introduced the concept of a SchemaResolver.  This interface has the following signature:

public interface SchemaResolver {

    /**
     * @param parentXSD - The XSD doing the import or included (null for root schemas), the system id can be obtained to resolve relative URIs
     * @param namespace - The namespace portion of the import/include
     * @param systemID - The URI representing the location of the XML schema.
     */
    public javax.xml.transform.Source resolveSchema(javax.xml.transform.Source parentXSD, String namespace, String systemID);

}

Java SE also has the concept of an LSResourceResolver (http://java.sun.com/javase/6/docs/api/org/w3c/dom/ls/LSResourceResolver.html).  This approach has the benefit of working well with the javax.xml.validation APIs.

Hopefully we can get some discussion on this topic, in order to come up with a solution that works for everyone.

-Blaise

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 

SchemaInputResolver.zip

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 

--- End Message ---