+ 1 to MetaModel Federation
Regards, Gajanan Patil -----Original Message----- From: Michel Kern [mailto:[email protected]] Sent: Friday, July 21, 2017 11:07 PM To: [email protected] Subject: Re: [DISCUSS] Name of new subproject for REST API webapp Hello My vote goes to Membrane first, then Federator Best Regards Michel Kern On 21-07-17 09:31, Dennis Du Krøger wrote: > Do you mean "MetaModel Federator" or "MetaModel Federation"? I was Federator > on the short list, but Federation in your last mail. > > > Anyway, my vote goes to Membrane. > > > BR, > > Dennis > > ________________________________ > From: Kasper Sørensen > <[email protected]<mailto:[email protected]>> > Sent: 21 July 2017 06:43:28 > To: [email protected]<mailto:[email protected]> > Subject: Re: Re: [DISCUSS] Name of new subproject for REST API webapp > > They don't seem so memerable to me TBH. > > I guess I'm leaning towards MetaModel Federation. Shall we have a vote? > > 2017-07-20 11:56 GMT-07:00 Michel Kern > <[email protected]<mailto:[email protected]>>: > >> Hello >> >> Then I suggest also: >> - Intertwine >> - Link >> - Bond >> - Mingle >> - Transduce (or Transducer) >> >> Best Regards >> Michel Kern >> >> >> On 20-07-17 18:24, Kasper Sørensen wrote: >> >>> One thing ... Try to say "MetaModel Membrane" really quick ... it's >>> a lot of M's! :-D >>> >>> 2017-07-19 3:29 GMT-07:00 Dennis Du Krøger < >>> [email protected]<mailto:[email protected]>>: >>> >>> I don't mind Membrane, but to me it is the opposite: A membrane is a >>>> partition or barrier. It doesn't bind anything together. >>>> >>>> Still works though; Most membranes allows some things to pass >>>> through it, while keeping others separate. :) >>>> >>>> BR, >>>> Dennis >>>> >>>> -----Original Message----- >>>> From: Kasper Sørensen [mailto:[email protected]] >>>> Sent: 19. juli 2017 05:55 >>>> To: [email protected]<mailto:[email protected]> >>>> Subject: Re: [DISCUSS] Name of new subproject for REST API webapp >>>> >>>> Hmm I like the idea of membrane. Not for it's "interface"ness, but >>>> for it's metaphor of binding things together (oh well, I guess >>>> interfaces do that too, but IMO the metaphor is stronger here for >>>> e.g. cross-querying datastores and such). >>>> >>>> So I would modify my preference to either: >>>> >>>> MetaModel Federator >>>> MetaModel Membrane >>>> >>>> 2017-07-17 7:19 GMT-07:00 Michel Kern >>>> <[email protected]<mailto:[email protected]>>: >>>> >>>> Hello >>>>> 'Federator' is ok for me (else it fullname would be 'Apache >>>>> MetaModel Model Federator') >>>>> >>>>> But I suggest also >>>>> - 'enterprise' as a Trekkie wink >>>>> - metaphors for 'interface' like 'membrane' >>>>> - metaphors of 'interact' like 'admix', 'mingle' >>>>> - metaphors for 'exchange' like 'swapper' or 'exchanger' >>>>> - metaphors for API like 'interoperator' >>>>> >>>>> See also https://pronovix.com/blog/what-api >>>>> >>>>> Best Regards >>>>> Michel Kern >>>>> >>>>> >>>>> >>>>> On 17-07-17 15:46, Kasper Sørensen wrote: >>>>> >>>>> I personally like "MetaModel Federator". Or some word/phrase that >>>>>> catches the meaning of federation / collection / gathering / >>>>>> >>>>> centralization. >>>>> 2017-07-15 10:16 GMT-07:00 Kasper Sørensen >>>>>> <[email protected] >>>>>> m>: >>>>>> >>>>>> Hi all, >>>>>> >>>>>>> As per the VOTE thread and VOTE RESULT just before, we are >>>>>>> creating a new subproject for the REST API webapp for MetaModel. >>>>>>> >>>>>>> So the question arises: What should we name it. >>>>>>> >>>>>>> Here are the suggestions that people passed in the VOTE thread. >>>>>>> Can you indicate what you prefer, or if you have other suggestions? >>>>>>> >>>>>>> RESTMetaDataFederation >>>>>>> MetaModel Federator >>>>>>> MetaFederator >>>>>>> Quid pro quo >>>>>>> Waggle dance >>>>>>> Wanderlust >>>>>>> Lindy hop >>>>>>> Fair trade >>>>>>> >>>>>>> >>>>>>> In addition, please consider that there are certain naming >>>>>>> considerations that the ASF asks of us [1]. We will probably >>>>>>> make it easier for ourselves if the subproject name is prefixed >>>>>>> with "Apache MetaModel" as to avoid too much legal research to >>>>>>> have to take place. >>>>>>> >>>>>>> [1] https://www.apache.org/dev/project-names.html >>>>>>> >>>>>>> Best regards, >>>>>>> Kasper >>>>>>> >>>>>>> >>>>>>> "Legal Disclaimer: This electronic message and all contents contain information from Cybage Software Private Limited which may be privileged, confidential, or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is strictly prohibited. If you have received this electronic message in error please notify the sender by reply e-mail to and destroy the original message and all copies. Cybage has taken every reasonable precaution to minimize the risk of malicious content in the mail, but is not liable for any damage you may sustain as a result of any malicious content in this e-mail. You should carry out your own malicious content checks before opening the e-mail or attachment." www.cybage.com
