1 / 29

Idea in Publishing

Kari Aaltonen. Idea in Publishing. The original data for …. different. Channels. different. Device. different. Content. different. Personilzed. Kari Aaltonen. Concept and challenges. Channels and devices Restrictions and variations Personalization

naif
Download Presentation

Idea in Publishing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Kari Aaltonen Concept and challenges • Channels and devices • Restrictions and variations • Personalization • • 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  Much more than XML only!!!

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

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

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

  6. Kari Aaltonen XML Applications Presentation-oriented publishing (POP) • Structured information is presented on various media (display, paper, mobile…) • document-centric • irreqular structure • for human consumption Message-oriented middleware (MOM) • New client-server architecture • 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. • data-centric • for machine consumption • data transport between systems

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

  8. Kari Aaltonen 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? <p><b>Mr. Matti Möttönen</b> <br> Sivukatu 3 <br> 00011000 Espoo</p> 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. 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.

  9. Kari Aaltonen 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.

  10. Kari Aaltonen 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.

  11. Kari Aaltonen 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 <firstname> elements that contained the text Kake would give you a much better set of results.

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

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

  14. Kari Aaltonen Exact digital replica

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

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

  17. POP Case: Workflow re-engineering

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

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

  20. POP CASE: Network Publishing Tools Mikael Ahlavuo

  21. CASE: XML Databases (MOM)

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

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

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

  25. Heart of XML Application

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

  27. Kari Aaltonen 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)

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

  29. See

More Related