[dxwg] A client should be able to determine which profiles are supported by a server, and with which content types or other properties, in order to receive the one most appropriate for their use.
[dxwg] A client should be able to discover which profiles are supported by a server, and with which content types or other properties, in order to receive the representation most appropriate for their use.
[dxwg] Invocation of a profile may be by profile name, a schema choice, an encoding, and/or a language. (schema? And assume that encoding is type as in type="application/xml".) [ID5] (5.5)
[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)
[dxwg] Requirement: A short token to specify a profile may be used as long as there is a discoverable mapping from it to the profile's identifying URI [ID5] (5.5)
[dxwg] There needs to be metadata about the views provided by profiles (“named collections of properties”) that can included in a http header [ID5] (5.5)
dxwg-ACTION-246: Coordinate querying european open data portal to estimate current class and property useage to use in assessing confirmation of implementation
dxwg-ACTION-247: Work with danbri on making sure that the dcat (=rdfa here) example in https://developers.google.com/search/docs/data-types/dataset a) works and b) is similarly exprssive to the schema.org and c) is up to date w.r.t. this wg's current efforts.
dxwg-ACTION-250: Add a note to the profiles guidance doc to indicate the motivation to have desrciptions of profiles is to help clients find out what is available