semiceu / adms Goto Github PK

Problem statement
The definition of representation technique currently says:

More information about the format in which an Asset Distribution is released. This is different from the file format as, for example, a ZIP file (file format) could contain an XML schema (representation technique).

However, talking here about a ZIP file (package) containing an XML schema inside seems confusing in the context of DCAT-AP Distribution Packaging Format, which would normally be used (for ZIP) together with media type (for XML schema) for this type of scenario.

This was identified in SEMICeu/GeoDCAT-AP#97.

Proposal
Change the definition simply to:

More information about the format in which an Asset Distribution is released.

Explain your issue

In DCAT-AP adms:sample is used to express a sample for a dataset.
As range is has in DCAT-AP dcat:Distribution.
As adms:Asset originally was a subclass of dcat:Dataset and within DCAT the notions dataset and distribution are distinct, the proposal is to lift the range to rdfs:Resource so that users of this property can set the range to their needs.

It avoids possible discussions on the applicability triggered by the possible disjointness of the range classes set in the ADMS vocabulary and the intended usage in the target specification.

The revision of ADMS from a DCAT profile to a broad vocabulary scoped on terms within its namespace was welcomed during the webinar of 24 April 2023.

However, as a consequence the classes adms:AssetRepository, adms:Asset and adms:AssetDistribution got disconnected, because the connecting properties dcat:dataset and dcat:distribution are omitted.

The proposal was made to introduce these 2 terms to make the ADMS vocabulary coherent and standalone.

In the RDF serialization there is adms:schemeAgency defined, while in the html there is adms:schemaAgency.
The difference is in the character 'e' and 'a'.

The html will be followed and thus the RDF serialization is adapted.

This may be due to my lack of experience with this type of documentation, but I am struggling to understand how to fully document an identifier of a particular scheme. The identifier documentation says the object can contain:

content string that is the identifier;
an optional identifier for the identifier scheme;
an optional identifier for the version of the identifier scheme;
an optional identifier for the agency that manages the identifier scheme.

What would be an example, preferably in JSON-LD, of an Identifier object implementing all of these optional identifiers?

Explain your issue

Was schemaAgency intentionally renamed? There is now issue with the identifier and it is called and referred as schemeAgency from multiple vocabularies.

For example https://semiceu.github.io/Core-Business-Vocabulary/releases/2.1.0/context/core-business-ap.jsonld refers it as schemeAgency.

URIs should not change.