Metadata about server profile support can be used for discovery and mediated traversal via content negotiation. [ID5] (5.5)

[nicholascar]

Entered from Google Doc

[rob-metalinkage]

The mechanisms for describing available profiles for a given resource should provide the tokens needed to perform content negotiation (i.e. metadata and protocol-level mechanisms should use the same identifiers)

[aisaac]

Just a note: as of today, our Google doc for group discussion still lists this requirement as undecided

[kcoyle]

The resolutions from the f2f in Lyon do not include this one. This was an action on @rob-metalinkage, which was closed but which I moved to pending review because I couldn't find evidence that it had been done. Perhaps he can clarify here? We seem to have lost the follow-up, unfortunately.

[rob-metalinkage]

This is inherent in the profiles negotiation approach - after reintroducing duplicates into the discussion we first need to check this isnt covered in a new rewording of the same requirement. If the answer for that is no then we need to accept this, as profneg makes no sense without it.

[rob-metalinkage]

discussed in CNEG group - https://w3c.github.io/dxwg/ucr/#RPFMD covers this issue - noting its not explicit about mechanism (server or catalog source of metadata)