RE: [wsrp-wsia] [I#121] user-info extensions being <any>

[Gil Tayar <Gil.Tayar@webcollage.com>]

Alejandro,

You may have missed the idea of using <xsd:any />. The idea is _not_ that
this makes the new field a formless blob of an unknown type, but rather the
inverse - it enables the Producer to create an extension _of whatever type
they like_, which enables the Consumer to use and validate the field
according to the type the Producer sets. So if the extension field is
"Spouse name" then the Producer can set type to string, and if the field is
"Spouse age" then the Producer can set the type to "0-120" (at least for the
foreseable future :->).

Even more so, the WSDL/Schema published by the Producer can include this
field not as an <xsd:any />, but with the appropriate name and type, and
thus allow the Consumer using its WSDL appropriate usage, while still
allowing the "generic" client to use it.

Gil

-----Original Message-----
From: Gil Tayar [mailto:Gil.Tayar@webcollage.com]
Sent: Sun, October 27, 2002 13:35
To: wsrp-wsia@lists.oasis-open.org
Subject: [wsrp-wsia] [I#121] user-info extensions being <any>


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>