+1 Michael Koziarski wrote: >> And that looks more complicated than it needs to be. > > Depends on what your requirements are. If you want a 'schema > language' to help non-rails clients, why not use one that's been > widely tested and has support in many different languages. Making up > something specific for rails would mean it's of questionable value to > non-rails programming environments. > > I'm not necessarily sold on the idea of generating a particular schema > language, or even of generating a schema at all, but I do know that > inventing our own is something we should be very wary of. > > >
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
