SELFIE resource model VS connegP list Profiles

[sgrellet]

Looking at this : https://conneg.info/mediatypes-service/connegp, we can read

1.1 list profiles
The preferred way to retrieve a list of profiles the server supports for a specific resource is to issue a GET or HEAD request for that resource. In either case, a server implementing content negotiation by profile SHOULD return an HTTP Link header containing information about the default representation of that resource and information about any alternate representations of that resource conforming to other profiles. The returned representation will be identified by rel="self", other representations by rel="alternate".

For a request for any Media Type, e.g. Notation-3 https://w3id.org/mediatype/text/n3, a Link header with the following information is returned:

<https://w3id.org/mediatype/text/n3?_view=mt>; rel="self"; type="text/html"; profile="https://w3id.org/profile/mediatype",
<https://w3id.org/mediatype/text/n3?_view=mt>; rel="alternate"; type="text/turtle"; profile="https://w3id.org/profile/mediatype",

etc...

Isn't that information provided close to be a 'flattened' view of the matrix we have in SELFIE resource model subjectOf part ?
'Close to be' as

• connegP 'type' seems to map to SELFIE choice of 'format'
• connegP 'profile' seems to map to SELFIE choice of 'conformsTo'
• but there is no "primaryTopic" and no "provider" as far as I can see

Where to go from this is open

[dblodgett-usgs]

@sgrellet -- I think this is something we could alude to in a future work section of the ER. I linked to this issue in the ER outlet. Want to draft a paragraph or two to go there?