Re: ebBP 2/23/2005: Early Notice of Pre-Committee Draft OASISebXML BPSS Tech Spec (ebBP!)

[YANO Keisuke (矢野啓介 ) <yano@jp.fujitsu.com>]

Monica,

Thank you for the notification of pre-Committee Draft.

My comments are below.

---
* Comment: In XML fragments through the spec, nameID attribute
values should start with a letter, not a digit, because of the 
xsd:ID type definition.

* Comment: line 404:
"A Business Collaboration is a set of Business Transactions"
should be "a set of Business Activities executing Business Transactions".
IMO, the distinction between Business Transaction and Business Transaction
Activity is a critical point to understand BPSS.

* Comment: Appendix A should conform to the BPSS 2.0 schema.

* Comment: Section 4.6.4: It is not clear to me what are
specificationVersion and instanceVersion. My guess is that
specificationVersion is the version of BPSS (that is, it will be 2.0)
and instanceVersion is the version of the BPSS instance identified
by the uuid attribute.  If that guess is right, line 730 should be
"Versioning by specification schema".

* Comment: line 1118: mimeType="XML" should be 
mimeType="application/xml". (see RFC 3023)

* Comment: line 1118-1120: This Attachment element instance
lacks a Specification element mandatory by the schema.
Suggestion: Remove Specification from Attachment in the schema
because the referenced BusinessDocument by Attachment has a
Specification. Also, the location attribute of the Specification 
element should be optional because some types of attachment such
like images don't have the location of specification.

* Comment: line 1183: "The is no limit ..." should be
"There is no limit ..."

* Comment: line 1207: "This examples shows ..." should be
"This example shows ..."

* Comment: line 1435: There must be one more Performs element
because BTA has at least two Performs elements according to the
schema. (Or, the schema should be changed so that minOccurs of
Performs in BusinessTransactionActivityType should be "1".)

* Comment: line 1436: TimeToPerform element should be placed
before Performs elements according to the schema.

* Comment: line 1229: TimeToPerform element should be placed
before Performs elements according to the schema.

* Comment: line 1476: "An XOR a fork means ..." should be
"An XOR fork means ..."

* Comment: line 1480: "Several path are ..." should be 
"Several paths are ..."

* Comment: line 1488: "A fork has a timeToPerform element"
should be "A fork has a TimeToPerform element". (The element name
starts with 'T', not 't'.)

* Comment: line 1502: "timeToPerform attribute" should be
"TimeToPerform element".

* Comment: line 1504: In the table, the comment of OR-Fork
and waitForAll="false" Join says "The duration of the fork
TimeToPerform SHALL NOT be null." This restriction should be 
relaxed. (Please consider the case that one path in a Fork-Join
block is a normal sequence and another path is optional. In this
case, we don't need TimeToPerform timeout to reach the Join.)

* Comment: line 1532-1533: Which expression language is used here?

* Comment: line 1569: There is not Section 6.4 in the spec.
Examples of timing redefinition should be provided here or in 
another section.

* Comment: Schema: The TimeToPerform element should have a reference
to a Variable, not the Variable element, for late binding.

* Comment: line 1625-1626, 1630-1631, 1645-1646: ToLink
elements don't conform to the schema. These examples are intended
to use guards in ToLink element, however conditionGuard attribute
is allowed only in FromLink element according to the schema.
Also, the ToLink elements of line 1645-1646 have expression
attribute, while a condition expression have to be expressed as
an element.

* Comment: line 2129: "IsIntelligibleCheckRequired" should
be "isIntelligibleCheckRequired" (starts with lower case 'i') like 
line 2132.

* Comment: line 2145: "IsAuthorizationRequired" should be
"isAuthorizationRequired" (starts with lower case 'i').

* Comment: line 2155: "IsNonRepudiationRequired" should be
"isNonRepudiationRequired" (starts with lower case 'i').

* Comment: line 2181: "An expression whose evaluation results
in TRUE or FALSE." should be "A parameter that takes the value 
true or false." because isPositiveResponse is a boolean attribute.

* Comment: line 2249-2250: "defined as the name or ID of a 
document envelope" should be "defined as the nameID of a document
envelope" as described in line 1564-1565.

* Comment: line 2261, 2265-2266: Attribute names "Name" and "NameID"
should be "name" and "nameID" respectively, according to the schema.

* Comment: line 2829: "BSIMAY" should be "BSI MAY".

* Comment: line 2903: Please correct my name.  "Yeisuke" should be
"Keisuke" (the first letter is 'K', not 'Y').

---

Thanks,

Yano K.