Workflow A quick summary of how the new technologies map to the DK Workflow

Planning Define the product conceptually and query the Triple Store to find relevant content, for example in “Spain for Heavy Drinkers” we’d need to search for POIs like bar, pub and that are situated in Spain Here be the tricky part of mapping from a free-form Triple store graph representation to a product plan(s)

Authoring Use tools that hide XML and use templates/pre-validation to standardise content (see RDF doc) Encourage editors to add rich meta Linked Data will allow redundancy, for example bar and pub but always try to simplify and suggest existing values

Mapping to RDF Use xml:id to link XML content fragments to statements in RDF xml:id=”RG_SPAIN652BARGOT_001 bjects#

Granularity For simplicity Content Objects such as POI that Linked Data will talk about should map to docbook/DITA topics or XHTML5 documents with section/article fragments Can use fragment identifiers in rare cases it still means managing a lot

Reuse: recommended One instance for each Content Object Use conditional profiling on the Object to filter out changes migrate automatically to relevant products needs extra notification and training for Editors

Reuse: alternative Maintain abstract Object that has up-to date info When writing about it manually check correctness and update one or both use secondary ID/IDREF or SemTech to link all related Objects safer but not too advantegous

Editorial: comments and change tracking Use XML Processing Instructions (PIs) to mark comments and change tracking in XML Use Oxygen or compatible convention for simplicity and tools support After each revision create a new version (only keep Pis for the current step)