Specify some normalization rules for URIs #147
Closed
Conversation
This file contains 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
justmoon
requested changes
Jan 22, 2017
| @@ -1211,7 +1211,9 @@ <h1 id="rfc.section.9.2.1"><a href="#rfc.section.9.2.1">9.2.1.</a> <a href="#par | |||
| <h1 id="rfc.section.9.2.2"><a href="#rfc.section.9.2.2">9.2.2.</a> <a href="#parameter-cost-cost" id="parameter-cost-cost">Parameter: Cost (cost)</a></h1> | |||
| <p id="rfc.section.9.2.2.p.1">The cost parameter is the cost of the condition that is represented by the URI.</p> | |||
| <h1 id="rfc.section.9.2.3"><a href="#rfc.section.9.2.3">9.2.3.</a> <a href="#parameter-subtypes-subtypes" id="parameter-subtypes-subtypes">Parameter: Subtypes (subtypes)</a></h1> | |||
| <p id="rfc.section.9.2.3.p.1">The subtypes parameter indicates the types of conditions that are subtypes of the condition represented by the URI. The value MUST be a comma seperated list of names from the <a href="#crypto-conditions-type-registry">Crypto-Condition Type Registry</a> <cite title="NONE">[crypto-conditions-type-registry]</cite> and SHOULD not include the type of the root crypto-condition. i.e. The value of the fpt paramtere should not appear in the list of types provided as the value of the subtypes parameter.</p> | |||
| <p id="rfc.section.9.2.3.p.1">The subtypes parameter indicates the types of conditions that are subtypes of the condition represented by the URI. The value MUST be a comma seperated list of names from the <a href="#crypto-conditions-type-registry">Crypto-Condition Type Registry</a> <cite title="NONE">[crypto-conditions-type-registry]</cite>.</p> | |||
| @@ -457,7 +457,7 @@ | |||
|
|
|||
| <meta name="dct.creator" content="Thomas, S., Reginelli, R., and A. Hope-Bailie" /> | |||
| <meta name="dct.identifier" content="urn:ietf:id:draft-thomas-crypto-conditions-02" /> | |||
There was a problem hiding this comment.
This is going to be draft-03 now, right?
There was a problem hiding this comment.
Correct! I actually think we should move this whole spec to it's own repo to allow it to be tagged before merging any more changes.
See #148
adrianhopebailie
added a commit
to rfcs/crypto-conditions
that referenced
this pull request
Mar 14, 2017
Migrate PRs from: interledger/rfcs#147 interledger/rfcs#157
adrianhopebailie
added a commit
to rfcs/crypto-conditions
that referenced
this pull request
Mar 14, 2017
Migrate PRs from: interledger/rfcs#147 interledger/rfcs#157
|
Migrated to rfcs/crypto-conditions |
adrianhopebailie
added a commit
to rfcs/crypto-conditions
that referenced
this pull request
Jul 13, 2017
Migrate PRs from: interledger/rfcs#147 interledger/rfcs#157
adrianhopebailie
added a commit
to rfcs/crypto-conditions
that referenced
this pull request
Jul 13, 2017
Migrate PRs from: interledger/rfcs#147 interledger/rfcs#157 * Update draft number * Make commas reserved characters in URI
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.
No description provided.