Hi Oisin, On Wed, 2011-03-23 at 12:41 +0000, Oisin Mulvihill wrote: > Hi Nicholas, > > This is quite interesting and quite couchdb like. I don't know much > (yet) about fluidinfo. I also posted a question about APIs earlier > with no response yet > (http://www.mail-archive.com/europython-improve@python.org/msg01561.html). >
You're not the first one to mention CouchDB in the context of Fluidinfo. They're quite different - to the extent that I ended up writing a blog post once to explain how: http://ntoll.org/article/fluiddb-is-not-couchdb (Comes in handy for moments like this... :-) > In the ep2011 iphone/android mobile app I'm working on I've been using > the XML data feed. I'm currently using phonegap for the first version. > I'm essentially working with a browser and javascript. Reading XML and > massaging a schedule out of it isn't pleasant. I'd +1 the REST > approach :) > OK... I'd be interested in helping out with this effort. It'd be great fun to plug Fluidinfo into a mobile app if only because of its openly writeable nature (for example, attendees could indicate which talks they want to attend and see who else is going, attach questions to event objects and so on). Of course this depends on getting EP2011 data into Fluidinfo. It's not very hard to do - the most important thing being that we organise/agree on a suitable schema. All the best, Nicholas. > All the best, > > Oisin > > > > On 23 March 2011 11:43, Nicholas Tollervey <nt...@ntoll.org> wrote: > Hi, > > A few weeks ago I volunteered to help with a Europython API. I > didn't > get any response :-( > > So being a go-ahead sort of a chap I've been doing some work > of my own. > John Pinner, Alex Willmer and I have recently been in contact > with each > other and I managed to get my hands on the Europython 2010 > data. > > I've used this as a starting point for experimenting with > Fluidinfo as a > means of providing an instant *writeable* HTTP/REST API for a > conference. > > Fluidinfo allows you to tag objects with information. I've > created > objects to represent two types of things: speakers and > events. Speakers are tagged with, er, speaker information and, > surprisingly enough, events are tagged with information about > talks, > meetings etc... > > You can have a look around with the explorer: > > http://explorer.fluidinfo.com/fluidinfo/europython.eu > > The namespace/tag hierarchy is on the left. Matching objects > and > associated values will be displayed in the main body. > > Here's an example query using fluidinfo.py (it's in PyPI): > > >>> headers, result = fluidinfo.call('GET', '/values', > tags=['europython.eu/2010/event/title', > 'europython.eu/2010/event/related-speakers', > 'europython.eu/2010/event/start-time', > 'europython.eu/2010/event/date', > 'europython.eu/2010/event/location'], query='has > europython.eu/2010/intended-audience/advanced and has > europython.eu/2010/streams/web') > > (Basically I'm asking for the title, speakers, start-time, > date and > location of all *advanced* talks at Europython2010 that are > about the > Web) > > >>> pprint.pprint(result) > {u'results': {u'id': {u'a95ba6f2-b148-4332-a385-cad911f6285b': > {u'europython.eu/2010/event/date': {u'value': u'Saturday 17 > July 2010'}, > > u'europython.eu/2010/event/location': {u'value': u'Lecture > Room 2'}, > > u'europython.eu/2010/event/related-speakers': {u'value': > [u'Gustavo > Narea']}, > > u'europython.eu/2010/event/start-time': {u'value': u'11:00'}, > > u'europython.eu/2010/event/title': {u'value': u'WSGI from > Start to > Finish'}}}}} > > A bit more explanation: > > Before being able to tag any objects you need to create the > tags you're > going to use in a top-level namespace associated with your > user. I've > created tags in the europython.eu/2010 namespace within which > I've > created the following sub-namespaces: > > class-type: Contains tags to indicate the type of classes held > at > Europython 2010. > > event: Contains tags used to describe / annotate an event at > Europython > 2010. > > intended-audience: Contains tags to indicate the intended > audience of > events at Europython 2010. > > locations: Contains tags to indicate the locations of events > help at > Europython 2010. > > speaker: Contains tags used to describe / annotate a speaker > at > Europython 2010. > > speakers: Contains tags to identify individual speakers. These > are > tagged to appropriate events at Europython 2010 - depending > upon their > involvement. > > streams: Contains tags to place events at Europython 2010 into > the > appropriate stream. > > Most importantly, using Fluidinfo means we'd have a writeable > API - i.e. > conference attendees can add, annotate and expand the data > about EP2011. > > Of course, there are bonus points because Fluidinfo is written > in > Python. > > Is this useful..? Can I get my hands on the EP2011 data when > it's > ready..? Will anyone respond this time..? ;-) > > Nicholas. > > _______________________________________________ > Europython-improve mailing list > Europython-improve@python.org > http://mail.python.org/mailman/listinfo/europython-improve > _______________________________________________ Europython-improve mailing list Europython-improve@python.org http://mail.python.org/mailman/listinfo/europython-improve
