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
Support returning RDF-based responses from the F-UJI API next to the current JSON-based response.
The responses should ideally make use of standard vocabularies, like DQV and PROV to represent the assessment data.
The RDF representation should not be specific to F-UJI, such that other methods of assessment could adopt the same representation. This would help to create a robust ecosystem of different tools in this space that could be used interchangeably or in a complementary fashion.
To be able to use the FAIR assessment data and incorporate it into other RDF-based (meta)data sources it would be very useful to be able to request the assessment report represented in RDF, next to the current JSON responses.
Possible Implementation
This could be implemented by supporting content-negotiation via the accept header. If a supported RDF media type is requested an RDF response can be returned instead of the default JSON-based response.
The text was updated successfully, but these errors were encountered:
Detailed Description
Support returning RDF-based responses from the F-UJI API next to the current JSON-based response.
The responses should ideally make use of standard vocabularies, like DQV and PROV to represent the assessment data.
The RDF representation should not be specific to F-UJI, such that other methods of assessment could adopt the same representation. This would help to create a robust ecosystem of different tools in this space that could be used interchangeably or in a complementary fashion.
The FAIR metrics should be linked to the FAIR vocabulary
Context
To be able to use the FAIR assessment data and incorporate it into other RDF-based (meta)data sources it would be very useful to be able to request the assessment report represented in RDF, next to the current JSON responses.
Possible Implementation
This could be implemented by supporting content-negotiation via the accept header. If a supported RDF media type is requested an RDF response can be returned instead of the default JSON-based response.
The text was updated successfully, but these errors were encountered: