References from draft-vasters-json-structure-sem-ann
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| draft-vasters-json-structure-alternate-names |
JSON Structure: Alternate Names and Descriptions
References Referenced by |
informatively references | ||
| draft-vasters-json-structure-core |
JSON Structure: Core
References Referenced by |
normatively references | ||
| draft-vasters-json-structure-import |
JSON Structure: Import
References Referenced by |
informatively references | ||
| draft-vasters-json-structure-relations |
JSON Structure: Relations
References Referenced by |
informatively references | ||
| draft-vasters-json-structure-units |
JSON Structure: Symbols, Scientific Units, and Currencies
References Referenced by |
normatively references | ||
| draft-vasters-json-structure-validation |
JSON Structure: Validation Extensions
References Referenced by |
normatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3339 |
Date and Time on the Internet: Timestamps
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8792 |
Handling Long Lines in Content of Internet-Drafts and RFCs
References Referenced by |
Informational | informatively references |