Page 1 of 1

Using dummy URLs for the schema: value

Posted: Thu Feb 06, 2025 3:59 am
by jsaiya
In my organization, the schemas for our JSON content are not made available on an HTTP(S) host. The value we use for the `schema` property inside the JSON file is a dummy URL.

I use the "Validate with..." feature to set a schema file on my local drive, but Oxygen still tries to access a schema file at that URL.

Is there a way to configure Oxygen so that I can direct it to ignore the values of the `schema` properties?

Re: Using dummy URLs for the schema: value

Posted: Thu Feb 06, 2025 10:09 am
by tavy
Hello,

If a reference to a remote JSON schema must be used, but a local copy of the schema should be preferred for performance reasons, the reference can be resolved to the local copy using an XML Catalog. You can find more about this in our user manual:
[Read more](https://www.oxygenxml.com/doc/versions/ ... talog.html)

To add a new catalog, you can define a document type for your documents. To do this, go to Options -> Preferences -> Document Type Association, and create a document type association similar to the sample ones like Personal (Sample-JSON).
[Learn more](https://www.oxygenxml.com/doc/versions/ ... ialog.html)

Then, add a catalog to resolve the location of the schema.
[Find out how](https://www.oxygenxml.com/doc/versions/ ... s-tab.html)

You can also add a new rule in the application catalog, located in "[Oxygen installation folder]\frameworks\catalog.xml".

I have also raised an issue to allow adding a custom catalog in the Oxygen JSON Editor. This option is available in the Oxygen XML Editor and Developer but seems to be filtered in the Oxygen JSON Editor.
[See more details](https://www.oxygenxml.com/doc/versions/ ... talog.html)

Best Regards,
Octavian