Re: [wsbpel] Issue - 149 - proposal to vote

[Alex Yiu <alex.yiu@oracle.com>]

Hi, Tony,

Those two attributes are already optional, which is XSD default.
And, about the "ref" thing:

<attribute ref="xml:lang"/>

That is a XML construct. That means we are refering and using a globally declared attribute and the QName of attribute name is "xml:lang".

Again, this pattern is a direct copy-and-paste from XSD documentation pattern.


I hope this clarifis the picture.




Regards,
Alex Yiu


Tony Fletcher wrote:

Dear Colleagues,

 

Sorry to be late responding to this issue, but having looked through the 'Proposal to Vote for Issue 149' again, I wonder if 'ref' is the best choice of name for this BPEL attribute, especially as 'ref' is also a 'keyword in XML Schema.

 

If it can be agreed now as a simple editing change I would suggest changing the attribute name 'ref' to 'language' (or some such).

 

Perhaps more controversially I would also suggest that both attributes on the "documentation" element are made optional.

 

<element name="documentation" id="documentation">
        <complexType mixed="true">
            <sequence minOccurs="0" maxOccurs="unbounded">
                   <any processContents="lax"/>
            </sequence>
            <attribute name="source" type="anyURI" use="optional"/>
            <attribute language="xml:lang" use="optional"/>
        </complexType>

 

Best Regards     Tony

A M Fletcher

 

Cohesions  (TM)

 

Business transaction management software for application coordination       www.choreology.com

 

Choreology Ltd., 68 Lombard Street, London EC3V 9LJ     UK

Tel: +44 (0) 1473 729537   Fax: +44 (0) 870 7390077  Mobile: +44 (0) 7801 948219

tony.fletcher@choreology.com     (Home: amfletcher@iee.org)

, I wonder if ref

-----Original Message-----
From: Alex Yiu [mailto:alex.yiu@oracle.com]
Sent: 31 July 2004 00:08
To: Alex Yiu
Cc: Satish Thatte; Francisco Curbera; wsbpel@lists.oasis-open.org
Subject: Re: [wsbpel] Issue - 149 - proposal to vote

Proposal to vote for Issue 149:

Proposed to add <documentation> to all BPEL extensible element.

Suggested description of <documentation> added to the specification text:
----------------------------
The content of <documentation> are for human-consumption. Example types for those content are: plain text, HTML and XHTML. On the other hand, tool-implementation specific information (e.g. the graphical layout details) should be added through elements and attributes of other namespaces, using the general BPEL extension mechanism. (i.e. bpws:tExtensibleElements).
----------------------------

Here is the suggested schema changes:
----------------------------

    <import namespace="http://www.w3.org/XML/1998/namespace" 
        schemaLocation="http://www.w3.org/2001/xml.xsd" />
     <element name="documentation" id="documentation">
        <complexType mixed="true">
            <sequence minOccurs="0" maxOccurs="unbounded">
                   <any processContents="lax"/>
            </sequence>
            <attribute name="source" type="anyURI"/>
            <attribute ref="xml:lang"/>
        </complexType>
    </element>
    <complexType name="tExtensibleElements">
        <annotation>
            <documentation>
        This type is extended by other component types
        to allow elements and attributes from
        other namespaces to be added.
       </documentation>
        </annotation>
        <sequence>
            <element ref="bpws:documentation" minOccurs="0" maxOccus="unbounded" />
            <any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
        <anyAttribute namespace="##other" processContents="lax"/>
    </complexType>
  

----------------------------