Re: [dxwg] There should be a way to look up additional information about a profile - this may be machine readable for run-time mediation or used to develop or configure a client [ID2] (5.2) (#286)

So the idea is as follows.

A profile has a certain identifier, let's say MyAppProfile.
Some clients will already be preprogrammed for MyAppProfile. So if they see MyAppProfile, they will know what to expect.

Other clients will not know about MyAppProfile.
So they need learn more about MyAppProfile. For instance, it might be that MyAppProfile is actually compatible with MyOtherProfile, which might help them. Or they might find a document clarifying the structure of MyAppProfile, which might also help them.

This requirement says that we need to add a mechanism for a client to go from MyAppProfile to "more information" about MyAppProfile.

It was worded this way because I do _not_ think DXWG should specify the structure or definition of that "more information", only the mechanism to look it up.

-----


The above might still be very abstract, but that's because I wrote it as a problem, not as a solution. When phrased as a solution, thing will likely become much clearer.

A possible solution is:
- profile identifiers are HTTP URLs
- the HTTP URLs need to be dereferenceable
  - i.e., when you perform a `GET` on the profile URL, you receive more information about the profile
- DXWG does not specify the format of the returned document
  - only that such a document can be retrieved by this mechanism

-- 
GitHub Notification of comment by RubenVerborgh
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/286#issuecomment-441652800 using your GitHub account

Received on Monday, 26 November 2018 14:15:11 UTC