8000 Close #91: Mention stand-in items by cabo · Pull Request #98 · core-wg/href · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Close #91: Mention stand-in items #98

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

Merged
merged 1 commit into from
Feb 3, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Split
Diff view
11 changes: 11 additions & 0 deletions draft-ietf-core-href.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,7 @@ normative:
STD94: cbor
# RFC8949
RFC9165: cddlcontrol
I-D.ietf-cbor-packed: packed

--- abstract

Expand Down Expand Up @@ -468,6 +469,16 @@ references:
as per {{ingest}} equivalent to `[0]`, which essentially copies the
base CRI).

Application specifications that use CRIs may explicitly enable the use
of "stand-in" items (tags or simple values), i.e., items used in place
of original representation items such as strings or arrays, where the
tag or simple value is defined to evaluate to the original item that
it is standing in place of.
Examples would be tags such as 21 to 23 ({{Section 3.4.5.2 of
RFC8949@-cbor}}), which might be used to represent text string
components by employing more compact byte strings, or reference tags and
simple values as defined in {{-packed}}.

For interchange as separate encoded data items, CRIs MUST NOT use
indefinite length encoding (see
{{Section 3.2 of RFC8949@-cbor}}); this requirement is relaxed for
Expand Down
Loading
0