NITF 2009 Autumn Working Group
Upcoming SlideShare
Loading in...5
×
 

NITF 2009 Autumn Working Group

on

  • 2,367 views

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.

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.

Statistics

Views

Total Views
2,367
Views on SlideShare
2,367
Embed Views
0

Actions

Likes
0
Downloads
3
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    NITF 2009 Autumn Working Group NITF 2009 Autumn Working Group Presentation Transcript

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