To:

All

Subject:

Session Idea: Developer Tools for Building Ottawa Services

Friday, May 15 at 04:38PM

What are the basic building blocks for letting developers within the City of Ottawa (and affiliated institutions) develop services and expose data? What are the tools needed that allow all developers to use City of Ottawa services and data?

How can developers, designers, and architects in or out of the City of Ottawa embrace openness?

I would like to discuss specific (but general) technology tools for building open services and making data available.

[Reply privately to Darcy Quesnel]
Monday, May 18 at 09:16PM

I think that policy review and changes will be the first step, at least at the City of Ottawa. Currently developers are not given any direction to be more "open" or "expose data", in fact they are likely encouraged to do the opposite. I think that residents will need to voice their desire or need for more openness, including what information and format are of most interest.

[Reply privately to Robert Giggey]
Wednesday, May 20 at 10:04AM

More openness is good. Exposing data is good. The point about format came up in the Top Task session. Somebody suggested that users want to use embeddable widgets - to choose a format that suits their task.

Laura Wesley suggested something like CDC's selection. See http://www.cdc.gov/Widgets/

The advantage of offering widgets is that CDC goes beyond openness and exposing data, and offers a choice of interface, a choice of what links are important to a user, a wide variety of widget formats, the HTML to embed them, and the webstats for each widget.

[Reply privately to Scott Smith]

Join the Conversation

Only attendees can send and receive messages.

If you are already a member, sign in.

Otherwise, visit the ChangeCamp Ottawa home page to join.