Open bertvannuffelen opened 1 year ago
Thanks @bertvannuffelen, PR #1572 implements your suggestions. I've noticed the negotiation for the W3C served URIs (http://www.w3.org/ns/adms#xxx) brings to a non-W3C host. May I ask what the development perspective for ADMS is in the future?
@riccardoAlbertoni It is explained in this webinar https://joinup.ec.europa.eu/collection/semic-support-centre/event/first-webinar-adms. But in short, the future is
Unless the community raises new use-cases I expect that this version will be stable for a long period.
@bertvannuffelen , the version of ADMS considered by the WG when discussing the re-use of its properties / classes in DCAT3 is the one in W3C space.
Pointing to another document would require a thorough review of it by the WG.
BTW, as far as I can understand, ADMS 2.0, by decoupling ADMS from DCAT (as stated in https://semiceu.github.io/ADMS/releases/2.00/#motivation-for-this-version), cannot be considered equivalent to the version in W3C space.
Hi,
lately ADMS got a new release. The new release did not changed any semantics of the terms, but now there is content negotation on the namespace and the usage beyond DCAT of ADMS is made easier By processing the DCAT specification, I spotted different usages how the ADMS terms are referenced. In brackets is the motivation for the change.
versionNotes => the link for the RDF property should be http://www.w3.org/ns/adms#versionNotes (the URI and not to the html specification, like for other properties)
status => the link for the RDF property should be http://www.w3.org/ns/adms#status (the URI and not the html specification, like for the other properties)
under example https://w3c.github.io/dxwg/dcat/#ex-proxy-id => the link for the RDF property adms:identifier should be http://www.w3.org/ns/adms#identifier (the URI will dereference to the html now and thus the link is agnostic to the publication location) => the link for the RDF property adms:schemaAgency should be http://www.w3.org/ns/adms#schemaAgency (the URI will dereference to the html now and thus the link is agnostic to the publication location)