RE: [wsrp-wsia] [I#140] Internationalization of property and enti tydescriptions

["Timothy N. Jones" <tim@crossweave.com>]

The proposal includes both values and resource names for strings.  The values 
are specified in the default language.  If that is all the consumer cares 
about, they don't need to process the resources.  If we adopted your 
suggestion, the consumer would be forced to download the values for all 
languages and process the list to find the one they want.  Also, it is 
theoretically possible to reuse resources in our proposal and have a single 
resource document for the entire entity rather than repeating them in the 
return of each getEntityPropertyDescription() call.

Tim

Quoting Gil Tayar <Gil.Tayar@webcollage.com>:

> How about something a bit more simple, but still XML-like?
>  
> <model>
>    <propertydescription name="p1" type="xsd:string">
>         <label xml:lang="en">Property 1</label>
>       <label xml:lang="fr">Propriete 1</label>
>         <hint xml:lang="en">this is a few sentences for some tooltip</hint>
> 
>         <hint xml:lang="fr">Ceci n'est pas une pipe</hint>
>     </propertyDescription>
>    ...
> </model>
>  
> I would propose this as a solution to all WSIA/WSRP localized strings.
>  
> Gil
> 
> -----Original Message-----
> From: Gil Tayar [mailto:Gil.Tayar@webcollage.com]
> Sent: Sun, November 03, 2002 12:17
> To: wsrp-wsia@lists.oasis-open.org
> Subject: [wsrp-wsia] [I#140] Internationalization of property and entity
> descriptions
> 
> 
> Note that this new issue comes with a tentative resolution, outlined below
> Status: Tentative Resolve
> Topic: customization
> Class: Technical
> Raised by: Charles Wiecha
> Title: Internationalization of property and entity descriptions
> Date Added: 3-Nov-2002
> Description: Need a common document format for carrying
> internationalization
> information for entity and property descriptions
> Resolution Date: 21-Nov-2002
> Proposed Resolution: 
> 
> Proposed notation is derived from the xliff standard, but oriented more
> toward resource descriptions than translation.
> <wsrp:localization>
> <resource resname='...'>
>  <value xml:lang='en'>English text</value>
>  <value xml:lang='fr'>French text</value>
> </resource>
> ...
> </wsrp:localization>
>  
> Example use for property descriptions is:
> <model xml:lang="en" localizationURL="...">
>    <propertydescription name="p1" type="xsd:string" label="Property 1"
>          hint="this is a few sentences for some tooltip"
>          label-resname="xyzzy" hint-resname="abccd"/>
>    ...
> </model>
>  
> <wsrp:localization>
> <resource resname='xyzzy'>
>  <value xml:lang='en'>English property 1 label</value>
>  <value xml:lang='fr'>Label de property un</value>
> </resource>
> ...
> </wsrp:localization>
>  
> and for Entity descriptions:  (note that this is a change in the entity
> description format as well)
>  
> <entitydescription xml:lang="en" localizationURL="...">
>    <shorttitle resname="abc">Short entity title</shorttitle>
>    <title resname="xyz">Entity title in english</title>
> </entitydescription>
>  
> <wsrp:localization>
> <resource resname='abc'>
>  <value xml:lang='en'>Short entity title</value>
>  <value xml:lang='fr'>Title court de l'entity</value>
> </resource>
> ...
> </wsrp:localization>
> Gil Tayar
> WebCollage
>  
> 
>