OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] How to validate JSON against XSD schemas

wouldn't you at least have to reimplement a namespace solution.

On Mon, Jul 16, 2018 at 3:57 PM, Piers MacDonald <piers@piersmacdonald.com> wrote:

We're fortunate at the current point that the UBL schemas we're using don't have any validation features not possible in JSON schema but it's definitely a risk

On Mon, Jul 16, 2018 at 12:50 PM, Ihe Onwuka <ihe.onwuka@gmail.com> wrote:

Several XSD concepts do not have a JSON Schema equivalent so definitely not 2.

On Mon, Jul 16, 2018 at 3:43 PM, Piers MacDonald <piers@piersmacdonald.com> wrote:

I know the title sounds impossible, give it a second. We have XSD schemas created by an open-standards industry group. In our service we'd like our customers to be able to use JSON or XML when supplying data. What's the best practice in a situation like this?

  1. Convert JSON payloads to XML and validate against the XSD.

  2. Convert the XSD to JSON Schema and validate each content-type against it's own schema

  3. Convert the XSD to a class-based in language specification and do schema validation in code and then handle content negotiation in the api middleware

  4. Secret super option

FWIW, these XSD schemas are not overly trivial: ~4000 lines long, multiple namespaces with a half-dozen common schemas shared between them. Changes are rare (one every 2 years) but new schemas are added much more frequently (10 per year)

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS