Homing in on the REBOL/Services TLA
As REBOL/Services closes in on its first prototype release (Alpha 1), it's also time to pick the final TLA three letter acronym (TLA). In blog 0105 I asked for your help in naming the TLA, and I received a good number of suggestions. I would like to thank you all for sending them to me.
Let me briefly summarize the purpose of using a TLA for REBOL/Service (since in general I do not like TLA's and try to avoid them whenever possible). But, the reasons are quite simple:
Further requirements of the TLA are:
Although it is not a requirement that the TLA must contain the word REBOL, it may be a good idea to include it because REBOL/Services takes advantage of the dialecting method of relative expressions, not only for the data but for the metadata and descriptive levels as well. This is much more difficult to do without the dialecting methodology of REBOL. I realize there was a lot of discussion about not putting REBOL in the name to make it more general and adoptable. I understand and appreciate that consideration.
In my next blog, I will list the acronyms that have been suggested so far, and we can take a look at which ones would work best based on the above requirements.