- From: Pedro Silva <pedro.cls93@gmail.com>
- Date: Sun, 23 Oct 2016 18:01:24 +0200
- To: John Cowan <cowan@ccil.org>
- Cc: Takuki Kamiya <tkamiya@us.fujitsu.com>, "public-exi@w3.org" <public-exi@w3.org>
- Message-ID: <CAJJ3jS8q3XTJYL=kgc7PdRg6g0cUH3-MCcnwdxHKKLK0mi-wGg@mail.gmail.com>
If I may suggest an additional point of view for consideration in favor of "Efficient Extensible Interchange". When searching on Google, Bing and Yahoo for EXI, the full extended name Efficient XML Interchange appears. Because this is a fairly unknown specification and is extending beyond XML, I suggest the acronym stand for something as a means for the public to understand what it is about. Pedro Silva 2016-10-22 4:38 GMT+02:00 John Cowan <cowan@ccil.org>: > > On Fri, Oct 21, 2016 at 7:54 PM, Takuki Kamiya <tkamiya@us.fujitsu.com> > wrote: > > >> The plan is that the acronym "EXI" will stand for "Efficient Extensible >> Interchange" >> instead of "Efficient XML interchange." This change is to indicate EXI is >> not >> only for XML, all while causing no changes to the acronym. > > > As an alternative plan, I propose that "EXI" be kept but that it not stand > for anything. Such "orphan initialisms" are common: to take three > internationally known examples, AT&T no longer stands for "American > Telephone and Telegraph", IBM no longer stands for "International Business > Machines", and KFC no longer stands for "Kentucky Fried Chicken". No > alternative expansions of these acronyms are in use. > > -- > John Cowan http://vrici.lojban.org/~cowan cowan@ccil.org > Be yourself. Especially do not feign a working knowledge of RDF where > no such knowledge exists. Neither be cynical about RELAX NG; for in > the face of all aridity and disenchantment in the world of markup, > James Clark is as perennial as the grass. --DeXiderata, Sean McGrath > > >
Received on Monday, 24 October 2016 09:09:45 UTC