From: Stefan F. <ste...@we...> - 2012-02-15 20:28:46
|
Frederick: the argument for data/structure separation was mainly for the two tier structure, where more than one default (predefined) profile was possible. It would still be conceivable to define that inside the structure document (e.g. pbem="..." and ftf="..."), but then it is clearly data. For the 3-tier structure there is only one (meta)-default profile, however I find it still easier to have all tiers identified identically. Anyway: Thanks for adding your options. Stefan On 02/15/2012 08:16 PM, Frederick Weld wrote: > Stefan: > I do not perceive adding defaults to a schema as mixing schema/data > definition. Defining defaults is actually a common part of schema > definition (see XMLSchema). > But I don't argue to change the current setup as it is already well established. > > ==>All config changes I initiated are now part of the default property > file - I will also maintain that file when adding new options in the > future. > > -- Frederick > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel |