adding profile media type parameter #92
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
the proposal is to add a profile media type parameter to both media types. it would allow profiles to be identified at the media type level. profiles according to RFC 6906 could be used to signal certain vocabularies that an activity stream may use (or that a client prefers). https://github.com/dret/ASDL is one way how such a profile could be represented (currently ASDL is focusing on AS1), but the profile parameter would not require a specific representation, or any at all. it would simply signify that an activity stream follows a profile.
|
RFC 6906 profiles can be used with |
|
if we add this, then maybe we can also add some recommendation or suggestion for people to expose extension vocabulary usage this way. i'd be happy to suggest something if there is interest. |
jasnell
added a commit
that referenced
this pull request
Apr 14, 2015
adding profile media type parameter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
the proposal is to add a profile media type parameter to both media types. it would allow profiles to be identified at the media type level. profiles according to RFC 6906 could be used to signal certain vocabularies that an activity stream may use (or that a client prefers). https://github.com/dret/ASDL is one way how such a profile could be represented (currently ASDL is focusing on AS1), but the profile parameter would not require a specific representation, or any at all. it would simply signify that an activity stream follows a profile.