[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 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.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]