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)

tl;dr: IMHO this requirement is not in scope for conneg-by-ap.

The UC for this requirement is [Discover available content profiles](https://w3c.github.io/dxwg/ucr/#ID5). Having built up the motivation for the feature, the UC goes on to say:

> Thus there is a need for discovering which profiles a service will offer for a given resource, and a canonical machine readable graph of metadata about what such offerings consist of and how they may be invoked. This may be as simple as providing a profile name, or content profile, schema choice, encoding and languages.

Discoverability and invocation of profiles is handled by the abstract methods [list profiles](https://w3c.github.io/dxwg/conneg-by-ap/#listprofiles) and [get resource by profile](https://w3c.github.io/dxwg/conneg-by-ap/#getresourcebyprofile), so we're fine there.

In the context of profile negotiation, the relevant part is "Thus there is a need for discovering which profiles a service will offer for a given resource [...] and how they may be invoked. This may be as simple as providing a profile name, or content profile, schema choice, encoding and languages." I. e. the part about the machine-readable graph is not in part of the scope for profile negotiation.

This comment is part of ACTION-240

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

Received on Tuesday, 30 October 2018 08:33:45 UTC