API Design Session Followups

[Bryce "City CarShare" Nesbitt]

I've created two new Google Groups, to continue the design of the two
API's we spent some time whiteboarding:

http://groups.google.com/group/api-design-tripml
http://groups.google.com/group/api-design-transit-service-alerts

Who can post the whiteboard photos? Who else wants admin rights to
the groups?


I'm also interested (actually more interested) in forming a group to
design this: a protocol to check if a reservable mode is available
now, in the future, and to actually book it (e.g. reserve a bike at
CalTrain at 6pm):

1. Level 1: Basic contact information, areas, costs, and locations
of services provided.
2. Level 2: Adds real time status to level 1 (e.g. "53 bikes
available now").
3. Level 3: Allows future queries as to availability and price of
service (e.g. 10 bikes at 6pm, $1 per hour).
4. Level 4: Allows reserving a future service (e.g. I want a bike
at 6pm).
5. Level 5: Integrated fare payment (e.g. Here's my credit cared).

City CarShare has a business case for this now, and a transit
integration case in the future (we want trip planners to offer cross
mode trips, starting with BART and transferring to car share).

[Joe Hughes]

Thanks for setting those up, Bryce. I uploaded the handful of
whiteboard shots that I had to file sections of those groups.

Joe