Ben Hutton

I'm actually not sure you CAN change the `$id` value in this situation. You may have references in the root schema resource which are relative URIs. If you're changing the...

> ... > > The bundled schema needs a new `$id`. > > > I'm actually not sure you CAN change the `$id` value in this situation. You may have...

Given @gregsdennis interpretation is reasonable, and the solution (as in, Greg's approach to bundling schemas) is reasonable and conformant to the spec, let's make the tests follow this approach? Sound...

> We need a solution that isn't implementation specific. I agree. I thought Greg's solution was implementation idependant. In that, we just needed to confirm that implementations were able to...

THe intent was for an implementation to be able to, at will, choose to bundle (maybe using third party tools) a schema for processing, transparantly to the end user. Mostly...

> > A Bundled Schema Resource MUST NOT be bundled by replacing the schema object from which it was referenced, or by wrapping the Schema Resource in other applicator keywords....

> The other problem is that although an output format includes annotations, output format tests are not directly testing for annotation behaviors, which means it's not helpful for the kind...

I originally presumed we would have some sort of human readable ID. UUIDs would be simpler in some respects. I guess it depends on the intended use case. If someone...

I think this is one of those situations where the spec defines what IS based on what is supported, but doesn't define outside of the scope of what's defined. That...

Any individual ones in the history are invalid, should be skipped. I've seen this a lot recently where the OADs were comitted in a broken state. It would be good...