Archives for July 2010

Use Case: Facebook

Like it or not, Facebook isn’t going away.  Having just passed half a billion members, it looks to become a fixed star in the Internet firmament.  Nothing is assured – least of all in the world of social networking – but it seems to be the default social networking technology for grandmothers, teenagers, and mobiles. Which [...]

Another kind of jCard

Here’s the jCard for the New York Times { “vcard” : [ { "class": "Public", "fn": "NY Times", "uid": "b636257c-93ca-11df-a183-7c6d628f0c21", "photo": "http://graphics8.nytimes.com/images/misc/nytlogo379x64.gif", "connections": [ { "twitter": "nytimes", "id": "Twitter" }, { "feed": "http://www.nytimes.com/services/xml/rss/nyt/HomePage.xml", "id": "US Home Page" }, { "feed": "http://www.nytimes.com/services/xml/rss/nyt/World.xml", "id": "World" }, { "feed": "http://www.nytimes.com/services/xml/rss/nyt/US.xml", "id": "US" }, { "feed": "http://feeds.nytimes.com/nyt/rss/Business", "id": "Business" [...]

Amazing

I’ve spent the last few weeks talking to a lot of people – including all of you. Many of you have come up with amazing suggestions for Plexus.  Some of you have gotten a song-and-dance form me about thinking about front-ends to Plexus.  Which leads to even more amazing suggestions, and ideas.  It seems that [...]

jCard format revisions

No file format survives its first encounter with database schema.  As designed, jCard format was a bit wrong – more a list than a dictionary.  I’ve taken out some of the spurious syntactical elements, and added a new keyword, ‘connections’, which represents the list of connection points. The new jCard looks like this: { “vcard” [...]

hCard and jCard — and a request

The consensus opinions seems to be that the XHTML version of the card should remain named ‘hCard’, in order to avoid further muddying the waters – and also to entice hCard devotees to give Plexus a whirl. John Allsopp suggested ‘jCard’ for the JSON version, and I rather like that. Henceforth pCard is dead – [...]

hCard or pCard?

John Allsopp, the man who (literally) wrote the book on microformats, has given pCard format a once-over. His suggestion? “Why not simply leave it as hCard?” The differences between pCard and hCard format are – at this time – entirely semantic. Something is a pCard because it’s to be used with Plexus. Something is an [...]

pCard format (XHTML & JSON)

I’ve spent a few days thinking about pCard format, here are the initial results of my work… This is the XTHML microformat, which is completely compatible with hCard microformat: <div class=”vcard”> <span class=”class”>Public</span> <span class=”fn”>Mark Pesce</span> <span class=”nickname”>mpesce</span> <span class=”uid”>6fa459ea-ee8a-3ca4-894e-db77e160355e</span> <img class=”photo” src=”http://upload.wikimedia.org/wikipedia/en/3/3d/Mark-cafelife.jpg” atl=”Mark Pesce” /> <a class=”url” href=”twitter:mpesce”>Twitter</a> <a class=”url” href=”feed:http://blog.futurestreetconsulting.com/?feed=rss2″>The Human Network</a> <a [...]

API Thoughts

The Plexus API has to do three things: Provide an interface by which client/front-ends can talk to the Plex Provide an interface for data sharing (the Sharer) Provide an interface for the ‘connected data stream’ (the Listener) There are any number of approaches that could be taken to provide an API.  Most web services provide [...]

The TODO list

I’ve started a basic list of things that need to be designed and implemented in the prototype.  It’s on the wiki. Feel free to contribute.  But remember, KISS.

Front Endings

A big part of Saturday’s conversation with Tony Parisi concerned the Plexus front end: what does it look like, how does it work, how does it talk to Plexus? Most of this has intentionally been left up to the designer/developer/implementer because there is no one right way to design a Plexus front end.  If Plexus [...]