Challenges of XML Authoring for the Rest of the World - XML Amsterdam 2011


Published on

SDL Xopus presentation for XML Amsterdam 2011. Creating good document models for usability and acceptance of XML authoring

Published in: Technology, News & Politics
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 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
  • Challenges of XML Authoring for the Rest of the World - XML Amsterdam 2011

    1. 1. The Challenges of XMLAuthoring for the Rest of the World Fredrik Geers SDL Structured Authoring
    2. 2. Personal backgroundInformation scienceAutomated publishingStructured content authoring
    3. 3. About SDLGlobal Information ManagementTranslationContent ManagementContent CreationContent Optimization
    4. 4. XML PotentialDo we reach the full potential of XML?
    5. 5. Reasons for choosing XML workflow?Multichannel outputContent reuseControlled structurePersonalization
    6. 6. Product Content Maturity ModelAwareStructureCollaborativeTransformativeEngaging
    7. 7. How to get content into XML?Manual conversionAutomatic conversionDedicated XML editorsFriendly XML editors (SDL Xopus)
    8. 8. Document models
    9. 9. Document model mattersDocument model impacts usabilityEngaging more people in the workflow
    10. 10. ProblemsAmbiguity & Inconsistency Paragraphs in listitemsTag abuse Citation becomes italic
    11. 11. Workflow
    12. 12. Authoring ContentPublishing
    13. 13. What to do with text that is Comic sans,bold and yellow? Authoring Content Publishing
    14. 14. Authoring ContentPublishing
    15. 15. You could still have text in Comic sans, boldand yellow Authoring Content Publishing
    16. 16. Authoring ContentPublishing
    17. 17. What to do with footnotes1 if they are notallowed in your publication? Authoring Content Publishing
    18. 18. Authoring ContentPublishing
    19. 19. 100% valid xml workflowContent model can be used as trustedsource Authoring Content Publishing
    20. 20. What about standards?DITADocBook
    21. 21. Specialize!Thinking about your document model savestimePublishingAuthoring
    22. 22. TipsOnly include elements that are fullysupportedAvoid ambiguityAvoid empty elements
    23. 23. ExampleSpecialized DITA in Xopus
    24. 24. XopusWYSIWYG xml editingBrowser-basedWritten in JavaScriptUses standard W3C technologyAPI for customization
    25. 25. Questions?
    26. 26. We’re hiring!Software engineersComputational linguistsQA engineersProduct managersJunior sales representatives
    27. 27. 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.