DSC00112

DSC00112
Originally uploaded by brof_ben

My lovely girl!!

Wikis in the Classroom

Wikis in the Classroom:

The new High Speed train

The new High Speed train
Originally uploaded by Aitor Escauriaza.

Very nice photo

W13-Beautiful Photo Album of Flickr API

The following is the easy teaching video showing how to use Flickr:


The API link1: http://metaatem.net/words
The API link2: http://splashr.com/

W12-Web2.0 Introduction

What put the 2 in Web 2.0?

Your instinct may tell you that some of the DNA-like attributes of Web 2.0 have been around for some time, and in truth, many have. So why didn’t we see Web 2.0 offerings popping up years ago? Because these older attributes, while significant, weren’t enough to produce viable Web 2.0 products. Some of the attributes we associate with Web 2.0 were introduced and commercialized as early as the mid 1990s; let’s call these Foundation Attributes. The figure detail below is part of a PDF that separates these “significant but not sufficient” attributes from the more recent Experience Attributes, those that create the kind of value that’s caused the recent excitement over Web 2.0.

When Experience Attributes are combined with Foundation Attributes for a Web 2.0 offering, the result can be a valuable new service with a fast-growth business model.

I identified these attributes based on how concisely they captured the capabilities of Web 2.0. Rather than returning to the underlying functional features of Web 2.0 (e.g., tagging, RSS), or overextending into the business impacts (e.g., mash-up ecologies), these attributes outline the capabilities of Web 2.0 independent of specific business concepts. Together, they represent the aspects of Web 2.0 success that you can apply in multiple market spaces.

Foundation Attributes Amazon was taking advantage of the Long Tail before we even had a name for the concept that has since become widespread. Ebay capitalized on the network effect to create a many-to-many marketplace. Early blogs were already embracing the value created from individual users.

These attributes — user-contributed value, the Long Tail, and network effect — are all Foundation Attributes of Web 2.0 services. They’re a part of many Web-based offerings, including some that we don’t call Web 2.0: User-Contributed Value - Users make substantive contributions to enhance the overall value of a service.

The Long Tail - Beating the sales of one or two best-seller products by using the Internet to sell a cumulatively greater amount of the products that have low demand or low sales.

Network Effect - For users, the value of the network substantially increases with the addition of each new user.

All of these attributes are significant parts of the Web 2.0 economic model, but aren’t sufficient to create the new value of Web 2.0 on their own. They enable Web 2.0 offerings to generate and maximize value from many sources, no matter how small they may be.

Experience Attributes Flickr, Google Maps, and Wikipedia are all unique services that were undeliverable before Web 2.0. What makes us take notice is the novel way they use Experience Attributes to generate value. (Foundation Attributes then distribute that value across the network and down the Long Tail.) Experience Attributes include:

Decentralization - Users experience services on their terms, not those of a centralized authority, such as a corporation. Co-creation - Users participate in the creation and delivery of the primary value of a service.

Remixability - Experiences are created and tailored to user needs by integrating the capabilities of multiple services and organizations. Emergent Systems - Cumulative actions at the lowest levels of the system drive the form and value of the overall system. Users derive value not only from the service itself, but also the overall shape that a service inherits from user behaviors.

By blurring the lines that traditionally delineate supplier, vendor, and customer, these services have pioneered new value streams that can output new types of offerings, harness new efficiencies, and produce higher levels of continuous innovation. Experience Attributes make Web 2.0 offerings fierce competitors in their respective marketplaces.

W11-XML DOM and SAX

Document Object Model (DOM) is a platform- and language-independent standard object model for representing HTML or XML and related formats. Strictly speaking, one should refer to "the DOM", but in practice, the "the" article is usually dropped.
Because DOM supports navigation in any direction (e.g., parent and previous sibling) and allows for arbitrary modifications, an implementation must at least buffer the document that has been read so far (or some parsed form of it). Hence DOM is likely to be best suited for applications where the document must be accessed repeatedly or out of sequence order. If the application is strictly sequential and one-pass, the SAX model is likely to be faster and use less memory.

