Issue 192: Applying extensibility uniformly to <partnerLinkType>, <role>, <property> and <propertyAlias>

["Tony Fletcher" <tony_fletcher@btopenworld.com>]

Title: Message

This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if the TC accepts it as identifying a bug in the spec or decides it should be accepted specially. Otherwise it will be closed without further consideration (but will be marked as "Revisitable")

The issues list is posted as a Technical Committee document to the OASIS WSBPEL TC pages on a regular basis. The current edition, as a TC document, is the most recent version of the document entitled in the "Issues" folder of the WSBPEL TC document list - the next posting as a TC document will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.    

---

Issue 192: Applying extensibility uniformly to <partnerLinkType>, <role>, <property> and <propertyAlias>

Status: received
Date added: 19 Feb 2005
Categories: Syntax and validation
Date submitted: 19 February 2005
Submitter: Alex Yiu
Description: I am double checking our current XSD grammar for <partnerLinkType>, <role>, <property> and <propertyAlias>.

I found out that those constructs are actually NOT extensible, unlike most of other BPEL constructs. I was quite surprised by that.

I think we should apply extensibility uniformly to <partnerLinkType>, <role>, <property> and <propertyAlias>.
Submitter's proposal: None yet.
Changes: 19 Feb 2005 - new issue

---

 Best Regards,

Tony                          

	Tony Fletcher Technical Advisor Choreology Ltd. 68, Lombard Street, London EC3V 9L J   UK
	Phone:	+44 (0) 1473 729537
	Mobile:	+44 (0) 7801 948219
	Fax:	+44 (0) 870 7390077
	Web:	www.choreology.com
Cohesions™
Business transaction management software for application coordination
Work: tony.fletcher@choreology.com
Home: amfletcher@iee.org