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)

@aisaac scripsit:
> It is about how to invoke a specific profile for a data resource. 

I still don't understand what "invoke a profile" means... Is it the same as "get content conforming to a profile"?

> This is DCAT-level (or in fact any resource that is described in RDF).

Yes, it's definitely not constrained to DCAT (and thus I don't think it's a DCAT requirement)

> It sounds like requiring a mixture of PROF (for describing profiles), DCAT (for linking a piece of data to a profile), and the methods in the Conneg doc that list profiles available for a specific negotiation option (Conneg or QSA). The issue is that how to represent the 'how to invoke' probably depends on the negotiation method.

I see the relation to PROF and to conneg, but not to DCAT in particular. _Any_ piece of data sent can conform to a profile, so we need a mechanism that doesn't depend on DCAT.

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

Received on Tuesday, 27 November 2018 13:08:45 UTC