OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-wsia message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: [wsrp-wsia] [I#???] inconsistent ResourceList handling


I received one other email about this area not being clear enough. My 
understanding of the intent when ResourceLists were introduced in Nov was 
that structures containing localized strings would also contain a 
ResourceList for localized values for that structure. I would suggest 
adding this to the description of ResourceList and ensuring that each such 
structure does have a ResourceList.

Rich Thompson




Richard Jacob <richard.jacob@de.ibm.com>
01/14/2003 04:41 AM
 
        To:     wsrp-wsia@lists.oasis-open.org
        cc: 
        Subject:        [wsrp-wsia] [I#???] inconsistent ResourceList 
handling



Gil, could you please create and assign an issue number to this topic:

Topic: ResourceList
Class: Minor Technical
Title: inconsistent ResourceList handling
Document Section: 4.1.6, 4.1.7, 4.2, 7.1.2, 7.1.8, 7.1.9, 7.2, 7.7
Description:
Currently we have a confusing (at least to me) way of how we handle
ResourceLists.
GetServiceDescription() returns the ServiceDescription type which contains
a ResourceList. It also returns a the EntityDescription[],
Role(UserCategory)Description[] and ModelDescription.
What is the ResourceList supposed to contain? I assume that it shold have
resources for the EntityDescriptions, UserCategoryDescriptions and
PropertyDescriptions (although it is not stated in the spec).
GetEntityDescription() takes sendAllLocales and desiredLocales parameters
but the returned EntityDescriptionType does not contain a ResourceList
type.
I think it should, otherwise we would only have the localized Strings with
exactly one language in them. Or is the consumer supposed to store the
ResourceList from GetServiceDescription() and look the resource up there? 
I
don't think we should desire this.
On the other hand ModelDescription contains a ResourceList. I assume it is
supposed to store the Resources for the PropertyDescriptions.
If so then the ResourceList returned by GetServiceDescription() would
contain redundant information as ServiceDescription contains
ModelDescription.
I think we should decide whether we have _one_ resource list which 
contains
_all_ resources for _all_ the description and when it is returned. Then 
the
desiredLocales and sendAllLocales flags would't make much sense for
getEntityDescription() and getEntityPropertyDescription().
Another option (and I think a better one) would be to have ResourceLists
for each of the Types, say one for EntityDescription, one for
PropertyDescription and one for UserCategorieDescription.
In that case ServiceDescription shoud not contain the ResourceList.


Mit freundlichen Gruessen / best regards,

        Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
Phone: ++49 7031 16-3469  -  Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com


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