Skip to main content

References from draft-luff-json-hyper-schema

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.

Reference type help

Document Title Status Type Downref
BCP 14
References Referenced by
normatively references
BCP 26
References Referenced by
informatively references
draft-ietf-appsawg-json-pointer JavaScript Object Notation (JSON) Pointer
References Referenced by
Proposed Standard normatively references
draft-zyp-json-schema JSON Schema: core definitions and terminology
References Referenced by
normatively references
RFC 2045 Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
References Referenced by
Draft Standard normatively references
RFC 2046 Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
References Referenced by
Draft Standard informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 2161 A MIME Body Part for ODA
References Referenced by
Experimental Possible Reference
RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by
Draft Standard informatively references
RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard normatively references
RFC 4287 The Atom Syndication Format
References Referenced by
Proposed Standard normatively references
RFC 5226 Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by
Best Current Practice informatively references
RFC 5988 Web Linking
References Referenced by
Proposed Standard informatively references
RFC 6570 URI Template
References Referenced by
Proposed Standard normatively references
STD 66
References Referenced by
normatively references