Raw

Just arrived, online calendar app. Looks pretty nice, functionality seems basic but worked for me. Inputs: manual via Ajax UI; import from iCal or CSV (MS Outlook) formats. Outputs: Ajax UI; notifications via email, SMS or pop-up; Atom feed ( here's mine), iCal ( here's mine). The sharing appears to be just private or public.

See also: CNET write-up, it's all over tech.memeorandum.

What I reckon is exciting here is the mashup (integration) potential, especially with the SPARQL Calendar Demo now being live. It's pretty cool that a couple of enthusiasts like Elias and Lee can provide facilities that Google can't, essentially through their choice of technologies.

I think a tiny bit of work around FOAF might be helpful at this point in time. When I was last playing with aggregator stuff it looked like it would be a very good idea to include service references in FOAF profiles - Bloglines feedlists, del.icio.us feeds etc. There are some bits in the FOAF vocab already, but it would be nice to figure out constructs (hopefully without having to invent too much new stuff) good for the whole data-reading chain across services, something like:

_:Person hasDataAvailableFrom <personal service URI> .

<personal service URI> endpointForService <official service URI>;

format <URI for format> .

<official service URI> a DataSupplyService;

name "PlopFlush" .

<URI for format> grddlXSLT <URI for XSLT> .

(Actually I think I already did this in the FeedsOfMyFriends play, but very informally). Much of this would be more like hints - e.g. it shouldn't really be necessary to give the format media type along with the URI, but in practice such info would make life easier. A person would only really need to put the first two lines in their FOAF, the rest would be in the commons.

This would have the practical effect of making the FOAF profile the locator for dynamic attention info, a very handy bit of discovery.

@en