- From: Lars G. Svensson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 May 2018 14:51:28 +0000
- To: public-dxwg-wg@w3.org
My intention always was that the requirements are that "a profile MUST have a URI" and that "the URI identifying the profile SHOULD be an http URI so that you can look up more information about it". I see no reason that there can be (at least) two kind of profile-aware servers 1. Those that are hard-coded to work with a specific (set of) profile(s) and 2. Those that can actually look up a profile, evaluate the constraints and then see if it can tweak the data in order to match the requirements set in the profile. This would be similar to schema-aware XML-processors that can also be hard-coded ("specialized to one or a fixed set of pre-determined schemas") or general-purpose ("those not specialized to one or a fixed set of pre-determined schemas"); cf. [XML-Schema 1.1 ยง4.3.2](https://www.w3.org/TR/xmlschema11-1/#schema-loc). I guess that profile-aware servers will be of the first kind, at least in the beginning. -- GitHub Notification of comment by larsgsvensson Please view or discuss this issue at https://github.com/w3c/dxwg/issues/214#issuecomment-393192559 using your GitHub account
Received on Wednesday, 30 May 2018 14:51:35 UTC