- From: Stephen Richard via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Jan 2019 17:25:04 +0000
- To: public-dxwg-wg@w3.org
This approach makes good sense to me; a profile is just a particular kind of specification (has some relationship to one or more base specifications). The ResourceDescriptor class could be modeled as a qualifiedAssociation to related resources, and any specification could/should have an array of related resources for guidance, validation, examples etc. The important thing for the content negotiation is the ability to identify a specification that the target representation conforms to, such that machine agents can identify and retrieve representations they can work with. -- GitHub Notification of comment by smrgeoinfo Please view or discuss this issue at https://github.com/w3c/dxwg/issues/716#issuecomment-459032300 using your GitHub account
Received on Wednesday, 30 January 2019 17:25:06 UTC