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
Work is being done by the W3C DataExchange Working Group on a specification for the so called Profile Negotiation. See the following documents1,2 for more info. Among other things, this specification makes it possible to negotiate with a linked data resource to deliver the data in a specific data model for example in schema.org or RiC-O.
We could do a experimental implementation of this spec to support a more fine grained way of negotiating with the Datasetregister to offer dataset in a specific distribution. As an example in the near future RKD will start publishing datasets both modelled in Schema.org and Linked Art. In addition we could build this service out to drive on-the-fly transformation of data based on sparql construct queries. Using this (draft) specification offers us generic approach for this type negotiation on the HTTP level without having to develop and implement a customized API for this purpose.
The text was updated successfully, but these errors were encountered:
Work is being done by the W3C DataExchange Working Group on a specification for the so called Profile Negotiation. See the following documents1,2 for more info. Among other things, this specification makes it possible to negotiate with a linked data resource to deliver the data in a specific data model for example in schema.org or RiC-O.
We could do a experimental implementation of this spec to support a more fine grained way of negotiating with the Datasetregister to offer dataset in a specific distribution. As an example in the near future RKD will start publishing datasets both modelled in Schema.org and Linked Art. In addition we could build this service out to drive on-the-fly transformation of data based on sparql construct queries. Using this (draft) specification offers us generic approach for this type negotiation on the HTTP level without having to develop and implement a customized API for this purpose.
The text was updated successfully, but these errors were encountered: