Re: [ebxml-bp] Specification xml fragment recheck in specification andits results: issue raised, please comment

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

Dale and team,
In line with our discussions with OASIS last week and to proceed, I've 
expanded our read-me from Committee Draft [original at 1].  I'd propose 
we inlcude this with the set of packages. For the errata, I would 
tentatively propose that we provide both examples recognizing the 
tooling preferences that may exist. If you (Dale) can clarify the 
examples, I can compile the errata for our consideration.  I'll have the 
other documents posted by in the morning.

Thanks.

[1] 
http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/email/archives/200604/msg00056.html 
(see: Readme explanation)

>moberg: In preparation for deciding about moving the CS to Oasis Specification,
>I was asked to check the examples in the specification once again....
>
>Unfortunately, in the .doc format, for section 3.4.6.3 on using
>xinclude, some of the quotation marks have been converted to the
>matching quotation mark values, and if the fragment is checked in Oxygen
>7.0, for example, a well-formedness complaint is issued. Also, in that
>example, the xinclude statement is commented out (probably a result,
>ironically, of checking the fragment for validity; validity check
>requires that the xinclude insertions be carried out before the schema
>check). This means the example doesn't actually technically have an
>xinclude in it, but just a comment. Will people be confused? 
>
>From now using
><xi:include href="signals-package-2.0.3.xml" parse="xml"
>        xpointer="xpointer(/ProcessSpecification/Package[1])"/>
>
>to using
><xi:include href="signals-package-2.0.3.xml" parse="xml"
>        xpointer="element(/1/1)"/>
>
> 
>
>[This assumes that the file "signals=package-2.0.3.xml" is in the
>current working directory, usually, but implementers should eventually
>figure that out.
>  
>

======================
Changes and/or errata relative to ebBP v2.0.3 Committee Specification
28 April 2006

In preparation for OASIS Standard, the ebBP TC identified one clarification
in an example in Section 3.4.6.3 where the xinclude statement was commented out.
A change has been issued as an errata and can be found under 
at our public web site, at: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebxml-bp,
under: Technical Work Produced by the Committee.

Note: In general in examples, should required elements be deleted,
a comment is included.  ID values for an IDREF data type may occur 
outside of this specification and the example, and may be identified
when a tool is used. 

======================
ebBP v2.0.3 Promotion to Committee Specification vote
18 April 2006

Note, in line with this specification promotion with the adjoining set of packages,
the OASIS ebBP team found two editorial changes required before promotion to Committee Specification
vote:
1. Non-normative references to other specifications (WSDL, WS-Addressing)
2. Non-normative language changes to the table in Appendix B for ebBP-CPPA mapping

References: 
a. Email re: Appendix B changes: http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/email/archives/200604/msg00042.html
	(Public: http://lists.oasis-open.org/archives/ebxml-bp/200604/msg00042.html)
b. Meeting Minutes for 11 and 18 April 2006: See, 
 11 April 2006: http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/17687/ebxmlbp-v2.0.3-Minutes-041106.txt
	(Public: http://www.oasis-open.org/committees/download.php/17687/ebxmlbp-v2.0.3-Minutes-041106.txt)

 18 April 2006: http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/17750/ebxmlbp-v2.0.3-Minutes-041806.txt
	(Public: http://www.oasis-open.org/committees/download.php/17750/ebxmlbp-v2.0.3-Minutes-041806.txt)
	
c. Diff documents held at: http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/17714/ebxmlbp-v2.0.3-Spec-cd-diff-en.zip
	(Public: http://www.oasis-open.org/committees/download.php/17714/ebxmlbp-v2.0.3-Spec-cd-diff-en.zip)

A super majority vote (7 of 9 voting members, no abstain or no votes cast) was successful on 18 April 2006 to:
1. Make changes proposed and approved. Change status to all packages to 'Committee Draft.'
2. Promote all the packages to OASIS for initiation of Committee Specification vote for ebBP v2.0.3.