[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [wsrp-wsia] [I#121] user-info extensions being <any>
This argues for requiring all service endpoints to view the space of user
profile extensions as flat. I would disagree that this is valuable and
there are multiple techniques available for dealing with deserializing such
objects. These include:
- WSDL extensions that declare the types
- Runtime attributes (xsi:type & xsi:schemaLocation) that declare the
types
- We have defined these as named sets of extensions ... I believe standard
(rather than dynamic) deserializers will be made available for common
extensions.
Many vendors may still choose to declare their extensions using a flattened
namespace. To require all extensions to be flattened loses the inherent
correlations in object/document hierarchies without a significant gain in
transferring/using the information.
Gil Tayar
<Gil.Tayar@webcol To: wsrp-wsia@lists.oasis-open.org
lage.com> cc:
Subject: [wsrp-wsia] [I#121] user-info extensions being <any>
10/27/2002 06:35
AM
Status: Active
Topic: user info
Class: Minor Technical
Raised by: Alejandro Abdelnur
Title: user-info extensions being <any>
Date added: 27-Oct-2002
Document Section: Interfaces v0.8/11.23
Description:
User-info custom attributes are elements of type <any>. This will make
difficult for consumers/producers to share custom user-info attributes.
The producer will most likely have to create a deserializer per
consumer for extended attributes.
If custom user-info attributes are strings they could be easily used by
all producers and entities by just doing a mapping.
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC