Comments on: REST needs Polymorphic XSD

By: Hipermídia e contratos dinâmicos: menor acoplamento | blog.caelum.com.br

Hipermídia e contratos dinâmicos: menor acoplamento | blog.caelum.com.br — Thu, 17 Dec 2009 12:07:54 +0000

[...] essas opções, a mais fácil e possivelmente perigosa envolve permitir qualquer tipo de conteúdo em qualquer campo, enquanto outra solução envolve o uso de tipos polimórficos: um perigoso início de schema-hell [...]

By: Hypermedia: making it easier to create dynamic contracts « Guilhermesilveira's Blog

Tue, 08 Dec 2009 11:25:06 +0000

[...] easy solution is to accept anything in too many places, which seems [...]

By: Michael Neale

Michael Neale — Tue, 07 Apr 2009 05:54:36 +0000

In the past, I have done xs:Any all over the place to allow for future changes. Oh, the horror

(all so it could still validate).

By: Alex

Alex — Thu, 02 Apr 2009 03:07:26 +0000

Do some people do schema validation? I’ve never met any yet. Ok, I’m young but still.

By: Randall

Randall — Tue, 31 Mar 2009 14:05:35 +0000

You might be able to achieve this by defining the base types (for polymorphism) in one schema, and the concrete types in a different schema that you could version. For example, in Listing 2 of http://www.ibm.com/developerworks/xml/library/ws-tip-xsdchoice.html the “Payment” type could be defined in NS1, while “CashPayment”, “CreditPayment”, and “CheckPayment” could be defined in NS2 (yet still extend NS1:Payment). NS2 could be versioned as needed, but you’d want to limit the changes to NS1.

The downside of this approach is that its very verbose, complex, and it may not even solve the problem in all cases.