Expand analysis of "Custom Registry Mechanism Registries" #1150
Conversation
JKRhb
force-pushed
the
extend-custom-registry-analysis
branch
from
7b0c65f
to
811fd27
Compare
|
The PR should now be ready for review :) Let me know if something is unclear or missing. |
|
Call of 15.11:
Our primary goal is to write a section where we document the mechanisms we want to adopt from other registries and maybe also what we should not do. |
registry-analysis/Readme.md
Outdated
|
|
||
| - Each entry consists of MIME type/subtype which is mapped to a publicly available specification for a byte stream format. Furthermore, it has to be specified if a flag for generating timestamps needs to be set with the byte stream format. | ||
| - It is recommended that the specification should be available without fees. | ||
| - All requirements mentioned in the [Media Source Extensions](https://www.w3.org/TR/media-source/#byte-stream-formats) specification must be fulfilled. |
There was a problem hiding this comment.
This is a good point for us, meaning we can specify the requirements of bindings in general in one place and registry requirements point to that.
|
|
||
| The registry, its entries and the modification process are specified as follows: | ||
|
|
||
| - Entries are given out on a "first come, first serve" basis |
There was a problem hiding this comment.
This is interesting for us and did not see this in other mechanisms. This can help with the case that two people try to register two entries (one each) for a certain protocol. E.g. what do we do if another person says "I don't like the CoAP Binding Template, here is mine which has other design decisions and thus not a direct improvement of the existing document"
Co-authored-by: Ege Korkan <egekorkan@gmail.com>
|
In the latest commits, I tried to separate the bullet points into the categories "Entry Format", "Submission Process", and "Modification Process", hope that addresses the discussion we had at last week's meeting :) |
|
@JKRhb will fill in the status and creation information. We will merge it asynchronously after those additions. |
Co-authored-by: danielpeintner <daniel.peintner@gmail.com>
|
Status and creation date are added, merging |
Will resolve #1144 -- currently still WIP.