SlideServe
Menu
Préférences
© SlideServe · v2026

content model workstream

diza avatar
22 diapositives · 392 Views · Jul 12, 2014

content model workstream. phase 1. Business transformation goals. Efficient content updating and publishing New business opportunities enabled Efficient location of internal content Fine-grained business analytics. Phases of the content modelling workstream. phase 1: creating the model

content model workstream - slide 1
01 / 22content model workstream
1 / 17

Télécharger la présentation

content model workstream
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation
  1. content model workstream phase 1

  2. Business transformation goals • Efficient content updating and publishing • New business opportunities enabled • Efficient location of internal content • Fine-grained business analytics

  3. Phases of the content modelling workstream phase 1: creating the model phase 2: testing and refining the model phase 3: handing over the model to DK phase 4: migrating content to the new model

  4. Phase 1 deliverables A model of how DK content can be structured as content objects Ontologies, which support content search and reuse A prototype to demonstrate content objects and ontologies

  5. What are content objects? Reusable "chunks" of meaningful content, which can be combined to created products

  6. DocBook Assembly DocBook’s method for topic-based authoring. • Can be chunked at any level (whole chapter or a paragraph) • Can be transformed from or to a traditional book structure

  7. DocBook Toolkit • Out-of-the-box production of PDF, HTML, EPUB, slides etc (good for proofing) • Excellent tools support (Oxygen XML) • Fully customizable - can layer own XSL on top • Disassemble existing DK-Schema books using standard XSL

  8. Introduction to linked data

  9. Linked data is about facts • Fact: The national gallery is an art gallery • Fact: The national gallery is in Trafalgar Square • Fact: Trafalgar Square's nearest tube is Charing Cross

  10. Very simple facts Thing ... has some property ... value subject ... predicate ... object

  11. Facts are stored in a data-base called a triplestore Ask questions like – what cultural buildings have a nearest tube station of Charing Cross?

  12. Linked data uses the web • http://sparql.kode1100.com/id/geonames/6944334 • http://sparql.kode1100.com/id/station/westminster Linked data stores are schema-less Got a new fact – just dump it in the store

  13. What facts might be useful to DK?

  14. Facts about real-world things • For example, the National Gallery - type, nearest tube, lat/long, wheelchair - access, opening times, tours, events... • Usually called "reference data" • Store them once – accessible to all titles and products

  15. Facts about content • this content object is about the national gallery, was written by ..., uses this image ..., which was taken by ..., which is rights cleared for the UK, is on page ... of the 2012 edition of the RG to London

  16. Facts need a vocabulary That's what the ontology is • A vocabulary for writing down facts • The ontology is divided into a number of separate modules

  17. There are currently ontology modules assembly asset attraction book content location product transport travel-product travel web

  18. There are extensible controlled vocabularies book-categories brands series travel-content travel-themes

  19. Demonstration

  20. Meeting the business transformation goals • Efficient content updating and publishing- Moving towards a "create once, publish everywhere" strategy, by separating content, structure, meaning and presentation • New business opportunities enabled- Leverage other sources of data - Increased brand awareness

  21. Meeting the business transformation goals • Efficient location of internal content- Use linked data to deeply query our content - Quickly respond to question like "how muchcontent is there about hotels in Paris?" • Fine-grained business analytics - Find out how content is performing at theobject level - Could inform commissioning/ editorialdecisions

  22. Next steps Requirements from February 18th • what does the content model need to do? Phase 2 throughout March • Creating products from content objects • Searching for content objects • Modelling more domains Phase 3 beginning in April? • Handover to DK Migration beginning in April?