Skip to content

Conversation

SergeyKanzhelev
Copy link
Member

@SergeyKanzhelev SergeyKanzhelev commented Feb 8, 2019

#247

and added link to CloudEvents extension.

This change will add the note "non-normative" to the spec. Supposedly it means that we will be able to keep updating it without the whole document versioning.

image


Preview | Diff

@danielkhan danielkhan changed the title Mark section non-informative Mark section non-normative Feb 12, 2019
@plehegar
Copy link
Member

See #247 for an alternative approach.

@SergeyKanzhelev SergeyKanzhelev changed the title Mark section non-normative Mark section non-normative and simply point to the registry Feb 15, 2019
@plehegar
Copy link
Member

Thinking about this further, is there now a reason not to make the link to the registry normative? Surely, we want to encourage implementation to follow what is in the registry rather than coming up with their own mapping. Imho, we should make the registry to document normative, and let it deal with the question on whether a particular mapping is normative or not. That's an other added bonus of haivng this indirection.

@SergeyKanzhelev
Copy link
Member Author

@plehegar makes sense. Changed

@SergeyKanzhelev SergeyKanzhelev changed the title Mark section non-normative and simply point to the registry Mark other protocols section point to the registry Feb 15, 2019
@AloisReitbauer
Copy link
Contributor

@plehegar please approve if this is fine for you.

@SergeyKanzhelev SergeyKanzhelev merged commit 5688d72 into master Feb 19, 2019
@SergeyKanzhelev SergeyKanzhelev deleted the sergkanz/makeOtherProtocolsSectionNonInformative branch February 19, 2019 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants