Broken links to json-schema references
See original GitHub issueAll links like this:
http://json-schema.org/latest/json-schema-validation.html#anchor17
need to be updated, they have been moved in the target to this format:
http://json-schema.org/latest/json-schema-validation.html#rfc.section.5.2
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Link to schema broken when requestBody entity name is not ...
It seems that the request body item name ( PetRequest ) must match the schema name ( Pet ). The default petstore example...
Read more >JSON Hyper-Schema: A Vocabulary for Hypermedia ...
JSON Schema is a JSON-based format for describing JSON data using various vocabularies. This document specifies a vocabulary for annotating ...
Read more >JSON Hyper-Schema: Hypertext definitions for JSON Schema
JSON Schema is a JSON based format for defining the structure of JSON data. This document specifies hyperlink- and hypermedia-related keywords of JSON ......
Read more >A Vocabulary for Hypermedia Annotation of JSON
JSON Schema is a JSON based format for defining the structure of JSON data. This document specifies hyperlink- and hypermedia-related keywords ...
Read more >Structuring a complex schema — Understanding JSON ...
Like any other code, schemas are easier to maintain if they can be broken down into logical units that reference each other as...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Relequestual I may be able to be of some assistance. Want to email me and we can identify a time to chat about what might be needed? {firstname}{lastname}{at}microsoft{dot}com
As an aside, given how many people and now companies are involved in OAS, it would be great to see some experienced individuals come and help with JSON Schema. Realistically there are 3 or 4 of us doing the work, none with experience of publishing IETF documents or defining internet standards… If OAS is going to be the future of APIs, and a huge core of that is JSON Schema, then the changes we make ought to be the right ones… - Any way this comment can be disseminated to those with experience?