Re: [wsrp] Some commets on CR304a

[Subbu Allamaraju <subbu@bea.com>]

I agree with the changes, and your suggestion for dropping StringArray. 
I don't see any use cases for keeping it.

In fact, if we decide not to let the V2 schema import V1 schema, we 
should consider not defining unused V1 types like NamedString and 
NamedStringArray in the V2 schema.

Subbu

Rich Thompson wrote:
> 
> Here is a modified version of the extra namespace definitions for 
> people's comments. I think this incorporates people's concerns todate 
> (not really related to v2, confusion with duplicated type names and the 
> name attribute should really be of type QName).
> 
> Let me know what people think ... particularly of the suggestion to drop 
> StringArray.
> 
> 
> 
> Rich
> 
> 
> *Subbu Allamaraju <subbu@bea.com>*
> 
> 05/25/05 01:35 PM
> 
> 	
> To
> 	wsrp <wsrp@lists.oasis-open.org>
> cc
> 	
> Subject
> 	[wsrp] Some commets on CR304a
> 
> 
> 	
> 
> 
> 
> 
> 
> Regarding the purpose and role of the extra namespace, Mike and others
> have pointed that types in this namespace could be used to provide some
> formal mapping between JSR168 and WSRP.
> 
> I can see the value, but I was wondering if anyone tried using
> NamedString to define such mappings, and willing to share some examples?
> 
> Based on some samples I tried out, it seems that we cannot guarantee
> interop between implementations with the current definition of
> NamedString. If there is a strong requirement for using this type in
> extensions, should we consider changing the type of the "name" attribute
> from "xs:string" to QName?
> 
> If we decide to keep this element, I would also suggest renaming
> NamedString to something else in the extra namespace to avoid confusion.
> 
> Rich - I noticed that the NamedString definitions in v1 and extra
> schemas are slightly different. The extra namespace uses value as an
> attribute while v1 defines value as an element. Was this intentional?
> 
> Subbu
> 
> 
> ---------------------------------------------------------------------
> 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
> 
> 
> 
> ------------------------------------------------------------------------
> 
> ---------------------------------------------------------------------
> 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