Hi Danny,
Thanks for RFC styling reminder.
This is just a directional vote. There would be spec text vote later.
Regards,
Alex Yiu
Danny van der Rijn wrote:
* Abstract Process of any profile should be valid regarding to the grammar in the AP common base
I would think that "should" should either be "SHOULD" or "MUST." I
prefer MUST.
Mehta, Vinkesh (US - Austin) wrote:
Modified
proposal as approved on Jan 11th, 2006 F2F ( copied from IRC):
===========================
Prefix convention used in this email:
* prefix "abs" refers to "...abstract-process-base-URI..."
* prefix "exec" refers to "...exec-process-base-URI..."
* prefix "template" refers to "...template-profile-URI..."
Schema details for the AP common base:
* There will be 2 distinct namespaces for Exec and Abs Process
* Provide XSD definitions for Exec Process
* Provide XSD definitions for the base of Abs Process
* Since the grammars of Exec Process and Abs Process Base are so different, there will be no attempt to share XSD details between the Abs Process Base and Exec Process. XSD for Abs Process Base will be produced, once after XSD for Exec Process is finished.
Clarification to the AP common base:
* A profile MAY provide additional grammar or XSD to perform syntax validation specific to the profile
* A profile MAY provide its extension construct of its namespace to allow additional information added to the Abstract Process.
* Abstract Process of any profile should be valid regarding to the grammar in the AP common base
Addition to Process-Template Profile:
* Provide a schema specific to process-template; attempt will be made to share details between XSDs for Exec BPEL and Process-Template (including modularization and changes in Exec BPEL to make parts of its definition more reusable by Process-Template).
* Adding an extension attribute [ template:createInstance ("yes"|"no") ] to <abs:opaqueActivity>
Addition to Visible Behavior Profile:
* The Visiable Behavior profile may provide an extra set of schema / grammar to provide extra syntax validation.
===========================
Hi all,
Some of us have had some off-line discussion. Here is an updated
proposal for Issue 82.1 (directional vote):
===========================
Prefix convention used in this email:
- prefix "abs" refers to
"...abstract-process-base-URI..."
- prefix "exec" refers to "...exec-process-base-URI..."
- prefix "template" refers to "...template-profile-URI..."
Schema details for the base:
- There will be 2 distinct
namespaces for Exec and Abs Process
- Provide XSD definitions for Exec Process
- Provide XSD definitions for the base of Abs Process
- Since the grammars of Exec Process and Abs Process Base are
so
different, there will be no attempt to share XSD details between the
Abs Process Base and Exec Process. XSD for Abs Process Base will be
produced, once after XSD for Exec Process is finished.
Clarification to the base:
- A profile MAY provide
additional grammar or XSD to perform syntax validation specific to the
profile
- A profile MAY provide its extension construct of its
namespace
to allow additional information added to the Abstract Process.
Addition to Process-Template Profile:
- Provide a schema specific to
process-template; attempt will be made to share details between XSDs
for Exec BPEL and Process-Template (including modularization and
changes in Exec BPEL to make parts of its definition more reusable by
Process-Template).
- Adding an extension attribute [ template:createInstance
("yes"|"no") ] to <abs:opaqueActivity>
===========================
Thanks!
Regards,
Alex Yiu
This message (including any
attachments) contains confidential information intended for a specific
individual and purpose, and is protected by law. If you are not the
intended recipient, you should delete this message.
Any disclosure, copying, or
distribution of this message, or the taking of any action based on it,
is strictly prohibited. [v.E.1]
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
|