Current use and future directions for Skosmos

[Osma Suominen]

Hi all,

Welcome to the skosmos-users list! I'm very happy to see that so many
people joined the list (currently 14), even despite my little mishap of
sending the invitation message in Finnish! :)

To open the discussion here, I want to ask you all,

1. What do you use (or planning to use) Skosmos for and how?

2. Does Skosmos work in your scenario? If not, what are the problems?

3. How would you like Skosmos to be developed in the future?

4. Do you, or your organization, expect to contribute to Skosmos
development in the future and if so, how? For example, user interface
translations, bug reports and fixes are always welcome, as well as
larger contributions for new features.

I'm asking because even though I know some of your deployment scenarios
already, it's always good to hear how the tool is being used around the
world and get ideas about future development. Obviously Finto and the
National Library of Finland has its own goals and priorities for
Skosmos, but it's good to be aware of common pain points, opportunities
for collaboration and ideas for new features.

-Osma

--
Osma Suominen
D.Sc. (Tech), Information Systems Specialist
National Library of Finland
P.O. Box 26 (Kaikukatu 4)
00014 HELSINGIN YLIOPISTO
Tel. +358 50 3199529
osma.s...@helsinki.fi
http://www.nationallibrary.fi

[Haag, Jason]

Hi Osma,

Thank you for starting this group.


1. I would like to evaluate SKOSMOS for its potential to be the
front-end interface for our published controlled vocabulary datasets
represented as RDF and SKOS. An example of one of these datasets are
available here: http://purl.org/xapi/adb/verbs. This isn't for a
particular library use case, but we anticipate having a repository of
terms that need to be classified,organized and related.

2. I'm not sure if SKOMOS will provide the total solution. I'm
currently evaluating Virtuoso Open Source for providing a SPARQL
endpoint and querying the data. I think SKOMOS might be useful for
providing a browseable and searchable interface for non-technical
users while Virtuoso will allow for more advanced queries and joins on
disparate datasets.

3. I like the idea of SKOMOS being based on SKOS since that is what we
are using to describe our controlled vocabularies. However, I think
the user interface and design could be improved. In the future it
would be nice if SKOMOS allowed for selected some nicely designed
templates or tighter integration with a CMS.

4. Possibly. If we use SKOSMOS we will probably help at least submit
bug reports and feature requests.

Thank you for reaching out!

Kind Regards,

J Haag
-------------------------------------------------------
Advanced Distributed Learning Initiative
+1.850.266.7100(office)
+1.850.471.1300 (mobile)
jhaag75 (skype)
http://motifproject.org (MoTIF Project)
http://ml.adlnet.gov (Web)
http://twitter.com/mobilejson (Twitter)
http://linkedin.com/in/jasonhaag (LinkedIn)

> --
> You received this message because you are subscribed to the Google Groups
> "Skosmos Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to skosmos-user...@googlegroups.com.
> To post to this group, send email to skosmo...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/skosmos-users/560D2880.5090808%40helsinki.fi.
> For more options, visit https://groups.google.com/d/optout.

[Thomas Francart]

Hello Osma

Thanks for setting up the mailing-list

1. What do you use (or planning to use) Skosmos for and how?

Automated publishing of multilingual vocabularies from a back-office SKOS management tool.

 

2. Does Skosmos work in your scenario? If not, what are the problems?

It should work (not tested yet). Handling of multilingual thesauri is key in all my use-cases.

 

3. How would you like Skosmos to be developed in the future?

French translation

Captcha on the feedback form
Ability to integrate with a CMS or add editorial content to front page

