Genealogy, Visual Cultures, Deafness and Home Renovations
Visual Cultures
Mashups? From Wikipedia:
In web development, a mashup is a web page or application that combines data or functionality from two or more external sources to create a new service. The termmashup implies easy, fast integration, frequently using open APIs and data sources to produce results that were not the original reason for producing the raw source data. An example of a mashup is the use of cartographic data to add location information to real estate data, thereby creating a new and distinct web APIthat was not originally provided by either source.
Types of mashups
There are many types of mashups, such as consumer mashups, data mashups, and enterprise mashups. The most common type of mashup is the consumer mashup, aimed at the general public.
Data mashups combine similar types of media and information from multiple sources into a single representation. One example is the Havaria Information Services’AlertMap, which combines data from over 200 sources related to severe weather conditions, biohazard threats, and seismic information, and displays them on a map of the world; another is Chicago Crime Map, which indicates the crime rate and location of crime in Chicago.
Enterprise mashups focus data into a single presentation and allow for collaborative action among businesses and developers. This works well for an Agile Development project, which requires collaboration between the Developers and Customer proxy for defining and implementing the business requirements. Enterprise Mashups are secure, visually rich web applications that expose actionable information from diverse internal and external information sources.
[edit]Mashups versus portals
Mashups and portals are both content aggregation technologies. Portals are an older technology designed as an extension to traditional dynamic Web applications, in which the process of converting data content into marked-up Web pages is split into two phases: generation of markup “fragments” and aggregation of the fragments into pages. Each markup fragment is generated by a “portlet“, and the portal combines them into a single Web page. Portlets may be hosted locally on the portal server or remotely on another server.
Portal technology defines a complete event model covering reads and updates. A request for an aggregate page on a portal is translated into individual read operations on all the portlets that form the page (“render” operations on local, JSR 168 portlets or “getMarkup” operations on remote, WSRP portlets). If a submit button is pressed on any portlet on a portal page, it is translated into an update operation on that portlet alone (“processAction” on a local portlet or “performBlockingInteraction” on a remote, WSRP portlet). The update is then immediately followed by a read on all portlets on the page.
Portal technology is about server-side, presentation-tier aggregation. It cannot be used to drive more robust forms of application integration such as two-phase commit.
Mashups differ from portals in the following respects:
| Portal | Mashup | |
|---|---|---|
| Classification | Older technology, extension to traditional Web server model using well defined approach | Using newer, loosely defined “Web 2.0” techniques |
| Philosophy/Approach | Approaches aggregation by splitting role of Web server into two phases: markup generation and aggregation of markup fragments | Uses APIs provided by different content sites to aggregate and reuse the content in another way |
| Content dependencies | Aggregates presentation-oriented markup fragments (HTML, WML, VoiceXML, etc.) | Can operate on pure XML content and also on presentation-oriented content (e.g., HTML) |
| Location dependencies | Traditionally content aggregation takes place on the server | Content aggregation can take place either on the server or on the client |
| Aggregation style | “Salad bar” style: Aggregated content is presented ‘side-by-side’ without overlaps | “Melting Pot” style – Individual content may be combined in any manner, resulting in arbitrarily structured hybrid content |
| Event model | Read and update event models are defined through a specific portlet API | CRUD operations are based on REST architectural principles, but no formal API exists |
| Relevant standards | Portlet behaviour is governed by standards JSR 168, JSR 286 andWSRP, although portal page layout and portal functionality are undefined and vendor-specific | Base standards are XML interchanged as REST or Web Services.RSS and Atom are commonly used. More specific mashup standards are expected to emerge. |
The portal model has been around longer and has had greater investment and product research. Portal technology is therefore more standardised and mature. Over time, increasing maturity and standardization of mashup technology may make it more popular than portal technology. New versions of portal products are expected to eventually add mashup support while still supporting legacy portlet applications. Mashup technologies, in contrast, are not expected to provide support for portal standards.
Genealogy
I am finding Genealogy very addictive.
www.ancestry.com
Surveys and Consent Forms
I came across this interesting page…
https://www.surveymonkey.com/s.aspx?sm=00jR3aFM_2fTyJr5rp1xlsKg_3d_3d
http://www.bioethicsanddisability.org/
Nicole Lawder , CEO
Deafness Forum of Australia
218 Northbourne Avenue Braddon ACT 2612
phone 02 6262 7808
mobile 0404 037 177
TTY 02 6262 7809
Fax 02 6262 7810
email nicole.lawder@deafnessforum.org.au
web www.deafnessforum.org.au
www.hearingawarenessweek.org.au
Posted by DeafDave at Thursday, October 15, 2009 0 comments
