[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Socially engineering the protocol name.
- To: atom-protocol <atom-protocol@xxxxxxx>
- Subject: Re: Socially engineering the protocol name.
- From: "Thomas Broyer" <t.broyer@xxxxxxxxx>
- Date: Wed, 20 Jun 2007 18:28:20 +0200
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iWzggjP6R0laYf7koFANoGBpif92lWDf+ZATJF1rtcZuUUaBNXz4R2NT2HAgM+nbP9fGs0nRShy2EoPq8bgo6YlVDTDfCGfW4jdcYSTDPQzcVGQ2wL3gkUFduKmc8crgtgEi6qOjstVmgyFrFO/pdiSjscx7JTay29O1/Dz92A0=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=d6hKnM6Dm78rCLnzgOFY1FRBESJeKPrk9wrVkwCRQocCuvDEHJTqbXQ4SFeiUvjr65tf2ArRQz/yalcqvSc8Xmr3T8kXjpde4qmGLMEzjJfb38XgNvP5KcSeMSXH+yagR6qq5WQvuknI3wkWjguqiKE74Bh8mAB2ciYTiITK/uk=
- In-reply-to: <452547.38058.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- List-archive: <http://www.imc.org/atom-protocol/mail-archive/>
- List-id: <atom-protocol.imc.org>
- List-unsubscribe: <mailto:atom-protocol-request@imc.org?body=unsubscribe>
- References: <452547.38058.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Sender: owner-atom-protocol@xxxxxxxxxxxx
2007/6/20, Matt Harmon:
Hi,
How about calling it the Fusion protocol (or just
"Fusion")?
How about Pie or Echo [1]? (sorry couldn't resist)
A random suggestion from a lurking civilian (and
possible future APP applications developer)
No, seriously, we're not trying to *invent* a name for the protocol
but to gain consensus on which of the existing names to push as the
one to use: APP, AtomPP, Atompub, AtomProtocol, Atom protocol, etc.
I think I'll keep "Atom protocol" or "AtomProtocol" or eventually just
"Atom" when not ambiguous in context.
[1] see introduction of http://intertwingly.net/wiki/pie/ProjectNameProcess
--
Thomas Broyer