Challenges of XML Authoring for the Rest of the World - XML Amsterdam 2011
•
0 likes•371 views
SDL Xopus presentation for XML Amsterdam 2011. Creating good document models for usability and acceptance of XML authoring
Recommended
Recommended
More Related Content
Similar to Challenges of XML Authoring for the Rest of the World - XML Amsterdam 2011
Similar to Challenges of XML Authoring for the Rest of the World - XML Amsterdam 2011 (20)
Recently uploaded
Recently uploaded (20)
Challenges of XML Authoring for the Rest of the World - XML Amsterdam 2011
- 2. The Challenges of XML Authoring for the Rest of the World Fredrik Geers SDL Structured Authoring
- 3. Personal background Information science Automated publishing Structured content authoring
- 4. About SDL Global Information Management Translation Content Management Content Creation Content Optimization
- 5. XML Potential Do we reach the full potential of XML?
- 6. Reasons for choosing XML workflow? Multichannel output Content reuse Controlled structure Personalization
- 7. Product Content Maturity Model Aware Structure Collaborative Transformative Engaging
- 8. How to get content into XML? Manual conversion Automatic conversion Dedicated XML editors Friendly XML editors (SDL Xopus)
- 10. Document model matters Document model impacts usability Engaging more people in the workflow
- 11. Problems Ambiguity & Inconsistency Paragraphs in listitems Tag abuse Citation becomes italic
- 12. Workflow
- 14. What to do with text that is Comic sans, bold and yellow? Authoring Content Publishing
- 16. You could still have text in Comic sans, bold and yellow Authoring Content Publishing
- 18. What to do with footnotes1 if they are not allowed in your publication? Authoring Content Publishing
- 20. 100% valid xml workflow Content model can be used as trusted source Authoring Content Publishing
- 22. Specialize! Thinking about your document model saves time Publishing Authoring
- 23. Tips Only include elements that are fully supported Avoid ambiguity Avoid empty elements
- 24. Example Specialized DITA in Xopus
- 25. Xopus WYSIWYG xml editing Browser-based Written in JavaScript Uses standard W3C technology API for customization
- 28. Questions?
- 29. We’re hiring! Software engineers Computational linguists QA engineers Product managers Junior sales representatives
- 30. www.sdl.com Copyright © 2008-2010 SDL plc. All rights reserved. All company names, brand names, trademarks, service marks, images and logos are the property of their respective owners. This presentation and its content are SDL confidential unless otherwise specified, and may not be copied, used or distributed except as authorised by SDL.
Editor's Notes
- Or DTD, XML Schema, Relax NG, Schematron
- Usability is affected no matter what tool is usedSome more than others – weird tag names hurt more in dedicated xml editors than in editors like XopusToo many elements is troublesome for all methods of getting to XMLMatters a lot if you want to get more people into the XML workflowUsability barriers hinder acceptance and adoption of new workflowimportant when your goal is engaging more people to the processissues can be solved with training where you have little authors, introducing more people this becomes harder
- Too much freedom in document model -> ambiguityAmbiguity -> inconsistencyNot clear what element to pick for your content -> tag abusePeople are inventive if a system doesn’t suit them
- Workflow from content authoring to publishing
- Common workflow without XML authoringAuthor has full freedom, different authors will make different decisionsContent model constrains freedomStrict rules for Publication
- Converting to a smaller set is painful:Loss of information / Manual choicesConversion -> More (tedious) work, less control. Information lost.
- Make everything broad is not the answer: a lot of work, you end up building Word.No conscious decision, evolved to this in the course of yearsWord can save as XML right?
- Too much effort building elements you’ll never needNo control over content
- XML editor: Authoring is never broader than contentIncreased control over contentIs it supported by publishing?Author still has too much freedom
- Too much freedom = not enough guidance
- Complete workflow uses same document modelModel is 100% supported through all stepsAll semantic elements have a representation in publishingModel is used as a tool to communicate what is expected from the author
- Both lots of elementsGood for:InteroperabilityUsing standard tools
- Publishing: do I need to write a stylesheet for this? Is it ever used?Authoring: can I use this element? Is is taken care for in the publishingStart small – add laterAdding elements is easier than removing them
- Only one way to describe a semantic elementHaving a list without listitems