This document was used for discussion in the Working Group and is no longer maintained.
Go to the release section (https://joinup.ec.europa.eu/asset/adms_foss/release/all) to download the latest version of ADMS.SW.
The section identifies a number of controlled vocabularies to be used for specific concepts in the ADMS.F/OSS specification. In this section, the term “vocabulary” is used as shorthand for various types of controlled vocabularies, including taxonomies (collections of controlled category labels or notations representing concepts in a hierarchical structure), thesauri (networked collections of controlled terms representing concepts in a networked structure) and other types of knowledge organisation systems.
In general, reuse of controlled collections of terms is recommended as far as possible. Where such collections do not exist, repository owners should consider creating and maintaining such collections to ensure consistent description.
Controlled Vocabularies specific to software assets
Forges based on the Savane, SourceForge, GForge, and FusionForge software have developed a software classification schema to classify open-source software. The Trove software map can be tailored to fit each repository's specific needs.
More information can be found on SourceForge: http://sourceforge.net/apps/trac/sourceforge/wiki/Software Map and Trove
An initial proposal was received by Elena Muñoz Salinero, based on a detailed study (Anexo IV: Estudio Taxonomías Forjas, 2011) by the Spanish F/OSS Competence Centre CENATIC. This study compares all taxonomies implemented by the Spanish forges, OSOR and some relevant forges (SourceForge, Launchpad, GoogleCode, Github). The conclusion of this study is that many of the forges share many taxonomies and it was proposed a minimum set of characteristics to be shared in the interchanging of projects and of course, and optional set of characteristics.
The document ADMS.F-OSS Controlled Vocabularies-v0.04.ods givens an overview of proposed taxonomies to classify software to be discussed with the Working Group on February 21 2012.
Licence
The SPDX specification includes a controlled vocabulary of licences: http://www.spdx.org/licenses/. Every licence listed here has an SPDX identifier and a term URI.
Operating System
This has potential values like
- Console (text based)
- Without input/output (service, daemon, api)
- Desktop
- Others
We'd have to create such a taxonomy ourselves.
Intended audience
A vocabulary for this could be useful beyond ADMS.F/OSS (good!). The proposed types of Public Administrations, citizens, enterprises and developer communities could perhaps be extended. I can't find an exact match in an existing vocabulary so maybe we should define one as part of ADMS.F/OSS? If so, I think it needs to be easily extensible.
User interface type
Development status
Programming language
DBpedia has stable URIs for all programming languages, e.g. http://dbpedia.org/resource/C++
Localizations
RFC 3066 provides a list of languages and locales used extensively in things like XML schema.
Controlled vocabularies to describe assets
We propose to adopte the controlled vocabularies defined in the ADMS specificaiton.
Domain
The proposed vocabulary for Domain is the domain level of EuroVoc.
|
ADMS Domain (EuroVoc eu:Domain) |
URI |
|
04 POLITICS |
|
|
08 INTERNATIONAL RELATIONS |
|
|
10 EUROPEAN COMMUNITIES |
|
|
12 LAW |
|
|
16 ECONOMICS |
|
|
20 TRADE |
|
|
24 FINANCE |
|
|
28 SOCIAL QUESTIONS |
|
|
32 EDUCATION AND COMMUNICATIONS |
|
|
36 SCIENCE |
|
|
40 BUSINESS AND COMPETITION |
|
|
44 EMPLOYMENT AND WORKING CONDITIONS |
|
|
48 TRANSPORT |
|
|
52 ENVIRONMENT |
|
|
56 AGRICULTURE, FORESTRY AND FISHERIES |
|
|
60 AGRI-FOODSTUFFS |
|
|
64 PRODUCTION, TECHNOLOGY AND RESEARCH |
|
|
66 ENERGY |
|
|
68 INDUSTRY |
|
|
72 GEOGRAPHY |
|
|
76 INTERNATIONAL ORGANISATIONS |
Subject
Many candidate vocabularies are available for Subject. Examples are the European Commission’s ECLAS Thesaurus and EuroVoc, EIONET’s GEMET, FAO’s AGROVOC, ZBW’s STW Thesaurus for Economics, the Library of Congress’ Subject Headings (LCSH) and Thesaurus for Graphic Materials (TGM)33 and others, The use of these vocabularies is closely linked to the domain to which t an Asset is related. It is recommended that terms should be assigned from a vocabulary that is most widely used in the domain covered.
Nature of documentation: Technical report