[dxwg] Question on IETF definition of Profile (#1002)

aisaac has just created a new issue for https://github.com/w3c/dxwg:

== Question on IETF definition of Profile ==
This is especially for @RubenVerborgh but I'm eager to hear from others.
In https://github.com/w3c/dxwg/issues/963 
the new proposed definition for IETF profiles is:

> a profile is a description of structural and/or semantic constraints documents can conform to in addition to the syntactical interpretation provided by more generic MIME types.

And now as per [this commit](https://github.com/ProfileNegotiation/I-D-Profile-Negotiation/commit/33818075f0544193ecc9af68ea403d1813f2d37a) it is

> a profile is a description of structural and/or semantic constraints documents can conform to structural and/or semantic constraints on representations of documents in addition to the syntactical interpretation provided by more generic MIME types.

@smrgeoinfo suggested that 

> this IETF definition is that it defines 'profile' to only apply to profiles of MIME types-- certainly a narrower scope that our discussions here.

@RubenVerborgh refuted that, and I note that indeed the last bit of the definition seeks to clarify that profiles are not MIME type focused. 

However I am really struggling with the first part of the definition, which mentions "representations of documents" and "structural constraints". Does this part include or exclude the JSON-LD profiles that are different from our profiles, as we're trying to establish [here](https://github.com/w3c/dxwg/issues/976)? Can you give examples of "structural contraints that wouldn't be semantic constraints nor syntactical constraint? Maybe a reference to a definition for "structural" would help here.


Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1002 using your GitHub account

Received on Tuesday, 16 July 2019 19:14:09 UTC