NITF 2009 Autumn Working Group


Published on

NITF Working Group presentation at the IPTC 2009 Autumn meeting. NITF is the News Industry Text Format, an XML format for news article content and metadata.

Published in: 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 2009 Autumn Working Group

  1. 1. NITF<br />Stuart Myles<br />Associated Press<br />Washington, DC / October 19th, 2009<br />
  2. 2. © IPTC –<br />2<br />Agenda<br />Approval of minutes from previous meeting<br />Matters Arising<br />Chairman’s Report<br /><ul><li><media-producer>
  3. 3. Media “chunks”
  4. 4. Enriched documentation
  5. 5. Foreign namespaces
  6. 6. NITF 3.5
  7. 7. NITF 4.0
  8. 8. G2ization
  9. 9. RDFization</li></li></ul><li>© IPTC –<br />3<br />NITF Minutes<br />Approval of Minutes from previous meeting:<br />Held on 15th June 2009<br />NM0904.1<br />
  10. 10. © IPTC –<br />4<br />NITF Matters<br />Matters arising?<br />
  11. 11. © IPTC –<br />5<br />Chairman’s Report<br />NITF = “News Industry Text Format”<br />Defines the content and structure of articles<br />IPTC’s most widely-used XML standard<br />435 members on the Y! list, up from 428 in March<br />26 emails since March<br /><br /><br />
  12. 12. &lt;media-producer&gt;<br />REQUEST: allow unlimited &lt;media-producer&gt; elements within the &lt;media&gt; element<br />&lt;media-producer&gt; - “Byline of media producer. Also used as a credit for the media.”<br />Currently, only a single &lt;media-producer&gt; is permitted (whereas &lt;media-caption&gt; may be infinite)<br /><br />© IPTC –<br />6<br />
  13. 13. &lt;media-producer&gt;<br />Proposed structure:<br />© IPTC –<br />7<br />Current structure:<br />Allow zero to many media-producer elements<br />
  14. 14. Media “Chunks”<br />REQUEST: a way to indicate that a large media object (such as a video) is comprised of several &quot;chunks&quot;:<br />After some thought, we decided that this can be conveyed using the existing NITF &lt;media&gt; definition. <br />Therefore, no change is necessary.<br />© IPTC –<br />8<br />
  15. 15. Conveying Media “Chunks”<br />&lt;media&gt; may have many &lt;media-reference&gt;s. Each reference could be to a “chunk”.<br />© IPTC –<br />9<br />&lt;media-metadata&gt; can be used to indicate that the &lt;media-reference&gt;s are “chunks” via@name and @value pairs<br />
  16. 16. &lt;media&gt; ≈ G2 Package<br />Insight – NITF’s &lt;media&gt; is (almost) isomorphic with G2’s package mechanism<br />List of item references, with metadata<br />Lacks “group” mechanism<br />TINNUTS<br />ODF, OOXML, EPUB, W3C Widgets, JAR/WAR/EAR, IDML, etc.<br />© IPTC –<br />10<br />
  17. 17. Enhanced Documentation<br />Started filling out FAQ’s<br />Thanks to John Iobst<br />In the pre conference package<br />More questions (and answers) welcome<br />More documentation updates required<br />Article model, transforms, element examples<br />NITF schema docs date back to 3.2…<br />© IPTC –<br />11<br />
  18. 18. Foreign Namespace<br />In NITF 3.4, support for “foreign namespaces” was introduced into the schema<br />Specifically, the “enriched text” has a choice of<br /> &lt;any namespace=&quot;##other&quot;/&gt;<br />This allows other namespaces to be used within such NITF elements as caption, tagline, etc.<br />© IPTC –<br />12<br />
  19. 19. Foreign Namespace Flaw<br />Unfortunately, two elements (p and hl2) that should be defined as “enriched text” in NITF 3.4 were not<br />This appears to have been an oversight<br />Therefore, I propose to fix their definitions in the schema<br />This has no impact on the DTD<br />But does allow them to include other namespaces<br />© IPTC –<br />13<br />
  20. 20. Foreign Namespaces Elsewhere?<br />So far, we have only allowed non NITF namespaces within enriched text<br />This means that NITF is a “closed” schema<br />Do we want to allow other namespaces to be mixed in with NITF documents?<br />Allow proprietary extensions to be “legal”<br />© IPTC –<br />14<br />
  21. 21. NITF 3.5<br />Allow unlimited &lt;media-producer&gt; elements within the &lt;media&gt; element<br />FAQ’s<br />Fix &lt;p&gt; and &lt;hl2&gt; definitions to be “enriched text” in the schema<br />Vote on a NITF 3.5 version<br />See in the pre-meeting package<br />© IPTC –<br />15<br />
  22. 22. NITF 3.5 Motion<br /><ul><li>MOTION – Standards committee
  23. 23. To adopt NITF v3.5 as specified in the documents in in the pre-meeting package. (Except to keep the NITF namespace as in the previous version)</li></ul>© IPTC –<br />16<br />
  24. 24. NITF 4.0 – G2ization<br />Lots of questions:<br />Can we follow a similar path as SportsML and create an NITF-G2?<br />If so, does NITF “Classic” live on forever?<br />Should &lt;nitf&gt; inherit from the NAR’s AnyItem?<br />How do we introduce qcodes?<br />Introduce qcode into common attributes?<br />Redefine attributes like @value as qcodes?<br />Clearly, we need help from the NARsters<br />© IPTC –<br />17<br />
  25. 25. NITF 4.0 - RDFization<br />There is no official RDF model for news<br />We should create an RDF model for news based on NITF<br />In fact, an RDF model for news is likely based on both NITF and NewsML-G2<br />This may also help with the G2ization of NITF<br />IPTC is the right organization to create a specialized vocabulary<br />© IPTC –<br />18<br />
  26. 26. NITF 4.0 Road Map<br />Kick off NITF 4.0 with a spring working group session<br />Preliminary discussion of<br />G2ization<br />RDFization<br />Namespaces<br />Target NITF 4.0 in one year’s time<br />End of 2010<br />© IPTC –<br />19<br />
  27. 27. NITF<br />Any other business?<br />© IPTC –<br />20<br />
  28. 28. © IPTC –<br />21<br />NITF<br />Date and place of next meeting:<br />Paris, France - Spring 2010<br />Thank You!<br />