Re: [dxwg] Profiles offered by a service must be discoverable through a machine-readable graph of metadata that describes what is offered and how to invoke the offered profiles. [ID5] (5.5) (#288)

+1 for clarifying 'offered by a service'. But I think it's still important to keep the notion of 'data offer' and less as a constraint for the representation).
Maybe "For a given resource, a data service must enable the discovery of the profiles for which a data consumer can access conformant representations of that resource. This must happen through machine-readable metadata that describes what is offered and how to invoke the offered profiles".

I would not add references to canonical representation and PROV. This is going toward the side of solution space, considering the original case. Even the canonical representation was not even there. It's rather a good design principle that we are going to adopt in our response to the requirement. 
(and I think it's completely fair that a requirement brought by a specific use case wouldn't necessarily incorporate all the best practices that are relevant for it)

-- 
GitHub Notification of comment by aisaac
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/288#issuecomment-443938416 using your GitHub account

Received on Tuesday, 4 December 2018 01:46:09 UTC