> RelaxNG is a schema for *XML*, not for a *model*. This schema is only > indirectly used to construct XML POSTs/PUTs, its primary use is for > the client to understand the makeup of your data. In fact, "Elements" > and "text nodes" aren't the correct conceptual way to describe a data > model.
Seems a fairly arbitrary distinction, given that we're talking about a schema for the API which will be returning xml documents... Automatically generating a schema seems like overkill, given that the schema for your models changes rarely, what's wrong with just a human readable API doc page. Like: http://basecamphq.com/api/ > So, I think RelaxNG is inappropriate for a simple, flexible > description of a data model, and that we should keep the format as > close to the current AR#to_xml format as possible. Your proposed format suffers from the same limitations in that almost everything provided is optional. I just don't really see how this enables anything new, surely anything javascript can do with the schema document, could also be done with the xml document received in response to /foos/1.xml? -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
