Stéphane Klein

Not a bug per se, more an annoying limitation. Resolution of relative URIs currently requires an absolute base url no matter what. However, if it cannot be avoided for most...

@edsiper thanks for the feedback! Aren't environment variables resolved at startup time only though? If that's the case, scheduling a re-start at offset changes would still be necessary.

Unless a $ref pointing to another document is encountered, we never leave the current schema, so it's expected to get always the same identifier (here the empty string) and the...

> The registerSchema behavior is wrong (relying on uniqueness of primary resource identifier even when it's empty string) I don't agree. The empty string is also a valid identifier. It's...

You're right, and actually even for #6, the schema should probably be taken from `$stack` and not `$schemas`, so we can safely exclude the empty string as you suggested.

Hi. Indeed, this is a 04-only lib for now. I'd like to catch up with the spec at some point, but by lack of time, it probably won't happen in...

@JanTvrdik, I think we must see this and the ideas in #6 and #11 as a whole and put a little more thought in it. AFAIK the issue isn't about...

Thanks for your work. On the positive side: - Conformance to RFC 6901 is a really good catch. The only missing part to make it complete now is the treatment...

I don't see anything in the spec to support that reasonning. Scopes have nothing to do with "declaration" of schemas, they're just a way to alter the URI against which...

I've noticed a problematic behaviour with a recursive, heavily nested schema I've been testing. I'd like to fix that before creating a tag. It should be done soon.