+1 for the name change. What i think we need though is to start tracking our "reserved" words and writing up some documentation around them.
Thanks Justin On 2013-06-11, at 1:05 PM, Antranig Basman <[email protected]> wrote: > This was discussed during Colin's recent visit to Boulder. I've written up > the main requirement as http://issues.fluidproject.org/browse/FLUID-5045 - > which I was reminded of during today's UIO strategy conversation today with > Justin, Yura, Cindy and Anastasia - in order to improve the ModelRelay system > as Anastasia has written up as > http://issues.fluidproject.org/browse/FLUID-5024, we first need to supply a > system whereby we can freely mix model transformations documents with general > IoC material. This is currently not possible as a result of the ambiguity in > meaning of "expander" which has an unrelated implementation in the two > systems. > > The proposal is to rename the use of "expander" in all model transformation > documents to "transform" as both being more intelligible and descriptive as > well as not colliding with our use of "expander". The exact keyword used will > be configurable as an option to the ModelTransformations system, enabling us > to support old documents if we require (in particular until the next GPII > release cycle). > > Please supply any questions, comments or other proposals - > > Cheers, > Antranig > _______________________________________________________ > fluid-work mailing list - [email protected] > To unsubscribe, change settings or access archives, > see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work _______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
