Denis Laxalde

@A1exKH, conflicts resolved and rebased. (Note that the first commit is also in #440.)

Yes I could. However, I'm not sure what the proper way to fix this. Sure your suggestion would work, but since this appears to be broken in other extensions as...

@vcharpenay Couldn't you keep JSON-LD declarations distinct from JSON Schema ones by relying on the JSON-LD context being referenced in an HTTP Link header (see https://www.w3.org/TR/json-ld/#interpreting-json-as-json-ld)? ``` GET http://example.org/imu/1 HTTP/1.1...

> The Web of Things includes other protocols than HTTP like CoAP or WebSocket. CoAP does not specify a "Link" Option (although one could define in a non-standard way) and...

Re-reading comments, it seems to me that we have been discussing around the idea of including semantic tagging *in JSON Schema documents* but I actually think this would better suited...

> @sebastiankb I think your view and @dlax's can be aligned by considering the Thing Description as both a JSON Schema document and an instance document @handrews I've been thinking...

@vcharpenay Here's another proposal to convey semantics in JSON Schema by making use of Hyper-Schema links: ```json { "type": "object", "properties": { "prop1": { "type": "array", "items": { "type": "number"...

> @dlax I've tried to sell the WoT folks on JSON Hyper-Schema, but so far they aren't biting :-) Hm, okay, didn't know that... On the other hand, from https://w3c.github.io/wot-thing-description/#interaction-patterns,...

@Anthropic > mapping enum values to readable titles Isn't it something that got solved in draft-6 with `const` keyword to be used with `oneOf` (see https://github.com/json-schema-org/json-schema-spec/issues/57#issuecomment-247861695)?

@Anthropic Thanks for clarification! Clearly, I missed the intent but it now makes sense to me.