NITF Working Group October 2007


Published on

IPTC's NITF is the XML standard for marking up news articles. These slides are from the October meeting of the NITF Working Group.

Published in: Business, Technology
  • 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

NITF Working Group October 2007

  1. 1. NITF Maintenance “All news is an exaggeration of life.” - Daniel Schorr, CBS News Stuart Myles Alan Karben Dow Jones XML Team Solutions Prague / October 17, 2007
  2. 2. Agenda <ul><li>Approval of minutes from previous meeting </li></ul><ul><li>Matters Arising </li></ul><ul><li>Chairman’s Report </li></ul><ul><li>State of NITF Today </li></ul><ul><li>NITF 4.0 </li></ul><ul><li>Future of NITF </li></ul><ul><li>Other business </li></ul><ul><li>The next meeting </li></ul>
  3. 3. NITF Minutes <ul><li>Approval of Minutes from previous meeting: </li></ul><ul><li>Tokyo 30th May 2007 </li></ul><ul><li>NM0704.1 </li></ul>
  4. 4. NITF Matters <ul><li>Matters arising? </li></ul><ul><li>I took over! </li></ul><ul><li>Děkuji to Alan Karben. </li></ul>
  5. 5. State of NITF Today <ul><li>News Industry Text Format </li></ul><ul><li>“ A solution for sharing news” </li></ul><ul><li>Developed by News Publishers, for News Publishers </li></ul><ul><li>Defines the content and structure of news articles </li></ul><ul><li>NITF v3.4 in DTD and XML Schema </li></ul><ul><li>http://www. nitf .org </li></ul>
  6. 6. State of NITF Today <ul><li>IPTC’s most widely-used XML standard </li></ul><ul><ul><li>455 members on the Y! list </li></ul></ul><ul><ul><li>Since June, 9 subscribed, 4 unsubs </li></ul></ul><ul><li>Recent history </li></ul><ul><ul><li>NITF largely the same since 90’s </li></ul></ul><ul><ul><li>Consolidation: removed HTML formats, streamlined enriched text, etc. </li></ul></ul><ul><ul><li>XML schema </li></ul></ul><ul><li>Stability </li></ul>
  7. 7. State of NITF Today <ul><li>Some activity </li></ul><ul><ul><li>Only 27 Y! messages since June </li></ul></ul><ul><ul><li>No one responded to NITF profiles or contributed to the G2 map </li></ul></ul><ul><li>Emerging Alternatives </li></ul><ul><ul><li>XHTML, Microformats, RDFa, PRISM, etc. </li></ul></ul><ul><li>NITF is strong, but with looming challenges </li></ul>
  8. 8. NITF 4.0 <ul><li>NITF Profiles: Core </li></ul><ul><ul><li>Inline and structural markup </li></ul></ul><ul><ul><li>No metadata that conflicts with G2 </li></ul></ul><ul><ul><li>Slimmed-down set of NITF elements </li></ul></ul><ul><ul><li>http: //tinyurl . com/ywzawr </li></ul></ul><ul><li>NITF Profiles: Power </li></ul><ul><ul><li>Map Power metadata to G2 metadata </li></ul></ul><ul><ul><li>http: //tinyurl .com/2rgfx6 </li></ul></ul>
  9. 9. NITF 4.0: Core, Power, G2 G2 Power Core Metadata not in NITF G2 expansion of NITF possible Map to G2 No map to G2
  10. 10. Core Conceptual Model <ul><li>Containers : </li></ul><ul><li>paragraph </li></ul><ul><li>sub-headline </li></ul><ul><li>table </li></ul><ul><li>media </li></ul><ul><li>list </li></ul><ul><li>sidebar </li></ul><ul><li>preformatted block </li></ul><ul><li>editorial note </li></ul><ul><li>Closers : </li></ul><ul><li>credit-line </li></ul><ul><li>biographical blurb </li></ul><ul><li>Many Containers hold Enriched Text : </li></ul><ul><ul><li>phrases (people, titles, etc) </li></ul></ul><ul><ul><li>highlights (stylistic emphasis) </li></ul></ul><ul><ul><li>link </li></ul></ul><ul><ul><li>break </li></ul></ul>article abstract headline super-headline sub-headline main-headline byline Containers Closer G2 main-headline byline phrases link
  11. 11. NITF Power Model nitf head title body Most NITF <head> elements and attributes map to G2 (or make no sense) Notable exceptions are <iim> <pubdata> and <revision-history> Map details at http: //tinyurl .com/2rgfx6 meta tobject iim docdata pubdata revision-history iim pubdata revision-history
  12. 12. NITF G2: Embedded Media <ul><li>NITF articles often embed a media item, e.g. image, audio, video, etc </li></ul><ul><li>The media item often has associated metadata, e.g. copyright, mime-type, height, width, etc. </li></ul><ul><li>When switching to NITF+G2, what do you do with the media item and its metadata? </li></ul>media body.content nitf media-metadata media-reference media-caption
  13. 13. NITF G2: Embedded Media <ul><li>It depends. </li></ul>
  14. 14. NITF G2: Embedded Media <ul><li>Three options: </li></ul><ul><ul><li>Create an item for the media object and use packageItem to glue the NITF article and media object together </li></ul></ul><ul><ul><li>Use links in the item header to reference media objects needed for the item to display correctly </li></ul></ul><ul><ul><li>Embed the media object in the NITF article </li></ul></ul>
  15. 15. NITF G2: Embedded Media <ul><ul><li>Create an item for the media object and use packageItem to glue the NITF article and media object together </li></ul></ul>newsMessage itemSet packageItem newsItem newsItem nitf media
  16. 16. NITF G2: Embedded Media <ul><ul><li>Use a link in the item header to reference the media object </li></ul></ul><ul><ul><li>(e.g. a graphic / audio / video on the web). </li></ul></ul>newsMessage newsItem nitf media link
  17. 17. NITF G2: Embedded Media <ul><ul><li>Embed the media object in the NITF article </li></ul></ul><ul><ul><li>Provide context </li></ul></ul><ul><ul><li>Exact placement </li></ul></ul><ul><ul><li>Specific order </li></ul></ul><ul><ul><li>Captions often specific to the article </li></ul></ul>media body.content nitf media-reference newsItem media-caption link
  18. 18. NITF G2 <ul><li>The choices with embedded media illustrate a general conclusion </li></ul><ul><li>When using NITF within NewsML-G2 there will be a number of choices that news publishers need to make </li></ul><ul><li>How much to embrace the “G2 Way”? </li></ul>
  19. 19. NITF G2: qcodes <ul><li>The NAR makes extensive use of qcodes </li></ul><ul><li>Should NITF adopt qcodes too? </li></ul><ul><li>qcodes are “qualified codes” </li></ul><ul><li>Scheme identifier followed by a colon followed by a code (which can contain a colon), e.g. </li></ul><ul><li>qcode=“org:DJ” </li></ul><ul><li>qcode=“poi:cz:praha” </li></ul>
  20. 20. NITF G2: qcodes <ul><li>In NAR’s PCL text markup: </li></ul><ul><li><headline>The </li></ul><ul><li><inline qcode=“org:DJ”> </li></ul><ul><li>Dow Jones </inline> representative visited <inline qcode=“poi:cz:praha”> </li></ul><ul><li>Prague </li></ul><ul><li></inline> </li></ul><ul><li></headline> </li></ul>In NITF <hl>The <org idsrc=“org” value=“DJ”> Dow Jones </org> representative visited <city code-src=“poi” city-code=“cz:praha”> Prague </city> </hl>
  21. 21. NITF G2: qcodes <ul><li>NAR provides powerful metadata capabilities using qcodes </li></ul><ul><ul><li>Hooks into conceptItem (path to ontology) </li></ul></ul><ul><ul><li>Ambiguous assertions of identity </li></ul></ul><ul><li>Nothing to stop providers using qcode-like values for existing NITF attributes </li></ul><ul><ul><li><org value=“org:DJ”> </li></ul></ul><ul><li>Or could add non backward compatible qcode attribute to relevant elements </li></ul><ul><ul><li><city qcode=“poi:cz:praha”> </li></ul></ul>
  22. 22. NITF G2: qcodes <ul><li>Proposal : Do not add qcodes to NITF. </li></ul><ul><li>Instead, use NAR’s inlineRef and NITF’s id. </li></ul><ul><li>NAR’s <inlineRef> mechanism allows qcodes to be applied to any element that sports an XML id attribute </li></ul><ul><li>All NITF elements support id </li></ul><ul><li>Including the useful “catchall” <classifier> </li></ul>
  23. 23. NITF G2: qcodes example <ul><li><newsItem> </li></ul><ul><li><inlineRef idrefs=“e1” qcode=“e:happy” confidence=“77”> </li></ul><ul><li><name>Happiness</><description>Mirth.</> </li></ul><ul><li><inlineRef idrefs=“p7” qcode=“p:buddha”> </li></ul><ul><li><name>Gautama Buddha</></inlineRef> </li></ul><ul><li>… </li></ul><ul><li><nitf><person id=“p7”>Buddha</> discussed the role of the mind in the pursuit of <classifier id=“e1”>happiness</> through the practice of the eightfold path… </li></ul><ul><li></nitf></newsItem> </li></ul>
  24. 24. NITF 4.0: Next Steps <ul><li>Re-solicit comments on Yahoo groups </li></ul><ul><li>Resolve and harmonize discussion points </li></ul><ul><li>Draft an NITF-in-G2 User Guide </li></ul><ul><li>Vote on NITF 4.0 Proposal in Beijing </li></ul>
  25. 25. NITF Future <ul><li>Stability </li></ul><ul><ul><li>Few changes recently </li></ul></ul><ul><ul><li>Not even to integrate with NewsML-G2 </li></ul></ul><ul><li>Requests </li></ul><ul><ul><li>Inline markup </li></ul></ul><ul><ul><li>More complex and richer </li></ul></ul><ul><ul><li>Inspired by microformats, XHTML </li></ul></ul>
  26. 26. NITF Future: Drive Adoption <ul><li>Text article model is close to universal </li></ul><ul><li>And yet it is being re-invented: </li></ul><ul><ul><li>PRISM, microformats, RDFa, XHTML, etc. </li></ul></ul><ul><li>This hurts interoperability and therefore competition and costs </li></ul>article abstract headline super-headline sub-headline main-headline byline Containers Closer
  27. 27. NITF Future: Drive Adoption <ul><li>What is the best way to drive adoption? </li></ul><ul><li>We could promote the NITF format </li></ul><ul><ul><li>Evangelize the NITF tags amongst publishers of other kinds </li></ul></ul><ul><ul><li>Adopt more and more of the complex markup of XHTML </li></ul></ul><ul><li>We could promote the common article model </li></ul><ul><ul><li>Map from the model to XHTML, RDFA, etc. </li></ul></ul><ul><ul><li>De-emphasize the NITF tags themselves </li></ul></ul>
  28. 28. NITF Future: Drive Adoption <ul><li>In my view, the best way to drive adoption is to do a combination of the two </li></ul><ul><li>We should create an explicit article model (similar to the NAR) </li></ul><ul><li>We would then create maps from the article model to various formats </li></ul><ul><li>The IPTC would declare support for NITF as “first among equals” </li></ul>
  29. 29. NITF <ul><li>Any other business? </li></ul><ul><li>Date and place of next meeting: </li></ul><ul><ul><li>Beijing, China Spring 2008 </li></ul></ul><ul><ul><li>Děkuji! </li></ul></ul>