ebBP 2/9/2005: Document Envelope Notation (wd Section 4.6.8.1)

["Monica J. Martin" <Monica.Martin@Sun.COM>]

In yesterday's TC call, we discussed what is used - name or nameID for 
the expression when Document Envelope Notation is used.  Given our 
decision and discussion, here is the proposed text:

Section 4.6.8.1:

FROM: This specification does not limit the type and number of languages 
a BSI MAY support for variables or condition expressions. However, for 
conformance, a BSI is required to support at least the XPath language, 
as well as the DocumentEnvelopeNotation. An XPath expression MAY involve 
the content of any DocumentEnvelope received prior to the transition 
within the scope of the current Binary (Business) Collaboration 
instance. XPath will also operate on the result of rendering EDI into 
XML per ISO/DIS20625. The DocumentEnvelopeNotation is simply defined as 
the name or ID of a document envelope.

TO: This specification does not limit the type and number of languages a 
BSI MAY support for variables or condition expressions. However, for 
conformance, a BSI is required to support at least the XPath language, 
as well as the DocumentEnvelopeNotation. An XPath expression MAY involve 
the content of any DocumentEnvelope received prior to the transition 
within the scope of the current Binary (Business) Collaboration 
instance. XPath will also operate on the result of rendering EDI into 
XML per ISO/DIS20625. [change] WHEN the DocumentEnvelopeNotation is used 
FOR THE EXPRESSION, the nameID of the DOCUMENT ENVELOPE SHOULD BE USED. 
MORE DETAILS ON THE USE OF NAMEID FOR REFERENCING IS FOUND IN SECTION 
4.11.1. [end-change]

To rationalize this change to the proposed draft schema, the following 
two annotations should be changed:
1) On ConditionExpressionType:
CHANGE ANNOTATION FROM:
<xsd:annotation>
            <xsd:documentation>The type related to the expression 
element. XPath or XSLT may be used
                as expression languages in the Condition Expression. The 
Condition Expression
                relates to the DocumentEnvelopeNotation defined in the 
v2.0 technical specification.
                For conformance, a BSI is required to support at least 
the XPath language, as well
                as the DocumentEnvelopeNotation (name and nameID of a 
Document Envelope), while use
                of XSLT is also recommended. Use of XPath and XSLT may 
be beneficial when variables
                are used. Note: This complexType was added in 
v2.0.</xsd:documentation>
        </xsd:annotation>

CHANGE ANNOTATION TO:
<xsd:annotation>
            <xsd:documentation>The type related to the expression 
element. XPath or XSLT may be used
                as expression languages in the Condition Expression. The 
Condition Expression
                relates to the DocumentEnvelopeNotation defined in the 
v2.0 technical specification.
                For conformance, a BSI is required to support at least 
the XPath language, as well
                as the DocumentEnvelopeNotation [change] (nameID of a 
Document Envelope), [end-change] while use
                of XSLT is also recommended. Use of XPath and XSLT may 
be beneficial when variables
                are used. Note: This complexType was added in 
v2.0.</xsd:documentation>
        </xsd:annotation>

2) On Variable:
CHANGE ANNOTATION FROM:
    <xsd:annotation>
            <xsd:documentation>A semantic element that supports the 
effective use of conditional
                constraints. The variable can be accessed by external 
elements.
                businessTransactionActivityRef and businessDocumentRef 
point to what context and
                documents are relevant to Condition Expression 
evaluation. Variable assumes type, if
                any, from expression evaluation. This element, for 
example, could be associated with
                a logical Business Document. The Condition Expression 
relates to the
                DocumentEnvelopeNotation. For conformance, a BSI is 
required to support at least the
                XPath language, as well as the DocumentEnvelopeNotation 
(name and nameID of a
                Document Envelope), while use of XSLT is also 
recommended. Use of XPath and XSLT may
                be beneficial when variables are used. Note: This 
element was added in v2.0.</xsd:documentation>
        </xsd:annotation>

CHANGE ANNOTATION TO:
    <xsd:annotation>
            <xsd:documentation>A semantic element that supports the 
effective use of conditional
                constraints. The variable can be accessed by external 
elements.
                businessTransactionActivityRef and businessDocumentRef 
point to what context and
                documents are relevant to Condition Expression 
evaluation. Variable assumes type, if
                any, from expression evaluation. This element, for 
example, could be associated with
                a logical Business Document. The Condition Expression 
[change] ALSO relates [end-change] to the
                DocumentEnvelopeNotation. For conformance, a BSI is 
required to support at least the
                XPath language, as well as the DocumentEnvelopeNotation 
[change] (nameID of a
                Document Envelope) [end-change], while use of XSLT is 
also recommended. Use of XPath and XSLT may
                be beneficial when variables are used. Note: This 
element was added in v2.0.</xsd:documentation>
        </xsd:annotation>