New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"profile" attribute for link set media types #9
Comments
for context: this issue would add a profile media type parameter as defined here: https://datatracker.ietf.org/doc/html/rfc6906#section-3.1 |
hvdsomp
added a commit
that referenced
this issue
Jun 1, 2021
In order to address #9 , added a section describing the use of the "profile" attribute and added the optional "profile" attribute in the IANA Considerations for the media types.
I made changes to the I-D to describe the use of the "profile" attribute for the link set media types. |
On 2021-06-01 12:26, Herbert Van de Sompel wrote:
I made changes to the I-D
<174a529#diff-78ac3483eb070a5e13b365b9e882859464ff08edc202a7fff9a144388cd78c69>
to describe the use of the "profile" attribute for the link set media types.
that looks great, thanks. as one minor tweak i'd rather say that profile
URIs "MAY" be registered, and not "SHOULD" be. the registry has seen
pretty much no usage so far, and while i think it's great to mention it,
it's perfectly ok to use profile URIs without registering them.
|
Agreed. I made the change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be useful to define a "profile" attribute for both media types defined in the I-D. Profiles could, for example, be used to express a constraint on the link relation types that are used in a link set. As a concrete example, TimeMaps from the Memento protocol (RFC7089) could be expressed as link sets. A profile attribute would allow indicating to clients that a particular link set is actually a Memento TimeMap.
The text was updated successfully, but these errors were encountered: