You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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)
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?
a joined collaboration between the SEMIC team and W3C for this vocabulary
no major changes are to be expected in the near future as the objectives are
to fresh up the specification ADMS to become a living specification with a community to address issues to
reduce the strong ties between ADMS and DCAT, so that ADMS terms can be used independently (current practice already, but that use was not according to the specification intentions.)
Unless the community raises new use-cases I expect that this version will be stable for a long period.
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)
The text was updated successfully, but these errors were encountered: