Her talk centered on three topics:
"Web services enable the bridging of data islands" (reinout: fits well with a previous entry by me about information islands)
"We need open indexes built from closed valuable data".
"Context is important in the dissemination of knowledge".
In New Zealand builders are among the first to use all the possibilities of mobile phones. So if there's a real and tangible benefit in using web services, they'll be very quick in adopting it.
You can do a lot of nice things when your drawing is stored in an accessible database (accessible by other applications) compared to stored just where your CAD package can reach it. There are some issues though:
Crime is a problem. In Manchester (UK) the idea cropped up to design security into the built environment. They try to analise all sorts of available ideas and try to find out whether and how to use them.
For example, you shouldn't place a tree close to a house. Fine, but: how close is close?
Very nice paper
The internet (http, xml, uri) changed everything. There is a change of paradigm: information containers dynamically composed and everything stored in a wide variety of formats.
All info is accessible. Good info. Bad info. (Reinout: just like "all news is good news" it seems like "any info is good info")
Per observed that we seemed to be aiming at a core model again.
Didn't write anything down for this one.
Per expects the semantic web to take off in the forseable future. Everything of value in the building industry should be fitted out with a URI (
http://www.example.com/buildingA/floor42). RDF, the semantic web's language (or a similar technology) is the metadata that describes those URIs.
Very important is the design of tools/methods/etc together with the industry.
Knowledge management can be done either within individual organisations or within a project. The latter is the subject of his presentation.
Knowledge management within a project has some challenges:
A couple of tools:
[Then followed an explanation of his framework, I didn't write it down].
At the end of the presentation someone asked whether his tools intervened directly into the proces or if they silently gathered information. The answer was "both".
Appropriate management of information flows is a competetive advantage.
Information exchange can be either "pull" (passive user) or "push" (active user). The definition of "push" being any information flow that occurs without explicit request by the person recieving it.
Actuall, a push at layer (n) may be implemented as a pull mode at layer (n-1), but that's a technicality. (You send (push) an email. But the recipient downloads the message from the server (pull)). You have to look at the level where there is the actual human/computer interaction.
There are two problems:
Push can be advantageous for reminders, when a rapid answer is required or when an answer is mandatory. Possible information overload is the disadvantage.
Pull limits information overload and doesn't disturb the incoming flow. The disadvantage is that it depends on an initiative by the user. Also information might be hard to find.
In the building industry a combination of push and pull is normally found.
Basic tenet: Try very hard to match the media richness to the task relevance.
My name is Reinout van Rees and I work a lot with Python (programming language) and Django (website framework). I live in The Netherlands and I'm happily married to Annie van Rees-Kooiman.
Most of my website content is in my weblog. You can keep up to date by subscribing to the automatic feeds (for instance with Google reader):