Re: [regrep] 1/29/2003: Localization Capabilities

[Farrukh Najmi <farrukh.najmi@sun.com>]

Monica Martin wrote:

>We indicated to the party raising the question, that we had the
>Localized capability.  This was raised particularly by some of the teams
>that are very multi-lingual focused, such as Dublin Core Registry
>prototype (They have to accommodate more than 20 languages).  I noted in
>ebRS that we briefly discuss in section G.4.2:
>
>However, the language information may be used as one of the query
>criteria, such as retrieving only DTD written in French. 
>
This is currently supported by our ad hoc query mechanisms. A DTD may be 
classified by a language classification and then an ad hoc query may 
find DTDs classified by the French language classification.

>Furthermore, a
>language negotiation procedure, like registry client is asking a
>favorite language for messages from registry services, could be another
>functionality for the future revision of this document.
>
Above type of functionality may be more sensible to leave to client APIs 
rather than registry specs. JAXR API for example allows clients to 
specify their preferred language and get localized content appropriately 
using the API. This is possible in JAXR even today with our current specs.

Of course we would be open to a clearly articulated use case and need 
for additional spec functionality in this area.

>
>Perhaps extended query or other important localization needs can be
>addressed in the future.  Thoughts?
>
Again we would need to see clear use cases and need justification. I do 
not believe that we have that in this thread.

>
>Thank you.
>Monica
>
>-----Original Message-----
>From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
>Sent: Wednesday, January 29, 2003 7:37 AM
>To: Breininger Kathryn R
>Cc: ebXML Regrep (E-mail); sang.shin@sun.com; weida@apelon.com;
>akotok@disa.org; lane.derek@epa.gov
>Subject: Re: [regrep] Presentations and questions
>
>
>Regarding "Multi-lingual capabilities" (I don't think this was covered
>yet):
>
>This is covered by our Internationalization (I18N) support, with classes
>InternationalString and LocalizedString (I'm referencing RIM v2.33). 
>The LocalizedString class contains 3 attributes:
>
>	- lang - specifies the language used by that LocalizedString
>	- charset - specifies the name of the character set used by that
>
>LocalizedString
>	- value - specifies the string value used by that
>LocalizedString
>
>Hope that helps,
>Joe
>
>"Breininger, Kathryn R" wrote:
>  
>
>>The overview presentation I gave and the tutorial presentation and
>>    
>>
>case studies Monica presented are now posted on the ebXML Registry home
>page under the "Documents" section, in a subsection titled
>"Presentations" http://www.oasis-open.org/committees/regrep/#documents .
>In addition, here are the questions that were raised during the panel
>discussion.
>  
>
>>*       Use of packages, how to organize items in a registry?
>>*       Taxonomies and classifications, what's the difference?
>>*       OAIS: integrity of objects over time
>>*       How to integrate 11179 and ebXML
>>*       Persistent locations in registries (DRIve)
>>*       How to register namespaces?
>>*       Multi-lingual capabilities
>>*       URI for RegistryObject
>>
>>The third question (Integrity of objects over time) was asked
>>    
>>
>specifically by Derek Lane, from EPA.  More detail on his question
>follows:
>  
>
>>1. Comparison between the two concepts ebXML Reg/Rep with OAIS
>>    
>>
>[Reference Model for an Open Archival Information System (OAIS)]
>  
>
>>2. Capability to ensure integrity of objects over time
>>3. If a checksum may be required to ensure that the object is what was
>>    
>>
>submitted over time (mentioned by Lane in discussion).
>  
>
>>Please respond with answers on the third question (details 1-3 above)
>>    
>>
>directly to the list and Derek Lane at lane.derek@epa.gov  The link to
>OAIS is at: http://ssdoo.gsfc.nasa.gov/nost/isoas/overview.html
>  
>
>>Please also feel free to discuss each of the other questions above on
>>    
>>
>the list.  This is a good opportunity to address some of these
>questions, and possibly consider for version 4.0 or as topics of best
>practice papers!
>  
>
>>Kathryn
>>
>>Kathryn Breininger
>>CENTRAL Project Manager
>>Emerging Technologies
>>Boeing Library Services
>>
>>425-965-0182 phone
>>425-237-3491 fax
>>kathryn.r.breininger@boeing.com
>>
>>----------------------------------------------------------------
>>To subscribe or unsubscribe from this elist use the subscription
>>manager: <http://lists.oasis-open.org/ob/adm.pl>
>>    
>>
>
>----------------------------------------------------------------
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.oasis-open.org/ob/adm.pl>
>  
>

-- 
Regards,
Farrukh