[MOBY-dev] xml:lang explored

[Paul Gordon]

I think we are mostly polyglots on this list, but for the sake of 
technical simplicity, I'd stick with just tracking the language rather 
than having multiple values in the registry.  Multilingual descriptions 
could be offloaded to the LSID metadata perhaps if people really want it.

Mes 0.02$ canadiens,

Paul

Mark Wilkinson wrote:
> Should we allow registration of objects, service-types and namespaces 
> in foreign languages also?  If so, then we need to re-think the entire 
> way we manage the ontology, and assign unique id numbers to each node, 
> where the rdf:label of the node can have multiple languages, rather 
> than having the node named by its label.
>
> ...can... worms... but it's probably the "right thing to do"...
>
> M
>
>
>
> On Mon, 26 May 2008 00:21:23 -0700, Jason Stewart 
> <jason.e.stewart at gmail.com> wrote:
>
>> Hey all,
>>
>> Here's what I have found out.
>>
>> I don't believe that changing the current parser for Central.pm is
>> going to help the situation. I have looked and besides special API's
>> like the one implemented by LibXML::Reader, the application is always
>> required to maintain the status of xml:lang using the standard SAX and
>> DOM API's - for Java or for Perl.
>>
>> We will have to preserve the information in the DB, so a decision
>> needs to be made on what level the xml:lang should be used - only for
>> descriptions?? or for the whole registration?? At the moment I don't
>> see any reason to use it for more than the description - how do people
>> feel about this? Changing this should require adding one column to the
>> DB.
>>
>> Finally, do we want registration with multiple descriptions? That will
>> probably require a significant change in the DB - a new table for
>> linking descriptions to registrations. Are people happy about that?
>>
>> Cheers, jas.
>> _______________________________________________
>> MOBY-dev mailing list
>> MOBY-dev at lists.open-bio.org
>> http://lists.open-bio.org/mailman/listinfo/moby-dev
>
>
>