Mashup Mindset
Tom Reamy
Chief Knowledge Architect
KAPS Group
Knowledge Architecture Professional Services
http://www.kapsgroup.com
Essential features
Simple Api
Content from 2 or more sites
Current emphasis on presentation
Content structure, data
Self Service – embed variety of mashups
90% of mashup examples use google maps
How to create mashups that are more than just cool
Content aggregation
2 sources or more
Faceted Navigation / Dynamic Classification
One facet – geography
Another – people
Another – event
Map of terrorist activities by region and range of activities within each region
Business of mashups
e-commerce sites – targeted advertising
within the enterprise
combine internet content with internal content
Libraries
Maps of libraries
“map” of library catalog
amazon library service
Platform for Mashups
Integrated – no standards now, everything is a complete custom job
Semantic
Semantic Infrastructure
How to develop diff
Location, people, companies, jobs, rental properties events
Ontology – model of the relationships of a dimension
Next – build in some intelligence – know how much VP in industry x usually makes – flag any that are higher than average.
IBM
Allows users can add and remove web services, with intelligence.
Mashups and folksonomy
Wikipedia del.icio.us
Just metadata that users add
Flats lists to not a –onomy make
“No quality control”
complexity theory
Santa fe istitute
Self-organizing
Example : Ant colonies – clear tunnels with no idea of how to clear a tunnel
Evolutionary mechanism – feedback with consequences
- get bad feedback – you die
- you have to rank everything
- wikipedia
mashups and evolution
- starting to become social
• they are easy to build
evolve better structures
refining taxonomies / folksonomies
embed feedback into mashup – evolve
who uses it, how are they using it?
Talis library mashup competition
Summary
Mashups – dynamic content from 2 or more
Need simple api
Use and build on content aggregation
Need content structure
If not available evolve folksonomies into standard taxonomies
Chief Knowledge Architect
KAPS Group
Knowledge Architecture Professional Services
http://www.kapsgroup.com
Essential features
Simple Api
Content from 2 or more sites
Current emphasis on presentation
Content structure, data
Self Service – embed variety of mashups
90% of mashup examples use google maps
How to create mashups that are more than just cool
Content aggregation
2 sources or more
Faceted Navigation / Dynamic Classification
One facet – geography
Another – people
Another – event
Map of terrorist activities by region and range of activities within each region
Business of mashups
e-commerce sites – targeted advertising
within the enterprise
combine internet content with internal content
Libraries
Maps of libraries
“map” of library catalog
amazon library service
Platform for Mashups
Integrated – no standards now, everything is a complete custom job
Semantic
Semantic Infrastructure
How to develop diff
Location, people, companies, jobs, rental properties events
Ontology – model of the relationships of a dimension
Next – build in some intelligence – know how much VP in industry x usually makes – flag any that are higher than average.
IBM
Allows users can add and remove web services, with intelligence.
Mashups and folksonomy
Wikipedia del.icio.us
Just metadata that users add
Flats lists to not a –onomy make
“No quality control”
complexity theory
Santa fe istitute
Self-organizing
Example : Ant colonies – clear tunnels with no idea of how to clear a tunnel
Evolutionary mechanism – feedback with consequences
- get bad feedback – you die
- you have to rank everything
- wikipedia
mashups and evolution
- starting to become social
• they are easy to build
evolve better structures
refining taxonomies / folksonomies
embed feedback into mashup – evolve
who uses it, how are they using it?
Talis library mashup competition
Summary
Mashups – dynamic content from 2 or more
Need simple api
Use and build on content aggregation
Need content structure
If not available evolve folksonomies into standard taxonomies
posted by Tricia @CheekyAttitude at 3:59 PM
0 Comments:
Post a Comment
<< Home