Advanced Web Technologies
Tuesday, 21 December 2010
Wednesday, 31 March 2010
NameSpace
Name Space
As far as I understand this is just another way of holding the XML data under a different name < xnlns:mynamespace=”thisismynamespace” > would work just if it does not look like this -> < xmlns:mynamespace ="http://thisismynamespace.com"> without have to be link with exists URI. So I don’t know why The World Wide Web Consortium demand you use URI why?
As far as I understand this is just another way of holding the XML data under a different name < xnlns:mynamespace=”thisismynamespace” > would work just if it does not look like this -> < xmlns:mynamespace ="http://thisismynamespace.com"> without have to be link with exists URI. So I don’t know why The World Wide Web Consortium demand you use URI why?
Wednesday, 3 March 2010
Week17
The reason some web programmers chooses CSS over XSL some browsers are not compatible with XSL or render the web page differentially.
< xsl:stylesheet version=”1.0”
< xsl:transform version=”1.0”
there is no different between the two line of XSL tag
In my understanding it would be unfair to compare cascading style sheet with Extensible Stylesheet Language. It might look from the outset they do similar job but they are very different , if you ask me they don’t even belong to a same category. XSL is language like any other programming language with the ability to perform logical steps and the ability to hold data in variable for manipulation. To make real life example it would be like comparing old style bill board where you put posters for display and the new age bill poster where you have a large digital screen displaying information. The large screen and old style bill board have same ability to display information but with very big difference between them.
< xsl:stylesheet version=”1.0”
< xsl:transform version=”1.0”
there is no different between the two line of XSL tag
In my understanding it would be unfair to compare cascading style sheet with Extensible Stylesheet Language. It might look from the outset they do similar job but they are very different , if you ask me they don’t even belong to a same category. XSL is language like any other programming language with the ability to perform logical steps and the ability to hold data in variable for manipulation. To make real life example it would be like comparing old style bill board where you put posters for display and the new age bill poster where you have a large digital screen displaying information. The large screen and old style bill board have same ability to display information but with very big difference between them.
Wednesday, 10 February 2010
Week 15
Object model is divided into two parts
“Secondly a collection of objects or classes through which a program can examine and manipulate some specific parts of its world.”
XHTML is derived from XML file, compare to HTML it is very strict about syntax and dynamic.
< html xmlns=http://www.w3.org/1999/xhtml xml:lang=”en”>
The above line is use to represent a name space in HTML document.
Since the late 1990 the whole computer programming industry has gone crazy about object. Object this object that. Things are created as object or turned into one. DOM document object modelling is one example take a simple text document add a XML with one root and several tag which you might think the document need and use a XML phrase which turn your newly created xml document into object with nodes and each node is an object. What I am wording is that what happen if you no longer need an xml?
“Secondly a collection of objects or classes through which a program can examine and manipulate some specific parts of its world.”
XHTML is derived from XML file, compare to HTML it is very strict about syntax and dynamic.
< html xmlns=http://www.w3.org/1999/xhtml xml:lang=”en”>
The above line is use to represent a name space in HTML document.
Since the late 1990 the whole computer programming industry has gone crazy about object. Object this object that. Things are created as object or turned into one. DOM document object modelling is one example take a simple text document add a XML with one root and several tag which you might think the document need and use a XML phrase which turn your newly created xml document into object with nodes and each node is an object. What I am wording is that what happen if you no longer need an xml?
Wednesday, 27 January 2010
Week15

Why would you convert XML to DOM?
To allows programs and scripts to dynamically access ,update and manipulating the content, structure, and style of a XML document.
You might want a piece of software -an intractive website, say, to access parts of the document.
What are the implication of turning XML Doc in to DOM?
Turn XML DOC in to Nodes with tree like structure. Each Nodes In the xml Document must be accessed using method or iterating through each array which hold the XML object. poddess properties and method.
Programes which can be used to access XML DOM are JavaScript,PHP,ASP.NET as far as am I KNOW there might be more for example JAVA, and C++
< ?xml version="1.0" encoding="ISO-8859-1" ?>
< xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
< xs:element name="Payment_doc">
< xs:complexType>
< xs:sequence>
< xs:element name="Sender" type="xs:string"/>
< xs:complexType>
< xs:sequence>
< xs:element name="company" type="xs:string"/>
< xs:element name="name" type="xs:string"/>
< xs:element name="address" type="xs:string"/>
< xs:element name="city" type="xs:string"/>
< xs:element name="Postcode" type="xs:string"/>
< xs:element name="country" type="xs:string"/>
< /xs:sequence>
< /xs:complexType>
< /xs:element>
< xs:element name="Receiver" maxOccurs="1">
< xs:complexType>
< xs:sequence>
< xs:element name="name" type="xs:string"/>
< xs:element name="addres" type="xs:string" minOccurs="0"/>
< xs:element name="city" type="xs:positiveInteger"/>
< xs:element name="country" type="xs:decimal"/>
< /xs:sequence>
< /xs:complexType>
< /xs:element>
< /xs:sequence>
< xs:attribute name="Transaction" type="xs:string" use="required"/>
< /xs:complexType>
< /xs:element>
< /xs:schema>
Wednesday, 20 January 2010
Week 14 XML Schema
CMT3315
Simple type XML Schema: element which do not contain other elements and has no attributes.
Complex type XML Schema: element which does contain other elements and inclued attributes.
XML Schema is extensible Schema definition you can:
• Reuse your Schema in other Schemas
• Create your own data types derived from the standard types
• Reference multiple schemas in the same document
Three perfefined XML Schema are boolean,integer and ENTITIES.
Longer Questions:
Xs:schema is the standard namespace for XML schema definition.
URI is the Schema language definition, can be found using the link.
Bank XML Schema
Simple type XML Schema: element which do not contain other elements and has no attributes.
Complex type XML Schema: element which does contain other elements and inclued attributes.
XML Schema is extensible Schema definition you can:
• Reuse your Schema in other Schemas
• Create your own data types derived from the standard types
• Reference multiple schemas in the same document
Three perfefined XML Schema are boolean,integer and ENTITIES.
Longer Questions:
Xs:schema is the standard namespace for XML schema definition.
URI is the Schema language definition, can be found using the link.
Bank XML Schema
Wednesday, 9 December 2009
WEEK10 AJAX
Shorthand for asynchronous JavaScript and XML there is nothing new here JavaScript and xml are indene ant of each other but put the two language together and you have a new age use of software, you might say what is the point of having xml with JavaScript they are both will suited for the world wide web. The idea behind this different way of programming is that to enhance user experience but there are some drawbacks to AJAX
1.Ajax interfaces are substantially harder to develop properly than static pages.
2.Pages dynamically created using successive Ajax requests do not automatically register themselves with the browser's history engine more example can be found @
"Why use Ajax?". InterAKT. 2005-11-10. http://www.interaktonline.com
1.Ajax interfaces are substantially harder to develop properly than static pages.
2.Pages dynamically created using successive Ajax requests do not automatically register themselves with the browser's history engine more example can be found @
"Why use Ajax?". InterAKT. 2005-11-10. http://www.interaktonline.com
Subscribe to:
Comments (Atom)
