1. XML for Information Management – Day 2 Airi Salminen University of Erlangen-Nuremberg Computational Linguistics Instructor: Professor Airi Salminen http://users.jyu.fi/~airi/ 12.1.-16.1. 2009 XML for Information Management

2. XML for Information Management – Day 2 Airi Salminen 2  1. Markup languages  2. Structured documents  3. World Wide Web Consortium Day 2: Background of XML Outline

3. XML for Information Management – Day 2 Airi Salminen 3 1. Markup languages intended for human readers intended for computers Markup

4. XML for Information Management – Day 2 Airi Salminen 4 punctuational presentational Markup for human readers Texthasalwaysincludedsomekindofmarkupalsobeforethetimeofcomp uters to clarify the written expression Text has always included some kind of markup, also before the time of computers. 1. Markup languages

5. XML for Information Management – Day 2 Airi Salminen 5 presentational procedural descriptive Markup for computers to provide information for a software module In markup languages clear separation of markup and primary content. Markup is metadata, adding some information to the primary data. 1. Markup languages

6. XML for Information Management – Day 2 Airi Salminen 6 Presentational markup information about the way the software module should present the primary content to the human perceiver In markup languages there is clear separation of markup and primary content. Markup is metadata, adding some information to the primary data. The tags and represent presentational markup in HTML. 1. Markup languages The markup in an HTML file

7. XML for Information Management – Day 2 Airi Salminen 7 Procedural markup a processing instruction for the software module Example of an XML element ]]> The strings represent procedural markup in XML. as character data ]]> instructs the XML processor to to continue normal identification of markup Example of an XML element ]]> 1. Markup languages The markup in an XML file

8. XML for Information Management – Day 2 Airi Salminen 8 Declarative markup describes the content of a piece of primary content, what it is, or declares that the piece is a member of a particular class Steve Chung steve.chung@university.ca XML is primarily for declarative markup. 1. Markup languages The markup in an XML file

9. XML for Information Management – Day 2 Airi Salminen 9 Markup in XML ‣All markup delivers information to XML Processor. DTD represents metamarkup, facilitating the definition of the markup vocabulary. ‣Markup in an XML document is usually classified in respect to the application. ‣Processing instructions represent procedural markup. ‣Element tags represent declarative markup. ‣In the specification of an XML application different kinds of meanings can be given to element names, they can be processing instructions to the application or instructions about the way the content should be presented by the application. 1. Markup languages

10. XML for Information Management – Day 2 Airi Salminen 10 Example of HTML markup University of Jyväskylä Faculties Humanities Information Technology Social Sciences admin@jyu.fi The element markup describes the structure for WWW publishing. 1. Markup languages

11. XML for Information Management – Day 2 Airi Salminen 11 University of Jyväskylä Faculties Humanities Information Technology Social Sciences admin@jyu.fi The same primary content with markup describing the content of elements by means of XML markup. 1. Markup languages

12. XML for Information Management – Day 2 Airi Salminen 12 1. Markup languages Logical structure of the HTML document html body Faculties University of Jyv ä skyl ä Humanities head admin@cjyu.fi br title h2 ul Social Sciences Information Technology li address Logical structure of the XML document university faculties Faculties University of Jyv ä skyl ä Humanities name admin@cjyu.fi Social Sciences Information Technology faculty contact_email faculty

13. XML for Information Management – Day 2 Airi Salminen 13 2. Structured documents Structured document ‣structure, content, and external presentation can be separated from each other and processed separately ‣structural components have names ‣structural components can be recognized by software modules ‣possible to define the structure

14. XML for Information Management – Day 2 Airi Salminen 14 Structured document Structure Content Layout 2. Structured documents

15. XML for Information Management – Day 2 Airi Salminen 15 Structured document Structure Content Layout 2. Structured documents Examples DTD.txtDTD.dtd rhymes.txtrhymes.xml style.txtstyle.css rhymes with style attachment.xml rhymes with style attachment.txt

16. XML for Information Management – Day 2 Airi Salminen 16 Management of structured documents ‣document management ‣management of the data contained in documents 2. Structured documents

17. XML for Information Management – Day 2 Airi Salminen 17 Traditional document management ‣no schema design ‣processing applied to documents ‣content and layout together Management of structured documents ‣schema design important ‣schemas can be utilized in various ways ‣processing of document parts ‣content, structure, and layout can be processed separately 2. Structured documents

18. XML for Information Management – Day 2 Airi Salminen 18 Database management ‣Database often the information repository of one software system called Database Management System (DBMS), data processed by the operations of the DBMS. ‣Design divided into schema design and view design. ‣Content produced gradually, by the operations of DBMS. ‣Queries are the most important operations. Management of structured documents ‣Different software systems used to manipulate data. ‣Schema design often related to extensive sectoral standard development. ‣Content produced by different kinds of programs, e.g. interactively by structure editors or automatically ‣Transformations most important operations. 2. Structured documents

19. XML for Information Management – Day 2 Airi Salminen 19 Database languages ‣definition languages ‣query languages Structured document languages ‣definition languages ‣style languages ‣various manipulation and transformation languages 2. Structured documents

20. XML for Information Management – Day 2 Airi Salminen 20 3. World Wide Web Consortium ‣W3C developes specifications to support the use of the web, publicly available at http://www.w3.org/TR/http://www.w3.org/TR/ ‣Development is systematic ‣Development process is specified and publishedDevelopment process

21. XML for Information Management – Day 2 Airi Salminen 21 ‣Working Draft: represents work in progress. ‣Candidate Recommendation: has received significant review from its immediate technical community, explicit call for implementation and technical feedback. ‣Proposed Recommendation: represents consensus in the development group, proposed to the Advisory Committee for review. ‣Recommendation: represents consensus within W3C, widespread implementation encouraged. Phases of the development process 3. World Wide Web Consortium

22. XML for Information Management – Day 2 Airi Salminen 22 3. World Wide Web Consortium ‣Remains as a Recommendation indefinitely. ‣W3C rescinds the recommendation. A report called Rescinded Recommendation is published. ‣A new version of the Recommendation is developed. ‣Minor modifications are done. A report called Proposed Edited Recommendation is published. What happens to a W3C Recommendation?