Handling of iso-thes ontology (http://pub.tenforce.com/schemas/iso25964/skos-thes/)

Ability to handle different versions of the same thesaurus over time

 

4. Do you, or your organization, expect to contribute to Skosmos development in the future and if so, how? For example, user interface translations, bug reports and fixes are always welcome, as well as larger contributions for new features.

French translation

Bug reports

As the developer of SKOS Play (http://labs.sparna.fr/skos-play), I may also think about an integration with SKOS Play to :

1. Use SKOS-Play as a "bask-office" for SKOSMOS to upload a vocabulary;
2. Pregenerate PDFs views (+ others) of the thesauri to publish them in SKOSMOS;

Thanks for making SKOSMOS available !

Thomas

 

I'm asking because even though I know some of your deployment scenarios already, it's always good to hear how the tool is being used around the world and get ideas about future development. Obviously Finto and the National Library of Finland has its own goals and priorities for Skosmos, but it's good to be aware of common pain points, opportunities for collaboration and ideas for new features.

-Osma

--
Osma Suominen
D.Sc. (Tech), Information Systems Specialist
National Library of Finland
P.O. Box 26 (Kaikukatu 4)
00014 HELSINGIN YLIOPISTO
Tel. +358 50 3199529
osma.s...@helsinki.fi
http://www.nationallibrary.fi

--
You received this message because you are subscribed to the Google Groups "Skosmos Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to skosmos-user...@googlegroups.com.
To post to this group, send email to skosmo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/skosmos-users/560D2880.5090808%40helsinki.fi.
For more options, visit https://groups.google.com/d/optout.

--

Thomas Francart - SPARNA
Web de données | Architecture de l'information | Accès aux connaissances
blog : blog.sparna.fr, site : sparna.fr, linkedin : fr.linkedin.com/in/thomasfrancart
tel :  +33 (0)6.71.11.25.97, skype : francartthomas

[Armando Stellato]

Hi Osma,

great you started a mailing list!

Replies here below :-)

> 1. What do you use (or planning to use) Skosmos for and how?

Well, I'm not a "user" but a developer as well. Since my team works on various projects about ontology and thesauri development [1], I usually recommend SKOSMOS as a fast and efficient solution for browsing thesauri developed with VocBench or Semantic Turkey.

> 2. Does Skosmos work in your scenario? If not, what are the problems?

It definitely works! As an improvement, maybe working with more triple stores, but that's not really a big limitation for now.

> 3. How would you like Skosmos to be developed in the future?

I would add support for SKOSXL. In my experience in developing VocBench, and as consultant for generation and publication of RDF content in general, I definitely understand that, even if a team embraces SKOSXL for content management, still an export to plain SKOS is necessary for final data publication. Currently, it seems most of large organizations keep at least metadata attached to their labels, and SKOSXL is a must: a very common solution is thus to publish labels in both formats. This guarantees compatibility with SKOS core clients, while providing the richest information developed in SKOSXL.
SKOSMOS could provide a configuration for knowing what to look for.
If you look at this page: http://aims.fao.org/aos/agrovoc/c_1221
you see labels are shown in a simple way (as if they were plain skos core labels), but they are clickable and they point to the URIs of their SKOSXL description.
This is a very simple data publishing system [2] "a la" Pubby, with no browsing, no concept tree, no caching etc... which are instead provided by SKOSMOS. I think this is a little and simple effort to improve SKOSMOS while representing at the same time a great added value.

Speaking of publishing system, maybe SKOSMOS could also be turned into a publishing system (i.e. resolve URI dereferenciation for all hosted resources). Not a general triple publisher such as Pubby, not as reconfigurable as Loddy, but very much verticalized on thesauri, mixing up http dereferenciation with the already existing browsing possibilities. Again, maybe not too much to implement, and a great value added to the existing system.

> 4. Do you, or your organization, expect to contribute to Skosmos
> development in the future and if so, how? For example, user interface
> translations, bug reports and fixes are always welcome, as well as larger
> contributions for new features.

Pls send me the list of all label/terms/text content in the UI of SKOSMOS and I will gladly send you back the Italian version!

Cheers,

Armando

[1] http://art.uniroma2.it/software/
[2] https://bitbucket.org/art-uniroma2/loddy

[Osma Suominen]

Hi Jason, Thomas and Armando,

Thank you all for your excellent input! I won't reply to each one
individually, but I will comment on a few key points which I have tried
to group together. If necessary we can continue on these topics in
separate threads.

[Jason]

> 2. I'm not sure if SKOMOS will provide the total solution. I'm
> currently evaluating Virtuoso Open Source for providing a SPARQL
> endpoint and querying the data. I think SKOMOS might be useful for
> providing a browseable and searchable interface for non-technical
> users while Virtuoso will allow for more advanced queries and joins
> on disparate datasets.

Right, Skosmos doesn't currently provide direct SPARQL access, though it
could be integrated (see issue #318).

[Jason]

> 3. I like the idea of SKOMOS being based on SKOS since that is what
> we are using to describe our controlled vocabularies. However, I
> think the user interface and design could be improved. In the future
> it would be nice if SKOMOS allowed for selected some nicely designed
> templates or tighter integration with a CMS.

[Thomas]

> Ability to integrate with a CMS or add editorial content to front
> page

Regarding UI design, there's of course always room for improvement. Some
tweaking can be done with a custom CSS (see config.inc). We use that in
Finto to change the colors and add some icons. Possibly
theming/templates could be built on top of that. We are quite happy with
the current Finto layout (except for the front page, which could use a
redesign), but any contributions in this area are welcome.

We have done quite a lot of usability testing on Finto and tried to
address actual problem cases we've seen users struggle with. So I think
the situation is not bad, but of course, the context of use may be
different in other organizations.

Integration with a CMS is a tricky issue. Currently Skosmos has been
designed as a stand-alone PHP web application (as opposed to e.g. a
WordPress or Drupal plugin). Bringing in content from a CMS is possible
in a very limited fashion, by using the left.inc / right.inc /
footer.inc hooks and custom code which you have to write yourself.

[Armando]

> It definitely works! As an improvement, maybe working with more
> triple stores, but that's not really a big limitation for now.

The problem is mainly the lack of good text index support in triple
stores. Otherwise any SPARQL 1.1 compliant triple store should already
work. (You may remember we tried Skosmos with an old version of
AllegroGraph, there the problem was mainly that it didn't follow SPARQL
1.1 well enough.)

Last time I looked (it was about two years ago, things may have changed)
for example the Virtuoso text index was totally unsuitable for Skosmos -
it required prefix queries of at least four characters. Also 4store's
word-based text index is similarly not very useful. Bigdata has a text
index that could be used, and in fact we had it working reasonably well
at some point in the past, but then the code bitrotted and was
eventually removed.

We're quite happy with Jena Fuseki and jena-text so there is little
reason to invest resources in supporting anything else. But of course,
contributions welcome...

[Thomas]

> Captcha on the feedback form

There is no captcha, but there are some tricks in the form code
(JavaScript and PHP) that make spamming quite difficult. In practice we
don't get almost any spam via the Finto feedback form. We used to get a
lot before these were implemented.

[Armando]

> I would add support for SKOSXL. In my experience in developing
> VocBench, and as consultant for generation and publication of RDF
> content in general, I definitely understand that, even if a team
> embraces SKOSXL for content management, still an export to plain
> SKOS is necessary for final data publication. Currently, it seems
> most of large organizations keep at least metadata attached to their
> labels, and SKOSXL is a must: a very common solution is thus to
> publish labels in both formats. This guarantees compatibility with
> SKOS core clients, while providing the richest information developed
> in SKOSXL. SKOSMOS could provide a configuration for knowing what to
> look for. If you look at this page:
> http://aims.fao.org/aos/agrovoc/c_1221 you see labels are shown in a
> simple way (as if they were plain skos core labels), but they are
> clickable and they point to the URIs of their SKOSXL description.
> This is a very simple data publishing system [2] "a la" Pubby, with
> no browsing, no concept tree, no caching etc... which are instead
> provided by SKOSMOS. I think this is a little and simple effort to
> improve SKOSMOS while representing at the same time a great added
> value.

You are right, and we have SKOS XL support on the radar (see issue
#109). But right now it hasn't been urgent for us.

I'm also a bit anxious about the usability implications. Right now terms
are only clickable in the case of semantic relationships (broader,
narrower, related), and they lead to another concept page. But if also
labels become clickable, there is potentially more confusion and many
more pages where the user may get lost. Perhaps some kind of inline
display for SKOS XL metadata would be more appropriate than a separate page.

[Thomas]

> Handling of iso-thes ontology
> (http://pub.tenforce.com/schemas/iso25964/skos-thes/)

What aspects of iso-thes in particular are you interested in? We already
have support for ConceptGroup and ThesaurusArray. Also there is at least
partial support for ConceptGroups nested using superGroup/subGroup so
for example the most recent version of the UNESCO Thesaurus groups can
be browsed: http://skosmos.dev.finto.fi/unesco/en/groups

Some of the iso-thes constructs are built on top of SKOS XL so we would
need to support that first to be able to support them as well.

In practice we haven't been working with enough datasets making use of
iso-thes (except the above mentioned structures) to be able to have real
use cases to implement. I'm only aware of the Getty vocabularies making
use of iso-thes features that we don't already support, do you know of
others?

[Thomas]

> Ability to handle different versions of the same thesaurus over time

This is a tricky one... I'm somewhat involved in the skos-history
project (https://github.com/jneubert/skos-history) and I know it is used
to provide access to change lists for the STW Thesaurus (see
http://zbw.eu/stw/version/about.en.html). But I'm not sure how this kind
of functionality could/should be implemented in Skosmos, which currently
only deals with the most current data. Ideas welcome!

[Armando]

> Speaking of publishing system, maybe SKOSMOS could also be turned
> into a publishing system (i.e. resolve URI dereferenciation for all
> hosted resources). Not a general triple publisher such as Pubby, not
> as reconfigurable as Loddy, but very much verticalized on thesauri,
> mixing up http dereferenciation with the already existing browsing
> possibilities. Again, maybe not too much to implement, and a great
> value added to the existing system.

It can already be used that way - Skosmos can obviously provide HTML
pages for concepts, and the Skosmos REST API can serve
content-negotiated RDF responses (RDF/XML, Turtle, JSON-LD) of concept
information. What is missing is the first point of access that needs to
perform a 303 redirect to the appropriate representation - this is
generally outside the control of Skosmos, of course depending on the URI
design (but I'd hate to see a /skosmos/ part in actual concept URIs).

For Finto and YSO, we have implemented redirection rules for the
www.yso.fi domain as rather simple Apache mod_rewrite rules that
redirect to the Skosmos installation according to the Accept header. Try
for example:

wget --header 'Accept: text/html' http://www.yso.fi/onto/yso/p1234
wget --header 'Accept: text/turtle' http://www.yso.fi/onto/yso/p1234

[Thomas]
> French translation

[Armando]

> Pls send me the list of all label/terms/text content in the UI of
> SKOSMOS and I will gladly send you back the Italian version!

I have previously set up a translation project on Transifex where it is
possible to translate Skosmos to several languages that FAO has
indicated it would like to support:

https://www.transifex.com/national-library-of-finland/skosmos/

French is listed but not yet started. This would be good to coordinate
with FAO.

Italian is not currently an option on the Transifex project, though it
could be easily added.

The Transifex strings are currently a bit out of date as there have been
a few new translated strings introduced in 1.2 and the upcoming 1.3
version. I will try to update it to the most recent strings soon.

Of course, translations can also be maintained and contributed the
traditional way, using po files. See here:
https://github.com/NatLibFi/Skosmos/wiki/Translation

[Thomas]

> As the developer of SKOS Play (http://labs.sparna.fr/skos-play), I
> may also think about an integration with SKOS Play to :
>
> Use SKOS-Play as a "bask-office" for SKOSMOS to upload a vocabulary;
> Pregenerate PDFs views (+ others) of the thesauri to publish them
> in SKOSMOS;

That would be awesome!

[Mikael Pesonen]

Hi Osma,

I also want to thank you for developing Skosmos and keeping it alive. We
don't have our plans ready yet so here's the info I have at the moment.

On 1.10.2015 15:35, Osma Suominen wrote:
> Hi all,
>
> Welcome to the skosmos-users list! I'm very happy to see that so many
> people joined the list (currently 14), even despite my little mishap
> of sending the invitation message in Finnish! :)
>
> To open the discussion here, I want to ask you all,
>
> 1. What do you use (or planning to use) Skosmos for and how?

We are defining our company ontology/vocabulary (business, technology,
people) with Vocbench and enabling users to browse it with Skosmos.

>
> 2. Does Skosmos work in your scenario? If not, what are the problems?

It works great. It's quite compicated to get the data from Vocbench to
Skosmos but that's a minor issue.

>
> 3. How would you like Skosmos to be developed in the future?
>
> 4. Do you, or your organization, expect to contribute to Skosmos
> development in the future and if so, how? For example, user interface
> translations, bug reports and fixes are always welcome, as well as
> larger contributions for new features.

I'll have to get back with these.

Br,
Mikael Pesonen

>
> I'm asking because even though I know some of your deployment
> scenarios already, it's always good to hear how the tool is being used
> around the world and get ideas about future development. Obviously
> Finto and the National Library of Finland has its own goals and
> priorities for Skosmos, but it's good to be aware of common pain
> points, opportunities for collaboration and ideas for new features.
>
> -Osma
>

--

www.lingsoft.fi

Speech Applications - Language Management - Translation - Reader's and Writer's Tools - Text Tools - E-books and M-books

Mikael Pesonen
System Engineer

e-mail: mikael....@lingsoft.fi
Tel. +358 2 279 3300

Time zone: GMT+2

Helsinki Office
Eteläranta 10
FI-00130 Helsinki
FINLAND

Turku Office
Linnankatu 10 A
FI-20100 Turku
FINLAND

[Neubert, Joachim]

Hi Osma, all,

Jumping in a bit late, just a few remarks:

I like Skosmos very much as a proof of the basic idea of SKOS, that SKOS enables generic tools and interfaces to otherwise quite different knowledge organization systems. That is valuable and encouraging - despite the fact that we currently have no plans to change the STW RDFa presence. (Would be difficult to fit into the website design, and it also would hardly be possible to include custom links to our EconBiz retrieval system, as well as to the subject category system, which pre-dates ISO-Thes and is a KOS at its own.)

I however think about hosting a Skosmos instance for other vocabularies (particularly ones we are discussing or preparing mappings to), and I'll happily contribute issues along the way :)

Particularly, I'd be happy to contribute to the development of a generic "versioning-aware" Skosmos. In that context, it would be helpful to have more actual use cases for versioned thesauri and/or classifications, and in particular the workflows interwoven with version changes.

+1 to the ideas about SKOS-XL (where possibly derived skos:prefLabels should provide the main linking points in the UI, and links or popups for skosxl labels as extended and secondary information) and about the way to provide concepts URIs *outside* the application (via content negotiation).

Thank you for the application, and for starting this discussion!

Cheers, Joachim

-----Ursprüngliche Nachricht-----
Von: skosmo...@googlegroups.com [mailto:skosmo...@googlegroups.com] Im Auftrag von Osma Suominen
Gesendet: Montag, 5. Oktober 2015 09:50
An: skosmo...@googlegroups.com
Betreff: Re: Current use and future directions for Skosmos

--
You received this message because you are subscribed to the Google Groups "Skosmos Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to skosmos-user...@googlegroups.com.
To post to this group, send email to skosmo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/skosmos-users/56122B8F.9040704%40helsinki.fi.

[Caterina Caracciolo]

Hi Osma, all, 

Greetings, and thank you for the nice work you do with Skosmos! Here my answers:

1. We use Skosmos for browsing and searching AGROVOC.

2. It works ok, although we had to adapt some things to make it work in our environment, with some not-so-beatiful results. Most notably, we had to skip the skosmos entry page to avoid loading the statistics, but now the entry page looks somehow unfinished. 

3. 

- Would like to have it integrated in cms, we use Drupal. 

- Support skos-xl. 

- At this point we have loddy for displaying agrovoc lod in HTML and Skosmos for nicer browsing and search. This is a bit too much, especially because it creates confusion in users ("what url should I use to refer to agrovoc concepts?" and they tend to get the one visualized in skosmos, as it is the one that looks nicer and that can actually be searched). I would want to simplify this and only use one tool. Skosmos?   

4. We have been giving feedback on features etc, and provided GUI translation in ES. More in the future, if possible.  

--
You received this message because you are subscribed to the Google Groups "Skosmos Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to skosmos-user...@googlegroups.com.
To post to this group, send email to skosmo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/skosmos-users/560D2880.5090808%40helsinki.fi.

[Osma Suominen]

Hi!

I have now updated the Skosmos translation project on Transifex so that
it matches the most recent Skosmos code (1.3-dev). I also enabled the
Transifex auto-update feature which should mean that the strings should
stay up to date w.r.t. the Skosmos source code. I also added Italian as
a target language.

If you want to contribute translations (Thomas mentioned that he could
do a French translation and Armando an Italian one), now would be an
excellent time to start ;)

Simply go to the Transifex project:

https://www.transifex.com/national-library-of-finland/skosmos/dashboard/

You will need to register and then request access. I can also send
invitations if necessary. Then you can start doing translation with the
Transifex UI in your web browser.

Skosmos 1.3 will include the Spanish translation that was just completed
by FAO, and possibly other languages if they are sufficiently ready at
the time of release. I expect the 1.3 release to happen later this month.

-Osma

On 05/10/15 10:49, Osma Suominen wrote:
> [Thomas]
>> French translation
>
> [Armando]
>> Pls send me the list of all label/terms/text content in the UI of
>> SKOSMOS and I will gladly send you back the Italian version!
>
> I have previously set up a translation project on Transifex where it is
> possible to translate Skosmos to several languages that FAO has
> indicated it would like to support:
>
> https://www.transifex.com/national-library-of-finland/skosmos/
>
> French is listed but not yet started. This would be good to coordinate
> with FAO.
>
> Italian is not currently an option on the Transifex project, though it
> could be easily added.
>
> The Transifex strings are currently a bit out of date as there have been
> a few new translated strings introduced in 1.2 and the upcoming 1.3
> version. I will try to update it to the most recent strings soon.

[Sandor Kopacsi]

Hi Osma,

Thank you for offering me to join this group.

1. University of Vienna is going to use Skosmos for its Phaidra project.

2. Skosmos doesn't work well, because I can not connect to other vocabularies. I have set the vocabularies.ttl as follow, 

:ysa a skosmos:Vocabulary, void:Dataset ;
    dc:title "COAR - Resource Type Vocabulary"@en ;
    dc:subject :cat_general ;
    void:uriSpace "http://purl.org/coar/resource_type/";
    skosmos:language "en";
    void:sparqlEndpoint <http://vocabularies.coar-repositories.org/sparql/repositories/coar> ;
    .
but it still doesn't work.

I have also tried with a local SPARQL endpoints (after uploading the SKOS file directly to Jena Fuseki) as follows:

void:sparqlEndpoint <http://localhost:3030/ds/sparql> ;

but I have the same problem. What should I modify?

Later on I also would like to connect getty vocabulary to Skosmos.

3., 4., Depends on the success of the trials.

Thank you for your help!

Best Regards,

Sandor

[Osma Suominen]

Hi Sandor!

Glad to hear that you will be using Skosmos!

I checked out COAR and it seems to me that it only represents labels
using SKOS XL properties. Skosmos doesn't support SKOS XL currently (see
issue #109), so you will first need to convert the data to SKOS Core
labels ("plain SKOS").

One tool that can do this for you is here:
http://art.uniroma2.it/owlart/documentation/utilities.jsf#skos_utilities

Hope this helps,
Osma

On 06/10/15 15:44, Sandor Kopacsi wrote:
> Hi Osma,
> Thank you for offering me to join this group.
>
> 1. University of Vienna is going to use Skosmos for its Phaidra

> <http://phaidraservice.univie.ac.at/> project.

> osma.s...@helsinki.fi <javascript:>

> http://www.nationallibrary.fi
>
> --
> You received this message because you are subscribed to the Google
> Groups "Skosmos Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to skosmos-user...@googlegroups.com

> <mailto:skosmos-user...@googlegroups.com>.

> To post to this group, send email to skosmo...@googlegroups.com

> <mailto:skosmo...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/skosmos-users/cb0e709c-4166-48b0-9fe0-55840f00e139%40googlegroups.com
> <https://groups.google.com/d/msgid/skosmos-users/cb0e709c-4166-48b0-9fe0-55840f00e139%40googlegroups.com?utm_medium=email&utm_source=footer>.

> For more options, visit https://groups.google.com/d/optout.

[Osma Suominen]

On 06/10/15 15:58, Osma Suominen wrote:
> Hi Sandor!
>
> Glad to hear that you will be using Skosmos!
>
> I checked out COAR and it seems to me that it only represents labels
> using SKOS XL properties. Skosmos doesn't support SKOS XL currently (see
> issue #109), so you will first need to convert the data to SKOS Core
> labels ("plain SKOS").
>
> One tool that can do this for you is here:
> http://art.uniroma2.it/owlart/documentation/utilities.jsf#skos_utilities

...or perhaps an easier way would be to simply load the data into Fuseki
and then execute this SPARQL Update query that converts SKOS XL labels
into SKOS Core labels:

--cut--
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX skosxl: <http://www.w3.org/2008/05/skos-xl#>
INSERT {
?c skos:prefLabel ?pref .
?c skos:altLabel ?alt .
?c skos:hiddenLabel ?hidden .
}
WHERE {
{ ?c skosxl:prefLabel/skosxl:literalForm ?pref }
UNION
{ ?c skosxl:altLabel/skosxl:literalForm ?alt }
UNION
{ ?c skosxl:hiddenLabel/skosxl:literalForm ?hidden }
}
--cut--

As a sidenote, many people seem to have it difficult to use vocabularies
created with VocBench in Skosmos, because of the "impedance mismatch"
between SKOS XL created by VocBench, and plain SKOS expected by Skosmos.
Maybe it would be easier if VocBench had a feature to export labels also
as plain SKOS?

Even if support for SKOS XL label metadata is added to Skosmos, it will
probably still require the labels to be also expressed using the SKOS
Core properties, because of the need to be able to query them using the
text index.

-Osma


--
Osma Suominen
D.Sc. (Tech), Information Systems Specialist
National Library of Finland
P.O. Box 26 (Kaikukatu 4)
00014 HELSINGIN YLIOPISTO
Tel. +358 50 3199529
osma.s...@helsinki.fi

http://www.nationallibrary.fi

[Sandor Kopacsi]

Dear Osma,

Thank you for your answer. 

I should convert the COAR SKOS XL file to SKOS Core locally, upload to Jena Fuseki, and run Skosmos. Am I right?

Does it mean, that the remote endpoint of COAR (http://vocabularies.coar-repositories.org/sparql/repositories/coar) can not be used ?
Thanks,

Sandor

P.S.: where can I reach other issues (e.g. #109) directly? 

> <mailto:skosmos-users+unsub...@googlegroups.com>.

[Osma Suominen]

Hi Sandor!

On 07/10/15 12:04, Sandor Kopacsi wrote:
> Dear Osma,
> Thank you for your answer.
> I should convert the COAR SKOS XL file to SKOS Core locally, upload to
> Jena Fuseki, and run Skosmos. Am I right?

Yes. Either use the OWLART tool, or the SPARQL Update query that I
posted in another message.

> Does it mean, that the remote endpoint of COAR
> (http://vocabularies.coar-repositories.org/sparql/repositories/coar) can
> not be used ?

Unfortunately yes. Skosmos requires the data to follow SKOS Core. The
COAR endpoint data currently is not SKOS Core.

> P.S.: where can I reach other issues (e.g. #109) directly?

In the GitHub Issues section, e.g.
https://github.com/NatLibFi/Skosmos/issues/109

-Osma

> > an email to skosmos-user...@googlegroups.com <javascript:>
> > <mailto:skosmos-user...@googlegroups.com <javascript:>>.

> > To post to this group, send email to skosmo...@googlegroups.com

> <javascript:>
> > <mailto:skosmo...@googlegroups.com <javascript:>>.

> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/skosmos-users/cb0e709c-4166-48b0-9fe0-55840f00e139%40googlegroups.com
> <https://groups.google.com/d/msgid/skosmos-users/cb0e709c-4166-48b0-9fe0-55840f00e139%40googlegroups.com>
>
> >

> <https://groups.google.com/d/msgid/skosmos-users/cb0e709c-4166-48b0-9fe0-55840f00e139%40googlegroups.com?utm_medium=email&utm_source=footer

> <https://groups.google.com/d/msgid/skosmos-users/cb0e709c-4166-48b0-9fe0-55840f00e139%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
> > For more options, visit https://groups.google.com/d/optout

> <https://groups.google.com/d/optout>.

>
>
> --
> Osma Suominen
> D.Sc. (Tech), Information Systems Specialist
> National Library of Finland
> P.O. Box 26 (Kaikukatu 4)
> 00014 HELSINGIN YLIOPISTO
> Tel. +358 50 3199529
> osma.s...@helsinki.fi <javascript:>
> http://www.nationallibrary.fi
>
> --
> You received this message because you are subscribed to the Google
> Groups "Skosmos Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to skosmos-user...@googlegroups.com

> <mailto:skosmos-user...@googlegroups.com>.

> To post to this group, send email to skosmo...@googlegroups.com
> <mailto:skosmo...@googlegroups.com>.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/skosmos-users/6558ad52-1ccc-4d66-ad53-115d60051bb5%40googlegroups.com
> <https://groups.google.com/d/msgid/skosmos-users/6558ad52-1ccc-4d66-ad53-115d60051bb5%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Armando Stellato]

Dear all,

a couple replies to both Osma's previous email and Sandor's one.

Yes Osma you are right, VB should do that export...and actually we added this option, except that a bug in VB2.3 related to a misalignment between API calls between that version of VB and the underlying ST server caused it not to work. It has already been fixed and it will be available in the next version of VB (ETA end of 2015).

The transformation of content does not require only SKOSXL Labels, but also reified skos definitions. See the link below for more details and for pointers on how to deal with them
http://vocbench.uniroma2.it/documentation/faq.jsf

the OWLART include that utility or, if you want to go through SPARQL, this is the other UPDATE you need to do in order to flatten the skos definitions as well

--cut--
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX skosxl: <http://www.w3.org/2008/05/skos-xl#>
INSERT {

?c skos:definition ?def .
}
WHERE {
?c skos:definition/rdf:value ?def .
}
--cut--

Or, if you still didn't run the one Osma gave you, this is a complete version that includes the definitions into the Osma's UPDATE for the labels.

--cut--
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>

PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX skosxl: <http://www.w3.org/2008/05/skos-xl#>
INSERT {
?c skos:prefLabel ?pref .
?c skos:altLabel ?alt .
?c skos:hiddenLabel ?hidden .

?c skos:definition ?def .

}
WHERE {
{ ?c skosxl:prefLabel/skosxl:literalForm ?pref }
UNION
{ ?c skosxl:altLabel/skosxl:literalForm ?alt }
UNION
{ ?c skosxl:hiddenLabel/skosxl:literalForm ?hidden }

UNION
{ ?c skos:definition/rdf:value ?def } }
--cut--

Cheers,

Armando

> email to skosmos-user...@googlegroups.com.
> To post to this group, send email to skosmo...@googlegroups.com.

> To view this discussion on the web visit
> https://groups.google.com/d/msgid/skosmos-

> users/5614E1FC.7070805%40helsinki.fi.

[Osma Suominen]

Hi Armando!

Quick comment: you are right about the definitions, but Skosmos already
supports VocBench-style reified definitions (see
https://github.com/NatLibFi/Skosmos/issues/146) so it is not absolutely
necessary to convert them if all you care about is displaying them in
Skosmos.

-Osma

[Armando Stellato]

Oh, that's great!
Sorry was not updated on that :-)
However, at least in case the SPARQL endpoint used by SKOSMOS is also the one used for publishing the data as LOD, it might be better to flatten that info as well, so other less-savvy clients can read it properly.

[Thomas Francart]

Hi Osma

[Armando]

Speaking of publishing system, maybe SKOSMOS could also be turned
into a publishing system (i.e. resolve URI dereferenciation for all
hosted resources). Not a general triple publisher such as Pubby, not
as reconfigurable as Loddy, but very much verticalized on thesauri,
mixing up http dereferenciation with the already existing browsing
possibilities. Again, maybe not too much to implement, and a great
value added to the existing system.

It can already be used that way - Skosmos can obviously provide HTML
pages for concepts, and the Skosmos REST API can serve
content-negotiated RDF responses (RDF/XML, Turtle, JSON-LD) of concept
information. What is missing is the first point of access that needs to
perform a 303 redirect to the appropriate representation - this is
generally outside the control of Skosmos, of course depending on the URI
design (but I'd hate to see a /skosmos/ part in actual concept URIs).

For Finto and YSO, we have implemented redirection rules for the
www.yso.fi domain as rather simple Apache mod_rewrite rules that
redirect to the Skosmos installation according to the Accept header. Try
for example:

wget --header 'Accept: text/html' http://www.yso.fi/onto/yso/p1234
wget --header 'Accept: text/turtle' http://www.yso.fi/onto/yso/p1234

Could you share the set of redirection rules you use at the Apache level to implement this ? or even put this in the documentation, since this is quite a common requirement ?

Thanks !

Thomas

[Osma Suominen]

Hi Thomas!

On 25/11/15 18:36, Thomas Francart wrote:

> Could you share the set of redirection rules you use at the Apache level
> to implement this ? or even put this in the documentation, since this is
> quite a common requirement ?

Sure, good request :)

Here is what we have (among other rules that probably aren't relevant to
you) in the Apache configuration for the www.yso.fi virtual host:


# redirect to RDF for Linked Data agents
RewriteCond %{HTTP_ACCEPT} application/rdf\+xml [OR]
RewriteCond %{HTTP_ACCEPT} text/turtle [OR]
RewriteCond %{HTTP_ACCEPT} application/ld\+json [OR]
RewriteCond %{HTTP_ACCEPT} application/json
RewriteRule ^/onto/([^/]+)/(.*)
http://api.finto.fi/rest/v1/$1/data?uri=http://www.yso.fi/onto/$1/$2 [R=303]

# redirect to HTML for everyone else
RewriteRule ^/onto/([^/]+)/$ http://finto.fi/$1/ [R=303]
RewriteRule ^/onto/([^/]+)/(.*) http://finto.fi/$1/page/$2 [R=303]


I must say these rules aren't perfect, for example they don't do proper
content negotiation between HTML and RDF if the client supports both but
prefers HTML (in that case, the redirect still goes to the RDF version).

I think that Skosmos could actually provide an entry point which would
perform a 303 redirect to either HTML or one of the RDF versions based
on content negotiation. I've created an issue for this:

https://github.com/NatLibFi/Skosmos/issues/359

Then the required configuration outside Skosmos could be just a single
mod_rewrite rule (see issue).

[Thomas Francart]

Thanks a lot for your help, this is very useful.

Thomas

[Bruno Kinoshita]

Hi Osma!

Late to party, but answers inline :)

> 1. What do you use (or planning to use) Skosmos for and how? 

NIWA (niwa.co.nz) collects several types of data, and make great part of it publicly available. We are evaluating SKOS solutions, like SKOSMOS and SISSVOC from CSIRO. The 

> 2. Does Skosmos work in your scenario? If not, what are the problems? 

We are still assessing it, so that's a WIP. So far I think it works for most use cases. We have several tools (e.g. Geoserver, Geonetworks, IPT, QGIS, in-house built tools) and our intention is to integrate the SKOS vocabulary service with these tools. In special with services that implement OGC standards like WFS, WMS, SOS, SensorThingsAPI, etc.

>3. How would you like Skosmos to be developed in the future? 

The same as now I believe. the project is active and has a healthy community. Furthermore it has a dependency/integration to Jena, and one of the maintainers of Skosmos is also a committer in Jena :) which is a great benefit for both projects.

>4. Do you, or your organization, expect to contribute to Skosmos 
development in the future and if so, how? For example, user interface 
translations, bug reports and fixes are always welcome, as well as 
larger contributions for new features. 

Definitely. I already got permission and CLAs for Geoserver and 52North SOS. Skosmos and SISSVOC, whatever we choose to use, we can help with development and sometimes sponsoring events or even development.

Thanks!

Bruno