Jason Desrosiers

Ah, I just looked at the mentioned sKema issue and it seems to corroborate my suspicion. They have a workaround to specifically handle `urn:`. I'm guessing that workaround is because...

I started a tread on Slack to try to get some more opinions on how to handle this case. https://json-schema.slack.com/archives/C8CQ81GKF/p1764527326577729

Based on the feedback we got here and in the slack thread, I think we want to include tests for `urn:`, `tag:`, and something arbitrary (like `foo:`). The arbitrary scheme...

Thanks for your feedback! > 1. From my understanding it is preferable to use relative paths rather than absolute URIs (file://...)? Is this correct and if so, why? In my...

> As I said, in my case the path/URI is not included in any committed code. I only use it to load the schema with `getSchema` so I can easier...

I think detecting absolute paths and throwing an error is the way to go. Let me know if you want to make the PR, otherwise I'll get to it soon....

Thanks for your feedback. Different people can have different ideas about what's essential, so it's valuable to hear different perspectives. Some of these things I'm aware of and some I'm...

Thanks for the offer. I have been working on this, but my attention keeps getting pulled to other things. I'll create a discussion with my vision for 2.0 and what...

@hysmio https://github.com/hyperjump-io/json-schema/discussions/80

@michaelfaith Thanks for sharing your perspective. I'm sure there are exceptions. In those cases, you can always make a temporary identifier like I demonstrated in the comment you're quoting from....