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
The Challenges of XMLAuthoring for the Rest of the World Fredrik Geers SDL Structured Authoring
Personal backgroundInformation scienceAutomated publishingStructured content authoring
About SDLGlobal Information ManagementTranslationContent ManagementContent CreationContent Optimization
XML PotentialDo we reach the full potential of XML?
Reasons for choosing XML workflow?Multichannel outputContent reuseControlled structurePersonalization