- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Fri, 25 May 2018 20:41:49 +0000
- To: public-dxwg-wg@w3.org
@agreiner said: > So the only thing required for a profile would be a URI? I tend to agree that the URI is only mandatory requirement for a profile. For the rest (profile metadata and (in)formal definitions of a profile), these are very much related to the specific use scenarios. The SHOULD can be considered as "recommended", but possibly also as "conditional" (i.e., "mandatory" if the requirements of a use scenario need it). E.g., in a scenario where profiles need to be published and made discoverable (in a specific registry, catalogue or Web site), a subset of profile metadata may be considered as mandatory. Likewise, profile definitions/representations may be mandatory when a use scenario require, e.g., support for validation. In any case, it would be important to explain in the guidance document "why" we may need profile metadata and profile definitions/representations. -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/issues/242#issuecomment-392179122 using your GitHub account
Received on Friday, 25 May 2018 20:41:52 UTC