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)

@larsgsvensson yes to me 'invoking a profile for a resource' means 'getting content conforming to that profile for the resource'.
And I'm using 'DCAT-level' as a generalization of what DCAT does, i.e. describing how datasets can be accessed. I fully agree that the requirement is wider than DCAT, but I don't see anything elsewhere that would provide such 'hooks' for the requirement. POWDER, maybe?
The issue is that as @RubenVerborgh says, Conneg somehow meets the requirement: it's clear what is offered and how to get it. But Conneg itself doesn't offer a 'machine-readable graph of metadata' that describes what is offered for a resource and how to get it, as this requirement seems to ask for.

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

Received on Thursday, 29 November 2018 07:50:55 UTC