more general information stored in a way that is more accessible
smaller pieces. you can make a boat out of this, or a car, or a farmhouse because it can be broken down into smaller pieces.
portability of information.
here, the people were portable, coming to the WPA office for jobs.
And madame secretary has the information come right to her.
Tell the story about Jack Blum. Thinking of closed--vs open -- systems, the software is one part of it, but it’s what you ask it to do. people use what they think are open systems, but they build them closed. Habit, many times expediency. So instead of looking at data, people create content management systems that mimic a folder structure that makes content brittle--you can’t move it to another part of a website without breaking it. You can’t deliver it to a new kind of system because you built your data system to deliver pages rather than flexible outputs. You can’t upgrade to the new version of the software because you have integrated the content into the software. It was faster.
so, here we are. Still standing in line.
Thinking about building your open system, first, enter the project with the mindset that you want to get your information OUT. You want to have the smaller pieces of content, so that you can be flexible. You want to use metadata so you can bring things together. You want to separate the content from the presentation layer, for real. Think about different ways you want to use content. For a blog post? On facebook or twitter? Will you deliver photos on a cool tablet device? What do you offer as a service? NARA docs teach... NSF iPad app
It’s the Data… Open & the Digital Strategy (Gwynne Kostin, Director, Digital Services Innovation Center, GSA )
Getting to Open Gwynne Kostin Director Digital Services Innovation CenterOffice of Citizen Services & Innovative Technologies U.S. General Services Administration