W3C home > Mailing lists > Public > public-ws-chor@w3.org > September 2004

Re: Import/Include - a proposal

From: Monica J. Martin <Monica.Martin@Sun.COM>
Date: Thu, 16 Sep 2004 11:21:15 -0700
To: Nickolas Kavantzas <nickolas.kavantzas@oracle.com>
Cc: Steve Ross-Talbot <steve@enigmatec.net>, public-ws-chor@w3.org
Message-id: <4149D99B.3000500@sun.com>


>Kavantzas: This is the current edited text from Greg based on Yves instructions. Are you confortable with it?
>
>2.4.6.2 Including Choreographies
>Choreographies or fragments of Choreographies can be reused in any Choreography definition by using XInclude [ref to Xinclude 1.0].
>This mechanism allow the merge of several XML infosets into one that
>becomes the Choreography definition.
>
>A CDL processor MUST resolve all XInclude declaration in the Choreography
>definition before doing any CDL-related processing.
>
>Example:
>
><choreography name="newChoreo" root="true">
>...
>   <variable name="newVariable" informationType="someType"
>             role="randomRome"/>
>   <xi:include href="genericVariableDefinitions.xml" />
>   <xi:include href="otherChoreography.xml"
>               xpointer="xpointer(//choreography/variable[1]) />
>...
></choreography>
>
mm1: Nick, thanks for your efforts. This does answer most of the 
questions raised for a syntactic approach to include. During the 
discussions on the related issues, there were three specific points 
related to Xinclude that may be important as implementerís notes:

    * The Xinclude only addresses syntactic inclusion.
    * The namespace of the included item is retained. That could result
      in a schema error recognized during CDL validation.
    * Xinclude requires the making the baseURI property required instead
      of optional.

Thanks.
Received on Thursday, 16 September 2004 18:21:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 01:01:05 GMT