Re: [wsrp] Comment on Sec 5.1.21 Extension Part

[Rich Thompson <richt2@us.ibm.com>]

In previous discussions we explicitly
decided to not make this an XPath ... considering the ongoing confusion,
perhaps renaming the field "extendedTypes" would make the TC's
intent and decisions in this area clearer.

Rich

Subbu Allamaraju <subbu@bea.com>

05/24/06 01:33 PM

To	wsrp <wsrp@lists.oasis-open.org>
cc
Subject	[wsrp] Comment on Sec 5.1.21 Extension Part

[Sending on behalf of Nate Lipke - for some reason
his emails are bouncing.]

5.1.21 ExtensionPart Type
The locations field should be better defined.
We should standardize on a syntax and use stronger language. E.g. the 
locations field MUST be specified as ...
Options:

     * Use the schema type name  (maybe the change the name
to 
parentTypes reflect this): EmployerInfo
     * Use a hierarchical format for the extensions to point
the actual 
element: /getMarkup/userContext/profile/EmployerInfo
           o Possibly allow for more complex locations:
/*/userContext/profile/EmployerInfo
           o Should these be Qnames: 
/wsrp:getMarkup/wsrp:userContext/wsrp:profile/wsrp:EmployerInfo
           o Should we use a XPath or subset of
XPath?
           o XQuery?

A problem with the first choice is highlighted by the example given:
The example refers to "Contact" which is a type not a location.
There 
are two fields (businessInfo and homeInfo) with the Contact type under
UserProfile.  Does this refer to both fields? Also what message should
this field be expected in. And how can an implementor determine this 
from the the ServiceDescription.


Thanks,

Nate
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries
 and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted
 and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

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