> 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.
Because that's a lot of work, and a standard format makes that work unneeded. The Beast forum doesn't need to publish an API doc, because it implements ActiveResource and so an ARes client can auto-assume almost everything it needs. Highrise hasn't published its API yet, but I bet it's going to be a lot simpler, since it was the very inspiration for ActiveResource, which it also implements. > Your proposed format suffers from the same limitations in that almost > everything provided is optional. How is this a limitation? Everything provided is optional. RelaxNG just forces you to declare this, which I think is unnecessary. > 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? This only works if there is at least one object saved in the database. -- Eric --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
