Jason Lewis

Sounds great except for this: > in some JSON document Specifying the server-side representation of a resource is the AntiREST, and I think we can do better. Perhaps - The...

@garemoko Yeah, I figured that, it's one of those editing things that I think needs to happen in a bunch of places :smile_cat:

Going back to the original issue: I think this can be addressed by changing one of the most egregious mistakes in the spec (from my perspective): > An Agent MUST...

@garemoko this is something that was recently adopted for the OBI 1.1 spec, I think I have some slides from one of those calls that explains how it works for...

@fugu13 @garemoko Here's Nate's presentation for using JSON-LD in OBI extensions, as promised: [Open Badges Standard Extension Proposal](https://docs.google.com/presentation/d/1dWMU2gdnfjBPRJTCcCDOJrs0xSgCwNc-IOUdjq9gRmw/edit?usp=sharing) I agree that JSON Schema can be overkill in some places, but...

@garemoko @andyjohnson I agree this should be patch/minor. I would suggest (for the patch version of this): - SHOULD use JSON-LD for Extensions - MAY include a JSON Schema URI...

@aaronesilvers The OWLs are not what they seem.  As far as the letter ordering... why is "Universal Coordinated Time" UTC? Just blame the French.

Leaving JSON-LD to the side (for the moment), what I'd really like to see come out of this is the ability for LRSs that parse extensions that declare a JSON-Schema...

This is the part I think needs to be altered: > An LRS MUST NOT reject a Statement based on the values of the extensions map. (From [4.1 Extensions](https://github.com/adlnet/xAPI-Spec/blob/1.0.3-Restructure/xAPI.md#41-extensions)) An...

@jhaag75 You're absolutely right - This should really be two issues, one for JSON-Schema validation and another for JSON-LD support. I'm going to edit to clarify that this issue is...