-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add some examples based on STP #20
base: main
Are you sure you want to change the base?
Conversation
Next step for me: Develop into form that can be PR'd into STP |
[2, 6(23 / container:item /), cri'./11'], | ||
[2, 6(23 / container:item /), cri'./12'], | ||
[2, 6(23 / container:item /), cri'./13'], | ||
[2, 6(42 / stp:next /), cri'stp-collection-after8.cbord'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[2, 6(42 / stp:next /), cri'stp-collection-after8.cbord'] |
[2, 6(10 / core:obs /), true], | ||
[2, 6(42 / stp:next /), cri'stp-index-1.cbord'], | ||
/ Alternatively to an embedded representation, multipart would just be another option / | ||
[2, 6(0 / coral:current-representation), 6.1668546672( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[2, 6(0 / coral:current-representation), 6.1668546672( | |
[2, 6(0 / coral:current-representation /), 1668546672( |
From meeting: Don't imply sending cbord around, just add Makefile builder and refer to built files |
This is rough and could be done in many different ways, but it shows some terms needed from STP (given that HTML's rel:next is probably too fuzzy), and also describes a form (using the as-links representation that the binary format has a more efficient version of, but I don't know that well enough).
Note that a very schema-driven, non-HATEOS, hard-paginating spec could prescibe that some resource follow the
[2, 6(56 / stp:all-are-of-this-form /), "stp-index-{linear}.cbord"]]
template. Such clients would ignore the additional semantic information and go right for the file names, while the serves could still provide that (and the other) information to be accessible to non-schema-aware consumers.