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


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

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

Subject: Re: [regrep] regrep 10/28/2005: Import Comment for Consideration on WSProfile

Duane Nickull wrote:
>You are talking at the schema level.  Any valid XML parser that supports
>XML Schema must have a handler to recognize and act upon and xs:import
>declaration.  It simply passes the URI to some other mechanism that
>retrieves it.  
>If the registry TC wanted to play a part in this, the storage of schema
>fragments in the registry, aliased using the mechanism Farrukh and Matt
>came up with, would work but I am not sure it offers any distinct
>advantage over storing them elsewhere.  Certainly as intrinsic objects,
>there persistence would be easier to monitor.
>Once the parser builds the in memory representation of the schema, the
>imported parts are present so there is no different to the applications
>using the parser output.
>These are really XML level issues, not WSDL, BPEL or registry ones.  As
>long as parsers are used in implementations that support xs:import and
>have access to the fragments there should be no problem.
Indeed WSDL and XML Schema Parsers will be necessary for any conforming 
implementation of WS Profile.

I tend to agree with Duane's assessment that " there should be no 
problem" in the scenario described.
Also I have implementation experience that supports that notion.

More inline below.
>-----Original Message-----
>From: Monica J Martin [mailto:Monica.Martin@Sun.COM] 
>Sent: Friday, October 28, 2005 2:39 PM
>To: ebXML Regrep
>Subject: [regrep] regrep 10/28/2005: Import Comment for Consideration on
>WS Profile
>Farrukh and registry experts,
>Here is what I found and you can assist in deciding if this is an item 
>that needs to be addressed in the Web Services Profile for Registry. 
>Take a WSDL that references an XML schema (.xsd) [Extend what is defined
>in WSDL v1.1 specification: http://www.w3.org/TR/wsdl#_example2]. I am 
>only providing the details and then we can decide if it needs redress 
>and if so when.
>In this example, the stock quote schema may itself import another schema
>fragment. I think you could see this for example with UBL where the 
>import a code list from somewhere else for their own core schema.
>My question is if the http://example.com/stockquote/stockquote.wsdl 
>imports the http://example.com/stockquote/stockquote.xsd, and we assume 
>that the .xsd also has an import: What impact does this have on the 
>Registry services if any. Is a WSDL validator set up to resolve the 
>import of the imported schema? Or, does the import of the imported 
>schema need to be specifically declared in the import statement in the 
>.wsdl? The XML schema specification partially addresses this [1].
Thanks for checking into this Monica.

There are two kinds of import at play here:

1. WSDL import statements

2. XML Schema import statements

The WSDL Parser MUST process (1) and the XML Schema parser MUST process (2).

This is not an issue at all assuming an impl is using WSDL and XML 
Schema Parsers.


>I think I indirectly brought this up because of significant discussions 
>in WS-BPEL. There were two schools of thought:
>  1. Require explicit import declaration of any imported document or
>     fragment. Case cited above. What we found in WS-BPEL that even
>     with explicit declaration of imports to an imported document,
>     collisions may occur at the XML schema level and conflict
>     detection may be required in implementation. I suggested in that
>     case an implementer's hint. [2]
>  2. Allow transitive imports and be silent on how this is resolved in
>     processing, i.e. there is no explict requirement for the import of
>     an imported document be specified in the WSDL.
>On a related subject, do we need to address if other element definitions
>of the WSDL are defined by WSDL extensibility (that uses QName 
>linking)?  Thanks.
>[1] Section 4 (XML Schema:
>   * The processor succeed in locating the *schema components*
>     <http://www.w3.org/TR/xmlschema-1/#key-component> transitively
>     required to complete an *assessment*
>     <http://www.w3.org/TR/xmlschema-1/#key-va> (note that components
>     derived from *schema documents*
>     <http://www.w3.org/TR/xmlschema-1/#key-schemaDoc> can be
>     integrated with components obtained through other means);.....
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  You may a link to this group and all your TCs in
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  You may a link to this group and all your TCs in OASIS


fn:Farrukh Najmi

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