Don’t start with the documents start with the domain Placing the project's primary focus on the core domain and domain logic Basing complex designs on a model Initiating a creative collaboration between technical and domain experts to iteratively cut ever closer to the conceptual heart of the problem.
Rich user journeys, stickiness',
Focus shifts from the assets to the model. We associate assets with the things in our model but allow the model to handle the context. Model is device agnostic so allows us build appropriate views for any given device.
Contribute to wikipedia where necessary. Music site uses musicbrainz in a similar way. Birth of open source vocabularies.
These relationships mean more interesting user journeys, greater link density, and more interesting queries on the data.
Model, and inparticualr working with RDF, allows to easily integrate a variety of data sources. It is the model that pulls them together to provide a constistent user experience. In summary: two ways that semantic web like technologies change the way we work. Becoming thing focused as opposed to document focused, a culture of building with open vocabulries to add context and links that would never be possible otherwise, getting the most value out annotations. Tag with a web scale identifer hooks that asset in the web of linked data and the unlimited potential to see the asset in new contexts.
How the emergence of the semantic web changes our approach to information architecture
How does the emergence of the Semantic Web change the way Information Architects design web products?