What #skos editors do you know / use ?
What is easy to use/install and free ?
#skos
1 post1 participant0 posts today
Hulp gevraagd!
Werkt jouw #overheidsorganisatie met #begrippenlijsten, #linkeddata of allebei? Vul dan uiterlijk woensdag 25 juni onze enquête in. Dit kost je maar een paar minuten. Jouw inzichten helpen ons om een beter beeld krijgen van het gebruik van linked data bij overheden, in het bijzonder #openstandaard #skos
De enquête verzamelt geen persoonsgegevens.
Vul hier de enquête in:https://ec.europa.eu/eusurvey/runner/onderzoek-linked-data-overheid
@DigitaleOverheid @pldn @nora @developer @digilab @NetwerkDigitaalErfgoed
Replied in thread
@datenschatz Für die Nordrhein-Westfälische Bibliographie haben wir mal die frei Ortsverschlagwortung ersetzt durch einen kontrollierten Ansatz auf Basis von #Wikidata und #SKOS: https://journal.code4lib.org/articles/15875
Die Einträge der Raumsystematik werden seitdem von Bibliothekar:innen in Wikidata gepflegt.
The Code4Lib Journal · How We Built a Spatial Subject Classification Based on WikidataFrom the fall of 2017 to the beginning of 2020 a project had been carried out to upgrade spatial subject indexing in North Rhine-Westphalian Bibliography (NWBib) from uncontrolled strings to controlled values. For this purpose, a spatial classification with around 4,500 entries was created from Wikidata and published as SKOS (Simple Knowledge Organization System) vocabulary. [...]
EVOKS (Editor for Vocabularies to Know Semantics) "allows you to:
- create a #SKOS vocabulary from scratch
- import SKOS vocabularies in RDF/XML or Turtle format
- edit SKOS vocabularies without using its textual representation
- work collaborativley
- publish the vocabulary with a single click in the vocabulary browser #skosmos
https://github.com/kit-data-manager/EVOKS
Has anybody tried it out yet? /cc @nichtich @osma @steffenr42
GitHubGitHub - kit-data-manager/EVOKS: EVOKS (Editor for Vocabularies to Know Semantics)EVOKS (Editor for Vocabularies to Know Semantics). Contribute to kit-data-manager/EVOKS development by creating an account on GitHub.
Gastvortrag von Felix Kraus @KIT_Karlsruhe upcoming! 
Herzliche Einladung ins Kolloquium Computerphilologie: Di, 10. Juni um 18.00 Uhr 
NFDI4Objects war auf dem SODa-Barcamp!
Vom 7.-9. April 2025 fand in Nürnberg das @SODa Barcamp statt (https://sammlungen.io/archive/soda-barcamp-2025). Unsere Kollegin Kristina Fischer aus Task Area 4 war dabei und gab Einblick in ihre praktische Arbeit mit #kontrolliertenVokabularen, #SKOS und der Entwicklung eines #Thesaurus für #Konservierung und #Restaurierung. Drei spannende Tage wurden Themen wie #Digitalisierung, #Sammlungen und Umgang mit #Forschungsdaten diskutiert und verschiedene Blickwinkel beleuchtet. 1/2
Last November we organized a survey for Annif users, and now the results have been published in the Doria repository of the National Library of Finland:
https://urn.fi/URN:ISBN:978-952-84-1301-1
The report includes an overview of:
- The vocabularies and datasets that are used with Annif
- The workflows that Annif is integrated with
- The problems Annif users are facing
urn.fiDoria: Annif Users Survey: Understanding Usage and Challenges
The first alpha version of Skosmos 3 has been published! This release provides a peek into the upcoming next major version of the Skosmos publishing tool for SKOS controlled vocabularies.
The release features a reimplemented front-end with a fresh layout and improved accessibility, as well as many architectural improvements and modernization of the codebase.
https://github.com/NatLibFi/Skosmos/releases/tag/v3.0-alpha.1
GitHubRelease Skosmos 3.0-alpha.1 · NatLibFi/SkosmosThis is the first alpha release of Skosmos 3.0 that provides an early peek into the upcoming final 3.0 release. It is mainly intended for Skosmos users who want to plan ahead for the 3.0 release. Y...
Version 1.3 of the automated subject subject indexing tool #Annif has been released!
This release introduces support for the EstNLTK analyzer for better Estonian lemmatization 
, optimizations to the MLLM backend, as well as maintenance and bug fixes, including better file permissions in multi-user environments.
GitHubRelease Annif 1.3 · NatLibFi/AnnifThis release introduces a new EstNLTK analyzer, improves the performance of the MLLM backend and fixes minor bugs.
The key enhancement of this release is the addition of a new analyzer for lemmatiz...
Continued thread
3. Widgets Wednesday #3 :
#Sparnatural tree widget 
The tree widget allows to select entities from a tree of values, typically a #SKOS ConceptScheme. Max. 3 values can be selected. Tree widget is implemented using the JS tree library.
See the documentation :
https://docs.sparnatural.eu/widgets.html#tree-widget
Continued thread
"Publish & reconcile against #SKOS vocabularies with #SkoHub", a #SWIB24 workshop in the Americas timeslot (17:00-21:00 UTC on 25 November), facilitated by @steffenr42, @tobiasnx & @Maipet. From the workshop description: "This hands-on workshop will guide participants through the process of publishing controlled vocabularies encoded in SKOS using SkoHub Pages. After that we will see how to use these vocabularies in reconciliation tasks with SkoHub Reconcile." Sign up at https://forum.swib.org/t/workshop-publish-reconcile-against-skos-vocabularies-with-skohub/138/1
SWIB Forum · 🔨 Workshop: Publish & reconcile against SKOS vocabularies with SkoHubFacilitator(s) Steffen Rörtgen (@sroertgen) , Petra Maier (@maipet) , Tobias Bülte (@tobiasNx) Agenda This hands-on workshop will guide participants through the process of publishing controlled vocabularies encoded in SKOS using SkoHub Pages. SkoHub Pages offers an efficient way to publish vocabularies in both human and machine-readable formats without requiring an additional server using GitHub Pages. After that we will see how to use these vocabularies in reconciliation tasks with SkoHub Re...
Die Folien zum @digiSberlin - Workshop zu #SKOS und #Thesauri von Ende September liegen jetzt hier: https://doi.org/10.5281/zenodo.13918574
ZenodoSKOS-Vokabulare. Von der einfachen Liste zum maschinenlesbaren VokabularMaterial zum SKOS-Workshop am 24. September 2024.
Replied to digiSberlin
@digiSberlin Der #SKOS-Workshop zeigte, dass vielen #GLAM|s eigene, domänenspezifische und offene #Thesauri ein Anliegen, aber Pflege, Bereitstellung und Nachnutzung auch wegen des sehr heterogenen Toolings nicht gerade trivial sind. Wir haben uns quellennah mit dem PDF-Thesaurus (https://coilink.org/20.500.12592/22sjdv) unseres ehem Projektpartners #DZI (https://www.digis-berlin.de/projekte/archiv/projekte-20222023/#tab-tb_km53655-5) beschäftigt, die Daten zunächst manuell, dann per Skript in Turtle überführt und schließlich die Publikation per @skohub diskutiert.
policycommons.netDZI-Thesaurus - alphabetische Sortierung DZI- Thesaurus | Policy Commons<bound method Artifact.get_generated_summary of <Artifact: DZI-Thesaurus - alphabetische Sortierung DZI- Thesaurus>>
Wir freuen uns darauf heute die Teilnehmer:innen des #SKOS Workshops bei uns am Zuse Institute Berlin zu begrüßen
.
Unsere Kollegen Marco Klindt und @awinkler führen heute ein in die Welt der Vokabulare und sprechen über die Nutzung des #SimpleKnowledgeOrganizationSystem.
Hulp gevraagd!
Werkt jouw #overheidsorganisatie met #begrippenlijsten, #linkeddata of allebei? Vul onze enquête in (uiterlijk 4 augustus). Dit kost je maar een paar minuten en jouw inzichten helpen ons om een beeld krijgen van het gebruik van linked data bij overheden, in het bijzonder #openstandaard #skos.
Vul de enquête in: https://ec.europa.eu/eusurvey/runner/onderzoek-linked-data-overheid
ec.europa.euGebruikt uw organisatie linked data?
I've been reminding myself of everything #RDF / #SKOS / #OWL-related with this helpful book:
https://www.sciencedirect.com/book/9780123859655/semantic-web-for-the-working-ontologist
I only need RDFS & SKOS, but how do semantic data scientists decide if the full range of OWL features is computationally (and energetically) suitable for use on large datasets?
Set relationships & cardinality imply a need either to materialise or else to compute (nearly) all implied triples before answering any query.
When do you cut over to more targeted software strategies?
Just having a look at the documentation of the Glycerine #IIIF viewer component, and I notice that the examples for annotations with a #SKOS vocabulary use our #DiGA thesaurus for Buddhist art as an example. 
https://github.com/Systemik-Solutions/glycerine-viewer
GitHubGitHub - Systemik-Solutions/glycerine-viewer: A VUE IIIF viewerA VUE IIIF viewer. Contribute to Systemik-Solutions/glycerine-viewer development by creating an account on GitHub.
Continued thread
Püntklich zum zweiten Tag des #4CultureForum "Brücken schlagen zwischen Terminologien: Herausforderungen und Perspektiven" haben wir einen Blogpost zur einfachen GitHub-basierten Publikation von #SKOS-Vokabularen veröffentlicht: https://blog.skohub.io/2024-03-21-skohub-pages/
blog.skohub.ioPublishing SKOS the easy wayA simple workflow for publishing your vocabs With SkoHub Pages we now provide a very simple way for publishing your SKOS vocabulary from a GitHub repository. It…
We are happy to announce SkoHub Pages which enables a simple process to publish your #SKOS vocabularies from GitHub without your own server: https://blog.skohub.io/2024-03-21-skohub-pages/
blog.skohub.ioPublishing SKOS the easy wayA simple workflow for publishing your vocabs With SkoHub Pages we now provide a very simple way for publishing your SKOS vocabulary from a GitHub repository. It…