Hyperschema

[gregsdennis]

Describe the functionality that isn't covered by this suite
Hyperschema should be implemented.

[gregsdennis]

URI templates are required by this specification. The previous .Net implementation is .Net Framework and hasn't been ported yet (not even into .Net 5). I looked at just pulling the class into the library, but it appears that it's not just a simple copy/paste of the class definition.

I'll either need to wait for MS to port it, or see if I can find one. I'm not sure I understand enough about the domain to implement it myself.

[gregsdennis]

Looks like someone did the direct port! Well, several people did, but this is the one I'm using.

[gregsdennis]

From the spec, section 6.4.1 on template pointers

The value of the "templatePointers" link description property MUST be an object. Each property value in the object MUST be a valid JSON Pointer [RFC6901], or a valid Relative JSON Pointer...

I can't evaluate relative pointers because of a limitation in the JSON element structure. I won't be able to support evaluating schemas with these for now.

[gregsdennis]

It sounds like this is more for code gen than validation, like generation of API clients. Visual Studio can do this for an API that publishes a swagger file. You point the tool at the API, and it generates all of the models and a client.

Is there any validation expected here? Even the spec doesn't really talk about "an instance is valid against this keyword if x criteria are met." I'm struggling to figure out what a validator would do with this.

I'm leaning on the Slack community to answer this.

[gregsdennis]

Confirmed in the JSON Schema Slack that this isn't a validation vocabulary. It's for tooling support.

I'm not sure that's something I want to support. At least not right now. Closing this.