W3C home > Mailing lists > Public > public-esw-thes@w3.org > September 2019

Re: Skout - A YAML-based format for SKOS

From: Marcel Otto <marcelotto.de@googlemail.com>
Date: Thu, 12 Sep 2019 03:05:57 -0700 (PDT)
To: Christophe Dupriez <dupriez@destin.be>
Cc: <public-esw-thes@w3.org>
Message-Id: <5D417AEC-E043-41BA-9BC3-1F0DFCE5CF50@gmail.com>
Hi Christophe,


Thanks for your feedback. I hope you don’t mind forwarding the discussion to the mailing list.


I generally agree that I18n is a very important aspect for concept schemes. It just wasn’t part of the use case I had, when implementing this. 


I already thought about support for language tags and also datatypes on literals. Unfortunately the obvious solution of using custom YAML datatypes doesn't seem to be viable, since these are not available in all YAML implementations, in particular the ones in Erlang/Elixir. So, some kind of special syntax on top of basic YAML must be introduced for this. 


But even when that extension will be implemented, I doubt that Skout will ever be a good solution for managing translations. I actually think a better approach is to use dedicated tools for the different aspects of managing a concept scheme. While I think Skout is very well-suited for managing the narrower hierarchy, other tools will probably better suited for the translations. For this case, IMO an already existing format for managing translations would be used ideally, eventually extended for use with SKOS. Something gettext-based with its large eco-system behind it and well-known by translators would come to mind for example. I’m not sure if something like that exists already.


Best,


Marcel








> On Sep 12, 2019, at 9:12 AM, Christophe Dupriez <dupriez@destin.be> wrote:
> 
> 
> Hello Marcel,
> 
> 
> Some feedback: for me SKOS is important for multilingual applications. A 
> concise support to specify multiple labels for different languages is 
> useful. A "pivot" language (latin, english...) must be defined to 
> generate the URI.
> 
> 
> My experience with SKOS is that it is a good minimum common denominator 
> to specify human/machine interface for concepts; but sometimes needs to 
> be slightly extended for a given application (for example to have 
> concept's usage statistics)
> 
> 
> The ASKOSI.org tried to provide common services based on SKOS for 
> applications (written in Java)
> 
> 
> Have a nice day,
> 
> 
> Christophe
> 
> 
> Le 12/09/19 à 08:54, Marcel Otto a écrit :
>> 
>> 
>> Hi together,
>> 
>> 
>> I recently released a new language for writing SKOS concept schemes in 
>> a more compact, human-friendly manner: 
>> https://github.com/marcelotto/skout
>> 
>> 
>> It might of interest for some you.
>> 
>> 
>> Marcel
>> 
> 
> 
> 
> 
> 
> 
> 
> -- 
> Christophe Dupriez
> DESTIN-Informatique.com
> Projet AKUINO.net
> Tél.: +32 475.77.62.11
> Twitter @AkuinoNET
> 
Received on Thursday, 12 September 2019 10:06:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:46:54 UTC