Re: [dxwg] question > is a software solution a dcat:Dataset? (#1221)

In terms of interoperability assets, **ADMS-AP for Joinup** consideres **_software solutions_** to be **_datasets_**. (reference to makxdekkers' comment on 4 Mar)

> the Application Profile is used for the aggregation of information about interoperability assets (controlled vocabularies, metadata schemas) and software solutions by the federated repositories on the Joinup platform, online collections of interoperability solutions maintained by European public administrations, businesses and citizens.

The software solution asset LEOS (Legislation Editing Open Software) is described as a dcat:Dataset: 
HTML on JoinUp - 
TTL metadata - (snippet below)

  a dcat:Dataset ;
  dc:type <>, <> ;
  dc:title "LEOS - Open Source software for editing legislation"@en ;  
  dc:description "LEOS Legislation Editing Open Software, is an open source software delivered under ISA² Action 2016.38 Legislation Interoperability Tools – LegIT
ADMS-AP for Joinup version 2.0 removes all use of Asset Description Metadata Schema for Software (admssw) which has been deprecated, and now solely seems to rely on ADMS for the description of Assets. Also, assets are classified using EIRA 

However, prior to the ADMS revision, it was commented that using just one specification for datasets, standards and software might make the specification less understandable. Also, the number of relevant asset layers (for software releases) also appreaded to present different implementation options. (See revision discussion:

GitHub Notification of comment by aidig
Please view or discuss this issue at using your GitHub account

Received on Tuesday, 14 April 2020 10:20:07 UTC