Hi Carlos, We plan to introduce the AsyncAPI version 3.x support in a future release of Oxygen Editor. Meanwhile, you can configure a custom validation scenario using the using the AsyncAPI 3.0 schema available in the official specification repository. This allows you to benefit from validation and ...

Hi Scott, Regarding your question about plugging a JSON Schema validator into Oxygen, the short answer is yes. We even recently added an external validator called json-sKema (https://github.com/erosb/json-sKema), which is available as an add-on starting with Oxygen version 26.0. However, plugging a ...

Hello, Oxygen does not support $anchor references. Instead, references can be resolved in JSON Schema Design Page if you add a $id value (URI fragment) to your local resource. So, all you have to do in order to have a working example is to go to common.jschema file and replace "$anchor": &...

Hello,

I am not sure why this doesn't work. At the moment, no other idea comes to my mind, but you may want to take a look at this topic, which is related to PHP statements used in XSLT: common-problems/topic6588.html

Regards,
Florin

Hello, One solution to ensure that the closing parenthesis in the PHP statement is not converted to "&gt;" could be to use a CDATA (Character Data) section in your XSLT template. By wrapping the PHP statement with <![CDATA[ ... ]]>, you prevent the XML parser from interpreting the cont...

Hello, Thank you very much for the feedback. We use a third-party library for XSD to JSON Schema called jsonix and, unfortunately, it ignores the documentation elements when converting. This is mentioned as a limitation on our user-guide . You may also want to check our OpenAPI editor and tools: htt...

Hello, Thank you for the feedback. Most likely, your XSD file contains a large enumeration that exceeds the default limit of 256 elements. You can use the customization attribute typesafeEnumMaxMembers to extend this limit. For example, if you want to extend it to 1000, you need to add inside the XS...

Hi Rob, Thank you very much for the feedback. We use a third-party library for the XSD to JSON Schema and, unfortunately, it doesn't support the round-trip conversion. Therefore, we need another tool for JSON Schema to XSD conversion, but it's certainly not an easy job. I created an internal issue b...

Hi Michael, I have analyzed the reported problem a little more, and it turned out that the "anyOf" wrapping is not necessary in this scenario, as you pointed out. Feel free to download and install the latest version of the XSD to JSON Schema add-on (25.0.1), that no longer makes this wrapp...

Hi Michael, Thank you very much for the feedback. If you don't select the Preserve case of names from the XSD option, the default JAXB naming algorithm will be applied when converting. For example, "some.nAMe" is changed to "SomeNAMe", and "Some_oth3r_name" is changed t...

Hi Carlos,

Actually, we have just started the development of this feature, for JSON schemas. Most likely, it will be available in the 25.1 version of Oxygen XML Editor, that is scheduled for release in March. I'll let you know when it's done.

Regards,
Florin

Hi Michael, Thanks for your feedback. You could try disabling the option "Preserve case of names from the XSD" within the dialog, which is checked by default. If unchecked, the resulting JSON Schema will not hold the same naming format as the XSD, and it should use a lowerCamelCase naming ...

Hi Michael, First of all, if you need JSON Schema Draft 2020-12 for defining your endpoints, I think the best solution is to migrate from OpenAPI 3.0 to 3.1.0. You can check this post for more details: https://www.openapis.org/blog/2021/02/16/migrating-from-openapi-3-0-to-3-1-0. On the other hand, I...

Hi Michael,

Just wanted to let you know that version 25.0.0 of the XSD to JSON Schema add-on has just been released, and the conversion to Draft 2020-12 is now available. Make sure you are using Oxygen XML Editor 25.

Regards,
Florin

Hi Michael, I forgot to mention that the conversion to Draft 2020-12 is available starting with the version 25.0.0 of the add-on, only for Oxygen XML Editor 25. This release of the XSD to JSON Schema add-on is scheduled for the next week. I will send you a notification when it is ready to install. R...

Hi Michael, OpenAPI 3.0 uses an extended subset of JSON Schema Specification, meaning that some keywords are supported and some are not, or they have slightly different usage than in JSON Schema. The XSD to JSON Schema tool will generate a JSON Schema file that is one of Draft 4, 6, 7, Draft 2019-09...

Hi Michael,

Just wanted to let you know that version 25 of Oxygen XML Editor has just been released, as well as version 24.1.1 of XSD to JSON Schema add-on. This includes the improvement that you requested.

Best regards,
Florin

Hi Michael, Thank you very much for the feedback. Indeed, wrapping enums into "allOf" seems kind of redundant, so I adjusted the XSD to JSON Schema converter tool a little. Your example would now look like this: "IncomeModeCode": { "type": "string", "enum...

Hi again Bob, Thank you very much for the suggestion. The Badgerfish convention seems to be a very comprehensive way of converting XML to JSON, as it uses some mappings for XML attributes and namespaces. This adds a bit of overhead to the JSON syntax, but, of course, there has to be a trade-off. May...

Hi Bob, Thank you for the detailed feedback. The XML to JSON conversion tool does not differentiate between XML attributes (including namespaces) and XML elements, so both of them are converted to JSON properties. When converting back to XML, all the JSON properties become XML elements, so the round...

Hello, Thank you for your report. We are aware of this issue, and it has already been fixed in the current development stream. The fix will be available in the next maintenance build, scheduled for the near future. At the moment, there is no option to control the described behavior. If you don't wan...

Hi Jamil,

I'm coming back to you with some good news. We added an option to control the desired output when converting XML to JSON, as you suggested. The new option is available in the new version of Oxygen 24.1 released yesterday.

Best regards,
Florin

Hi Carlos,

Thank you again for your feedback. Indeed, it would be a very nice feature. We have an issue related to this topic (for JSON Schema, specifically) and I mentioned your request right there. I will keep you up to date with its status.

Regards,
Florin

Hi Carlos, I tried this schema: https://raw.githubusercontent.com/asyncapi/spec-json-schemas/master/schemas/2.3.0.json. It is the most recent release of the AsyncAPI spec schema. I associated it to an AsyncAPI document (you can also save it to your local machine), and the validation started automati...

Hi Carlos, Thank you very much for your detailed proposal. I added an issue related to this on our internal issue tracker, in order to do an in-depth analysis of AsyncAPI specification, and how can we integrate it in Oxygen. I will keep you up to date with its status. In the meantime, you can alread...

Hi Alex, Thank you for your interest. It looks like your XSD contains a large enumeration, that exceeds the default limit of 256 elements. You can use the customization attribute typesafeEnumMaxMembers to extend this limit. For example, if you want to extend it to 1000, you need to add inside the XS...

Hi Jamil,

I added an issue on our issue tracker to investigate the possibility of adding such an option. I will let you know as soon as possible when (or if) this feature will be implemented.

Thank you for your interest and feedback!

Regards,
Florin

Hi Jamil, Just a few clarifications related to the XML - JSON conversion. Starting from version 23.0, we made a little change to the conversion of empty XML elements. Thus, an empty XML element with both start tag and end tag, such as: <subnode></subnode> is converted to an empty JSON Object , i.e. ...

Hello, Thank you for your feedback. As you already mentioned, this XSD refers to other XSDs, by importing some global schema components. When converting to JSON Schema, they result into properties, that are placed on the root of the schema, and wrapped into an "anyOf" compositor. The eleme...

Hi Matthijs, Thanks for sending us this sample schema. I tried (on Windows) to validate multiple instances using this schema, and the validation seemed to work every time. Indeed, the schema is not oversized, but, as you mentioned, in combination with large instances, the validator might get confuse...