1 / 23

Content Model Workstream phase 1

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

viet
Download Presentation

Content Model Workstream phase 1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Content Model Workstreamphase 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. Book structure

  7. XML structure

  8. Selecting content

  9. 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

  10. 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

  11. Introduction to Linked data • 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 • Very simple facts • Thing ... has some property ... value • subject ... predicate ... object • Facts are stored in a database called a triplestore • Ask questions like – what cultural buildings have a nearest tube station of Charing Cross • 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

  12. What facts might be useful to DK? • Facts about real world things • e.g. 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 • 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

  13. 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 • there currently are ontology modules • assembly • asset • attraction • book • content • location • product • transport • travel-product • travel • web • there are extensible controlled vocabularies • book-categories • brands • series • travel-content • travel-themes

  14. The Attractions Module Attraction Built Location Natural Location Event Attraction Activity Attraction Journey Attraction

  15. The Attractions Module Attraction Built Location Natural Location Event Attraction Activity Attraction Journey Attraction Cultural Location Gallery Museum

  16. The Attractions Module Attraction Built Location Natural Location Event Attraction Activity Attraction Journey Attraction Cultural Location Beach Waterfall Gallery Museum

  17. The Attractions Module Attraction Built Location Natural Location Event Attraction Activity Attraction Journey Attraction Cultural Location Beach Waterfall Horse Riding Hiking Gallery Museum

  18. Not limited to one Vocabulary Different people use different vocabularies to describe the same thing • to the geek • AggregateContentObject • to API developer • an article • to the editor • Breakout Box • to the web publisher • a web page Core Content Assembly Web Book RG EWG Content

  19. How is this used in the prototype Gallery Leicester Square Content type National Gallery nearestMetro hasPart subject Content Charing Cross representativePoint title National Gallery lat long 51.50872 -0.12841 Content Embankment Content Metadata Reference Data

  20. Prototype Web Server • wanted an environment for trying things out • before the CMS system is ready • purely experimental • Developer's UI Web API Web API Query content facts XML Database A triple store munge original

  21. Demo

  22. Questions

  23. 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?

More Related