search

metno / S-ENDA-documentation

Temporary documentation and use case descriptions for the S-ENDA project - when concepts are tested and verified, content is gradually moved to more long term solutions.
https://s-enda-documentation.readthedocs.io/
2 stars 6 forks source link

Describe interface for provenance data for distribution services #198

Closed havardf closed 1 year ago

mortenwh commented 3 years ago

@havardf - can you clarify what needs to be done here?

havardf commented 3 years ago

I am a bit rusty about the context here. I think though it relates to the more general problem about how custom distribution services, like the frost and api.met.no should provide metadata about how their data was produced.

Eg. should the service itself provide a DCAT-AP-NO v.2.0 document describing the service, its data and the provenance of its data? Or is it best to expect those kinds of metadata to be produced, distributed and presented by another channel, e.g the same channel that is used for registering metadata for netcdf-datasets and such.

So the issue is not just about describing the interface, but figuring out what such an interface should be.

niellaNina commented 2 years ago

Fjerner denne fra epic L5.4 ... Havner litt på siden av den og da kan den epicen lukkes