The Simple API for XML (SAX) is a serial access parser API for XML. SAX provides a mechanism for reading data from an XML document. It is a popular alternative to the Document Object Model (DOM).
The W3C DOM specifications are divided into levels, each of which contains required and optional modules. To claim to support a level, an application must implement all the requirements of the claimed level and the levels below it. An application may also support vendor-specific extensions which don't conflict with the W3C standards. As of 2005, Level 1, Level 2, and some modules of Level 3 are W3C Recommendations which means they have reached their final form.
Level 0
The application supports an intermediate DOM, which existed before the creation of DOM Level 1. Examples include the DHTML Object Model or the Netscape intermediate DOM. Level 0 is not a formal specification published by the W3C but rather a shorthand that refers to what existed before the standardization process.
Level 1
Navigation of DOM (HTML and XML) document (tree structure) and content manipulation (includes adding elements). HTML-specific elements are included as well.
Level 2
XML namespace support, filtered views and events.
Level 3
Consists of 6 different specifications:
DOM Level 3 Core;
DOM Level 3 Load and Save;
DOM Level 3 XPath;
DOM Level 3 Views and Formatting;
DOM Level 3 Requirements; and
DOM Level 3 Validation, which further enhances the DOM
-------------------------------------------------------------------------------
A parser which implements SAX (ie, a SAX Parser) functions as a stream parser, with an event-driven API. The user defines a number of callback methods that will be called when events occur during parsing. The SAX events include:
XML Text nodes
XML Element nodes
XML Processing Instructions
XML Comments
Events are fired when each of these XML features are encountered, and again when the end of them is encountered. XML attributes are provided as part of the data passed to element events.
SAX parsing is unidirectional; previously parsed data cannot be re-read without starting the parsing operation again.
----------------------------------------------------------------------------------

W10 XML (Critical Description)

The Extensible Markup Language (XML) is a W3C-recommended general-purpose markup language that supports a wide variety of applications. XML languages or 'dialects' may be designed by anyone and may be processed by conforming software. XML is also designed to be reasonably human-legible, and to this end, terseness was not considered essential in its structure. XML is a simplified subset of Standard Generalized Markup Language (SGML). Its primary purpose is to facilitate the sharing of data across different information systems, particularly systems connected via the Internet[1]. Formally defined markup tag and syntax language sets are based on XML (such as RSS, MathML, GraphML, XHTML, Scalable Vector Graphics, MusicXML and thousands of other examples) allow diverse software to reliably understand information formatted and passed in these languages within a given type (e.g. for music notation.) [better attribution for the following is needed] XML has been consistent with the general evolution of micro-computers within basic camps (by O.S. or processor type for example) that enables specialization of repetitive tasks. In XML's case, the task is to create a skeletal construct for exchanging complete, often complex, types of data reliably. Accomplishing the task in a formal collective fashion lowers costs and increases functionality and reliability for individual developers and the end user. XML is an open, meaning fee-free standard, with an engineering-savvy governing board and standards adoption process, like many recent digital systems initiatives including USB, flash memory formats, and digital television.
Advantages and disadvantages:
Advantages:
1.It is a simultaneously human and machine-readable format;
2.It supports Unicode, allowing almost any information in any written human language to be communicated;
3.It can represent the most general computer science data structures: records, lists and trees;
4.Its self-documenting format describes structure and field names as well as specific values;
5.The strict syntax and parsing requirements make the necessary parsing algorithms extremely simple, efficient, and consistent.
6.XML is heavily used as a format for document storage and processing, both online and offline,
7.Its logically-verifiable format is based on international standards;
The hierarchical structure is suitable for most (but not all) types of documents;
8.It manifests as plain text files, which are less restrictive than other proprietary document formats;
9.It is platform-independent, thus relatively immune to changes in technology;
10.Its predecessor, SGML, has been in use since 1986, so there is extensive experience and software available.
Disadvantages:
1.XML syntax is redundant or too large relative to binary representations of similar data.
2.The redundancy may affect application efficiency through higher storage, transmission and processing costs.
3.XML syntax is too verbose relative to other alternative 'text-based' data transmission formats.
4.No intrinsic data type support, XML provides no specific notion of "integer", "string", "boolean", "date", and so on.
5.The hierarchical model for representation is limited in comparison to the relational model or an object oriented graph.
6Expressing overlapping (non-hierarchical) node relationships requires extra effort.

Some words on What is the XML DOM?
1.The XML DOM is the Document Object Model for XML
2.The XML DOM is platform- and language-independent
3.The XML DOM defines a standard set of objects for XML
4.The XML DOM defines a standard way to access XML documents
5.The XML DOM defines a standard way to manipulate XML documents
6.The XML DOM is a W3C standard
The DOM views XML documents as a tree-structure. All elements; their containing text and their attributes, can be accessed through the DOM tree. Their contents can be modified or deleted, and new elements can be created. The elements, their text, and their attributes are all known as nodes.
We can learn XML Dom in W3C tutorial
XML 2.0 features is very a very good artical to refer XML's future development.