RE: translations

Hi Tom,

> 
> That is one way to do it, but it ultimately puts a significant
> maintenance burden on the person (i.e., you) who is collecting
> and aggregating those translations into one big schema.  
> 
> As an alternative -- in principle, at any rate -- translators
> might maintain the translations in RDF on their own servers
> and you would merely point to them and merge their contents
> into a multi-lingual RDF description automatically.

I think we probably need all RDF descriptions of SKOS Core to be under the same configuration management, so it may be a problem for SKOS Core to import files from other servers.

What if we have on the W3C server e.g.

core.rdf
core/annotations/en.rdf
core/annotations/fr.rdf

... and so on, with core.rdf containing statements like ...

<http://www.w3.org/2004/02/skos/core> owl:imports <http://www.w3.org/2004/02/skos/core/annotations/fr> .

... for each language resource, and then e.g. core/annotations/fr.rdf containing only statements involving predicates with literal range (i.e. rdfs:label, rdfs:comment, skos:definition etc.)?

Or do we want http://www.w3.org/2004/02/skos/core to serve a content-negotiated representation with only the annotations in the requested language? 

Cheers,

Al.

> 
> Harry Wagner has developed a tool [1] to help people input
> translations of the labels, definitions, and comments of
> Dublin Core elements into various languages and output those
> translations in RDF/XML, e.g.:
> 
>       <rdf:Description
>       rdf:about="http://purl.org/dc/elements/1.1/creator">
>         <rdfs:label
>         xml:lang="ja-JP">&#20316;&#25104;&#32773;</rdfs:label>
>         <rdfs:comment
>         xml:lang="ja-JP">&#24773;&#22577;&#36039;&#28304;&#12398;
>         
> &#20869;&#23481;&#20316;&#25104;&#12395;&#20027;&#12383;&#1242
> 7;&#36012;
>         
> &#20219;&#12434;&#12418;&#12388;&#23455;&#20307;</rdfs:comment>
>         <dc:description
>         xml:lang="ja-JP">&#20316;&#25104;&#32773;&#35201;&#32032;
>         
> &#12398;&#20363;&#12392;&#12375;&#12390;&#65292;&#20154;&#6529
> 2;&#32068;
>         
> &#32340;&#20006;&#12403;&#12395;&#12469;&#12540;&#12499;&#1247
> 3;&#12394;
>         
> &#12393;&#12364;&#12354;&#12427;&#12290;&#19968;&#33324;&#3034
> 0;&#12395;
>         
> &#12399;&#65292;&#20316;&#25104;&#32773;&#12398;&#21517;&#2106
> 9;&#12399;
>         
> &#12381;&#12398;&#23455;&#20307;&#12434;&#25351;&#31034;&#1237
> 7;&#12427;
>         
> &#12383;&#12417;&#12395;&#29992;&#12356;&#12427;&#12398;&#1236
> 4;&#12424;
>         &#12356;&#12290;</dc:description> <rdf:type
>         
> rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
>       </rdf:Description>
> 
> -- from a schema used to seed the registry in the open-source
> Dublin Core Metadata Registry project [2,3].
> 
> In DCMI we have for quite awhile thought it would be nice to
> push the RDF-formatted translations out to the translators for
> maintenance, but very practical issues have always stood in
> the way.  Moreover, we have recognized that the very simple
> model presented above does not begin to capture important
> contextual information such as exactly what was translated,
> by whom, and the status of a translation (if any).
> 
> This may not be the right list for having this discussion,
> but it might be worth at some point using the relatively
> straightforward issue of translation maintenance as a starting
> point for re-examining the issues involved in the distributed
> maintenance of a machine-processable standard.
> 
> Tom
> 
> [1] http://wip.dublincore.org/translate/
> [2] http://dublincore.org/dcregistry/
> [3] svn://svn.dublincore.org/registry/trunk
> 
> -- 
> Dr. Thomas Baker                      baker@sub.uni-goettingen.de
> SUB - Goettingen State                            +49-551-39-3883
> and University Library                           +49-30-8109-9027
> Papendiek 14, 37073 Göttingen
> 
>

Received on Wednesday, 6 July 2005 17:07:35 UTC