Skip to main content

Poll: Best Atom Publishing Protocol abbreviation?

Since there's a debate about the best-practice abbreviation to use, I thought I'd run a survey:


  1. Atompub should be the other option. Case matters and camelcase messes things things up... That would have been my vote...


  2. Can we vote for a follow-up choice? Personally, I like the term "APP" because it's short, and can be said as an acronym. I like it because it conjures up the idea of an application. (Which is also a bad thing for it) It is, however, completely un-googleable.

    As my second choice, I like Atompub. It's easy to say, easy to search for, and gives a clear impression that it's short for "Atom Pub[lishing Protocol]"

    I asked my wife, (who has no prior introduction, save for shoulder surfing my emails) and she voted for "APP"

  3. Koranteng - I think we need to consider all of these to be case-insensitive but case preserving wherever possible :)

    Duck - Good point, but I'm constrained by the technology I've chosen to do the poll :).  It may be moot as aToMpUb seems to be getting a clear majority, not just plurality, of #1 votes.  


Post a Comment

Popular posts from this blog

The problem with creation date metadata in PDF documents

Last night Rachel Maddow talked about an apparently fake NSA document "leaked" to her organization.  There's a lot of info there, I suggest you listen to the whole thing:

There's a lot to unpack there but it looks like somebody tried to fool MSNBC into running with a fake accusation based on faked NSA documents, apparently based on cloning the document the Intercept published back on 6/5/2017, which to all appearances was itself a real NSA document in PDF form.

I think the main thrust of this story is chilling and really important to get straight -- some person or persons unknown is sending forged PDFs to news organization(s), apparently trying to get them to run stories based on forged documents.  And I completely agree with Maddow that she was right to send up a "signal flare" to all the news organizations to look out for forgeries.  Really, really, really import…

Personal Web Discovery (aka Webfinger)

There's a particular discovery problem for open and distributed protocols such as OpenID, OAuth, Portable Contacts, Activity Streams, and OpenSocial.  It seems like a trivial problem, but it's one of the stumbling blocks that slows mass adoption.  We need to fix it.  So first, I'm going to name it:

The Personal Web Discovery Problem:  Given a person, how do I find out what services that person uses?
This does sound trivial, doesn't it?  And it is easy as long as you're service-centric; if you're building on top of social network X, there is no discovery problem, or at least only a trivial one that can be solved with proprietary APIs.  But what if you want to build on top of X,Y, and Z?  Well, you write code to make the user log in to each one so you can call those proprietary APIs... which means the user has to tell you their identity (and probably password) on each one... and the user has already clicked the Back button because this is complicated and annoying.

The hill outside Google HQ, about a 270 degree panorama.