1. Idea in Publishing different The original data for … different different different Channels Device Content Personilzed.... Kari Aaltonen

2. Concept and challenges Channels and devices Channels and devices Restrictions and variationsPersonalization Contents are designed—personalized—on-the-fly for each user or user group based on their preferences. The contents are not the same for all users or business partners.Adaptivity The contents and presentation can "adapt" to the device/display the user has for browsing (also network capacity etc.)Content-awareness Based on user's location, preferences, time, usage history, etc., the user gets the "best-matching" contents and presentation available People do not always want that they are monitored Kari Aaltonen  Much more than XML only!!!

3. Publishing Document-centric Web Browser Client X WAP 1. Clients http:// … evtek.htm Organisation / Application http:// … evtek.wml WAP gateway DB 4. Data Organisation / Application DB How to transform XML from one format into another? Is the document valid? How to parse the file? What does the data mean? How to traverse XML? Services data-centric SOAPSOAP Kari Aaltonen Why XML? 2. User Interfaces3. Business Logic

4. Prognose of XML usage in 2003 ”70% of transactions will use XML in 2003” - Gartner Group Kari Aaltonen ”Today the first apprach in a new project is XML based” - Quartal

5. B2B – B2C – C2B Content reuse (B2C, C2B) publish dynamically to multible channels publish dynamically to multible channels syndication to broader audience syndication to broader audience reuse, redistribute, relicense reuse, redistribute, relicense Data Interchange (B2B) supply chain integration supply chain integration business control and oversight business control and oversight online catalogs and product information online catalogs and product information E-Businesses speed up processes and reduced cost. Content owners must leverage their assets. Kari Aaltonen

6. XML Applications Presentation-oriented publishing (POP) Structured information is presented on various media (display, paper, mobile…) Structured information is presented on various media (display, paper, mobile…) document-centric document-centric irreqular structure irreqular structure for human consumption for human consumption Message-oriented middleware (MOM) New client-server architecture New client-server architecture Middleware software handles the dbase (server) and sends the data in XML to the client. Middleware software handles the dbase (server) and sends the data in XML to the client. Same client can read different dbases as far as data is in XML. Same client can read different dbases as far as data is in XML. data-centric data-centric for machine consumption for machine consumption data transport between systems data transport between systems Kari Aaltonen

7. What is XML? A storage format for word processors, documents and application objects A storage format for word processors, documents and application objects  purchase orders … Self describing data interchange format for B2B infrastructure Self describing data interchange format for B2B infrastructure  may replace EDI as B2B exchange format Used to store application meta data Used to store application meta data Provides Enterprise Application Integration Provides Enterprise Application Integration  (EAI) Intechange of data between non integrated applications Open distributed application protocol Open distributed application protocol  SOAP Standard developed by W3C Standard developed by W3C Kari Aaltonen Standard Free extensable Human readable Machine comprehensible

8. Why do we need XML HTML is the most successful markup language. You can view the simplest HTML tags on virtually any device, from palmtops to mainframes, and you can even convert HTML markup into voice and other formats with the right tools. Given the success of HTML, why did the W3C create XML? Mr. Matti Möttönen Sivukatu 3 00011000 Espoo The trouble with HTML is that it was designed with humans in mind. Even without viewing the above HTML document in a browser, one can figure out that it is someone's address. You and I know it's an address, but a machine doesn't. As humans, you and I have the intelligence to understand the meaning and intent of most documents. A machine, unfortunately, can't do that. While the tags in this document tell a browser how to display this information, the tags don't tell the browser what the information is. You and I know it's an address, but a machine doesn't. Kari Aaltonen

9. XML simplifies data interchange Because different organizations (or even different parts of the same organization) rarely standardize on a single set of tools, it can take a significant amount of work for applications to communicate. Using XML, each group creates a single utility that transforms their internal data formats into XML and vice versa. Best of all, there's a good chance that their software vendors already provide tools to transform their database records (or LDAP directories, or purchase orders, and so forth) to and from XML. Kari Aaltonen

10. XML enables smart code Because XML documents can be structured to identify every important piece of information (as well as the relationships between the pieces), it's possible to write code that can process those XML documents without human intervention. The fact that software vendors have spent massive amounts of time and money building XML development tools means writing that code is a relatively simple process. Kari Aaltonen

11. XML enables smart searches Although search engines have improved steadily over the years, it's still quite common to get erroneous results from a search. If you're searching HTML pages for someone named "Kake," you might also find pages on chocolate chips, computer chips, wood chips, and lots of other useless matches. Searching XML documents for elements that contained the text Kake would give you a much better set of results. Kari Aaltonen

12. XML makes more metadata Semantic Web: metadata and intelligence to the Web Metadata Metadata like RDF (Resource Description Framework) to better describe the contents and relationships of your data. Kari Aaltonen

13. Presentation-oriented publishing (Case POP) ref Pira Digital Demand editorial pagination post- processing email browser media phone digi –TV SERVER SERVICE planning digital printing textpictvoice asset management system multichannel communication between customers/editorial subcribes/printing advertisement selling circulation selling attachments advertise- ments video CTP Kari Aaltonen

14. Exact digital replica Kari Aaltonen

15. Message-oriented middleware (Case MOM) Kari Aaltonen

16. What ever is needed – Can You Do It with XML? Kari Aaltonen

17. POP Case: Workflow re-engineering

18. POP CASE: Content Management www.quartal.com Olli Pietilä

19. On-line Business processes between: Human-to-human System-to-human/human-to-system (WEB) System-to-system (RosettaNet) NOKIA SUPPLIER Millions of components every hour MOM CASE: Integrated Business Processes Conducted On-Line Barbara Heikkinen

20. POP CASE: Network Publishing Tools Mikael Ahlavuo

21. CASE: XML Databases (MOM)

22. MOM CASE: XML db and Java Devendra Yasothai (thesis) Development of NetPro Reuse Tools - XML Database and Search Tool - for Collaborative Project Learning

23. POP CASE: XML and Multichannel Publishing Project Juha Nieminen

24. Applying XML… 1. Application environment/programs should use xml? database 2. Use XML database? XML editors Files 3. Group editing facilities. Local 5. Know the channel and device XSL editors editor designer 6. Hide XML, develope the process. Engineer import export 4. Content management.

25. Heart of XML Application

26. Open Source Publishing System COCOON XSLT Processor (e.g. Xalan) Stylesheets Stylesheet A Java servlet (e.g. XML Enabler) Web server Client A Client B Client C Client X http Req.http Request XML Document XSL XSL + XML HTML Doc Kari Aaltonen

27. Open source development Apache XML Project currently consists of the following sub- projects, each focused on a different aspect of XML: Xerces - XML parsers in Java, C++ (with Perl and COM bindings) Xalan - XSLT stylesheet processors, in Java and C++ Cocoon - XML-based web publishing, in Java AxKit - XML-based web publishing, in mod_perl FOP - XSL formatting objects, in Java Forrest - Cross-project Documentation and Website Infrastructure Xang - Rapid development of dynamic server pages, in JavaScript SOAP - Simple Object Access Protocol Batik - A Java based toolkit for Scalable Vector Graphics (SVG) Kari Aaltonen

28. Linux server J2EE Kari Aaltonen LINUX 9.3 Apache 2.2 Java Virtual Machine 1.5 Tomcat 5.5.8 http sessions JSP Servlets port 8080 port 80 html JBOSS 2.4+ Enterprise Java Beans eXist Native xml database Xalan XLST processor 1.8 Xerces parser 2.6 Cocoon 2

29. See