ADMS.SW is intended as a model that facilitates federation and co-operation. It is not the primary intention that forge owners redesign or convert their current systems and data to conform to ADMS./FOSS, but rather that ADMS.SW can act as a common layer among software forges that want to exchange data.
Status of this document
This section describes the status of this document at the time of its publication. Other documents may supersede it.
This document has been developed and reviewed by representatives of the Member States of the European Union, PSI publishers, and by other interested parties. Publication of this Draft for public review does not imply endorsement by the European Commission or its representatives. This is a draft document and may be updated, replaced or made obsolete by other documents at any time. It is inappropriate to cite this document as other than work in progress. The Working Group will seek further endorsement by the Member State representatives in the ISA Coordination Group or the Trusted Information Exchange Cluster.
Comments on the vocabulary are invited via the forum.
Table of Contents
Introduction
Asset Description Metadata Schema for Software (ADMS.SW) was developed under the European Commission's ISA Programme. This is the namespace document, generated from the associated RDF schema. Full documentation is provided in the specification document itself. This includes background information, use cases, the conceptual model and full definitions for all terms used.
Namespace
The URI for this vocabulary is
http://purl.org/adms/sw/
When abbreviating terms the suggested prefix is admsf
Each class or property in the vocabulary has a URI constructed by appending a term name to the vocabulary URI. For example:
http://purl.org/adms/sw/SoftwareProject
Vocabulary Terms at a Glance
Asset Description Metadata Schema for software (ADMS.SW) UML Class Diagram
A Software Project is a time-delimited, often collaborative undertaking with the objective to produce one or more software releases, materialised as software packages.
A Software Release is an abstract entity that reflects the intellectual content of the software and represents those characteristics of the software that are independent of its physical embodiment. This abstract entity corresponds to the FRBR entity expression (the intellectual or artistic realization of a work). An example of a Software Release is the Apache HTTP Server 2.22.22 (httpd) release.
A Software Package represents a particular physical embodiment of a Software Release, which is an example of the FRBR entity manifestation (the physical embodiment of an expression of a work). A Software Package is typically a downloadable computer file (but in principle it could also be a paper document) that implements the intellectual content of a Software Release. A particular Software Package is associated with one and only one Software Release, while all Packages of a Release share the same intellectual content in different physical formats. An example of a Software Package is httpd-2.2.22.tar.gz , which represents the Unix Source of the Apache HTTP Server 2.22.22 (httpd) software release.
A Software Repository is a system or service that provides facilities for storage and maintenance of descriptions of Software Projects, Software Releases and Software Distributions, and functionality that allows users to search and access these descriptions. A Software Repository will typically contain descriptions of several Software Projects, Software Releases and related Software Distributions.
A Repository is a system or service that provides facilities for storage and maintenance of descriptions of Releases and Distributions. A Repository will typically contain descriptions of several Assets and functionality that allows users to search and access these descriptions. The Distributions - the actual files themselves - will typically be available from the Repository or elsewhere on the World Wide Web.
VCard fully represents the ADMS.SW class of Contact Information
Usage Note
ADMS.SW uses VCard to provide contact information regarding a Software Release, including e-mail, address, name and associated Web page information. See Representing vCard Objects in RDF for details of this widely used specification.
The dcterms:LicenseDocument class fully represents the RADion concept of a Licence
Usage Note
Used in RADion to provide the conditions or restrictions that apply to the use of a Distribution, e.g. whether it is in the public domain, or that some restrictions apply like in cases attribution is required, or the Asset can only be used for non-commercial purposes etc.
A Distribution is a particular representation or concretisation of an Asset in the form of a downloadable computer file that implements the intellectual content of an Asset. A particular Distribution is typically associated with one Asset.
A Software Asset is an abstract entity that reflects the intellectual content of the software and represents those characteristics of the software that are independent of its physical embodiment. This abstract entity corresponds to the FRBR entity expression (the intellectual or artistic realization of a work). An example of a Software Asset is the Apache HTTP Server 2.22.22 (httpd) asset.
The Conceptual Model includes a 'Code' datatype that is used by several classes. This is expressed using the href="http://www.w3.org/TR/skos-primer/">SKOS vocabulary with a particular 'code' usually being a skos:Concept that is part of a scheme. The intention is that the skos:Concept class be used as follows:
for the content property, use skos:notation
he 'list' property will be taken care of by means of the skos:inScheme property;
the list agency property is likely to be applied to the scheme as a whole for which dcterms:creator is appropriate
The skos:Concept class fully represents the ADMS.SW classes 'Intended Audience', 'Locale', 'Operating System', 'Status', 'Topic', and 'User Interface Type' (see section on the Code datatype for details).
The foaf:Document class fully represents the ADMS.SW concept 'Documentation'.
Usage Note
Used in ADMS.SW specifically for the class of documents that further describe a Software Asset or give guidelines for its use. ADMS.SW expects all documents to have a title (use dcterms:title).
This class is based on the UN/CEFACT Identifier complex type defined in See Section 5.8 of Core Components Data Type Catalogue Version 3.1. The various properties can be fulfilled as follows:
use skos:notation to provide the actual identifier (the Identifier class is effectively meaningless without this property and conceptually it is mandatory)
use dcterms:type to provide an identifier for the type of identifier issued (the identifier scheme)
use adms:schemeVersion to identify the version of the identifier scheme;
use adms:schemeAgency to provide the name of the agency that created the identifier (as an rdfs:Literal).
Although not part of the ADMS conceptual model, it may be useful to provide further properties to the Identifier class:
use dcterms:creator to link to a URI of an Agent class describing the issuing Agency;
use dcterms:created to provide the date on which the identifier was issued.
A Software Identifier is a complex type (based on the software identifying system in the ISO19770-2:2009 software identification tag data model [ISO19770-2]) consisting of: a unique token within the regid domain of the tag creator and a tag creator regid.
Usage Note
Used in ADMS.SW to aligin with the software identifying system in the ISO19770-2:2009 standard.
The SPDX class 'Checksum' fully represents the ADMS.SW type with the same name. A Checksum is value that allows the contents of a file to be authenticated. Even small changes to the content of the file will change it's checksum. This class allows the results of a variety of checksum and cryptographic message digest algorithms to be represented.
The dcterms:created property fully represents the ADMS.SW property 'date of creation'.
Usage Note
The ADMS.SW and RADion RDF Schemas use this to provide the creation date of this version of the Repository, Asset or Package. RADion expects a datatyped value and for it to be conformant with ISO 8601, preferably using an xsd data type.
The dcterms:publisher property fully represents the RADion and ADMS.SW relationship of the same name
Usage Note
Used in RADion and thus ADMS.SW to link to the organisation responsible for the publication of the Asset, Repository or Distribution. Note that the range is dcterms:Agent.
The distributionOf relationship associates a Distribution (its domain) with the Asset (its range) of which it is a Distribution. It is the inverse of distribution
description
Type of Term
Property
QName
doap:description
URI
http://usefulinc.com/ns/doap#description
Definition
Both the dcterms:description and doap:description properties fully cover the ADMS.SW property of the same name. It would be better if doap:description were defined as a sub-property of dcterms:description.
A data set of metrics about the software project or software release.
Usage Note
The range of this property is not fixed by the ADMS.SW specification. It is recommended to related this property to an instance of the class 'qb:DataSet'.
The theme taxonomy relationship associates a Repository with a classification scheme for the assets within it. Its domain is rad:Repository and its range is skos:ConceptScheme.
The dcterms:modified property fully represents the RADion and ADMS.SW property Date of Last Modification.
Usage Note
RADion uses this to provide the date of latest update of the Repository, Asset or Package. RADion expects a datatyped value and for it to be conformant with ISO 8601, preferably using an xsd data type.
The distribution relationship associates an Asset (its domain) with a Distribution (its range). In the case of software, it associates a Software Release (its domain) with a Software Package (its range). It is the inverse of distributionOf
The dcterms:coverage property fully represents the RADion relationship of the same name
Usage Note
RADion uses this to link to the geographic region or jurisdiction that the Asset or Repository applies to. Note that the range is dcterms:LocationPeriodOrJurisdiction of which rad:GeographicalCoverage is a sub class.
Conformance Statement
A conformant implementation of this vocabulary MUST understand all vocabulary terms defined in this document.
Document generated from the RDF schema using this XSLT
