[datacatalogs] Internationalization for Catalogs/Datasets/Resources

[James McKinney]

I didn't take a deep look, but it looks like DCIP supports DCAT serialized in N3 notation. DCAT is fully internationalized as far as I know, and the N3 notation supports it. The current JSON representation might not support internationalization, however. This can be solved by DCIP switching to JSON-LD instead of JSON. It wouldn't require changing that much in the current JSON representation, and users who are not interested in the "LD" part can simply ignore the extra properties. But as I said, this is somewhat speculation because I didn't have a deep look.

Cheers,

James

On 2013-10-21, at 5:47 PM, Aaron Couch wrote:

> Not sure if this is the best place to ask this, but this listserve was the only resource linked to from http://spec.datacatalogs.org/
> 
> Is there an agreed upon convention for translation of open data catalogs, datasets, or resources? Many CMSs make it easy to translate content, however DCIP and other similar resources don't seem to take this into account other than specifying the language of a particular entity. 
> 
> A simple example would be to provide translated titles or descriptions for a Dataset or Resource. As long as the UUIDs are the same would this break DCIP best practice? 
> _______________________________________________
> data-catalogs mailing list
> data-catalogs at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/data-catalogs
> Unsubscribe: http://lists.okfn.org/mailman/options/data-catalogs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/data-catalogs/attachments/20131021/6aa8bdae/attachment-0001.html>