RE: [wsbpel] Issue 88 - comments to proposal

["Chris Keller" <chris.keller@active-endpoints.com>]

Hi Paco,

One other issue I thought of was the indirect nature of property aliases.
If we make imports mandatory, we should note that property aliases must also
occur in the list imports even though the BPEL process doesn't directly
refer to them.

- Chris


-----Original Message-----
From: Francisco Curbera [mailto:curbera@us.ibm.com] 
Sent: Wednesday, July 20, 2005 8:45 AM
To: wsbpel@lists.oasis-open.org
Subject: [wsbpel] Issue 88 - comments to proposal


Resending with subject line...

----- Forwarded by Francisco Curbera/Watson/IBM on 07/20/2005 08:44 AM
-----
 

                      Francisco Curbera

                                               To:
<wsbpel@lists.oasis-open.org>

                      07/19/2005 11:16         cc:

                      PM                       From:     Francisco
Curbera/Watson/IBM@IBMUS                                               
                                               Subject:

 




Diane was kind enough to let me know the summary of comments that came up
during the discussion of issue 88 last week (which I missed). Here are my
comments to those comments:

   "consider changing import name since its used in different ways by other
   specs". We discussed this before. Import in BPEL does fundamentally the
   same thing as import in WSDL and XSD. Using a different word will only
   confuse everyone.
   "add a clarification that location attribute is a "hint" vs physical
   location as in xsd import". I don't understand the "vs physical location
   in xsd". SchemaLocation is a hint as well.
   "clarify whether referencing of wsdl artifacts from indirect import is
   allowed or not." This is already clarified in my updated proposal. The
   answer is "yes".
   "in 1B add "for example" to the text in the parenthesis about xsd
   redefinition". OK


Paco


---------------------------------------------------------------------
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