NITF 2009 Spring Working Group

649 views

Published on

Spring 2009 meeting of the NITF maintenance working party.

NITF is the News Industry Text Format - the XML markup for the structure and content of news articles.

Published in: Technology, News & Politics
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
649
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
5
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

NITF 2009 Spring Working Group

  1. 1. NITF Maintenance www.NITF.org Stuart Myles Associated Press Dow Jones Porto / March 1st, 2009
  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>© IPTC – www.iptc.org <ul><li>NITF and </li></ul><ul><ul><li>Adult language </li></ul></ul><ul><ul><li>Redlining </li></ul></ul><ul><ul><li>qcodes </li></ul></ul><ul><ul><li>Conformance levels </li></ul></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><ul><li>Held in Nice, October 2008 </li></ul></ul><ul><ul><li>NM0806.1 </li></ul></ul><ul><ul><li>Thanks to John Iobst for standing in </li></ul></ul>© IPTC – www.iptc.org
  4. 4. NITF Matters <ul><li>Matters arising? </li></ul><ul><ul><li>(I changed jobs) </li></ul></ul>© IPTC – www.iptc.org
  5. 5. Chairman’s Report <ul><li>NITF = “News Industry Text Format” </li></ul><ul><li>Defines the content and structure of articles </li></ul><ul><li>IPTC’s most widely-used XML standard </li></ul><ul><li>428 members on the Y! list, down from 471 in July </li></ul><ul><li>9 emails in Sept and Oct, none since </li></ul><ul><ul><li>7 about bad language </li></ul></ul><ul><ul><li>1 each on redlining and converting XHTML to NITF </li></ul></ul><ul><ul><li>http://www.nitf.org </li></ul></ul><ul><ul><li>http://groups.yahoo.com/group/nitf/ </li></ul></ul>© IPTC – www.iptc.org
  6. 6. Adult Language <ul><li>What is the ****ing problem? </li></ul><ul><li>Some providers want to markup potentially offensive terms </li></ul><ul><li>Suggestions were to use <em> or <classifier>, e.g. </li></ul><ul><ul><li>What the <classifier id=“ap:naughty”>hell</> do I know? by Illinois </li></ul></ul>© IPTC – www.iptc.org
  7. 7. Redlining <ul><li>How to indicate what text has changed? </li></ul><ul><li>Stuart Myles works at Dow Jones </li></ul><ul><li>Stuart Myles works at Dow Jones Associated Press </li></ul><ul><li>Does anyone do this? How? </li></ul>© IPTC – www.iptc.org
  8. 8. 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:AP” </li></ul><ul><li>qcode=“poi:pt:oporto” </li></ul>© IPTC – www.iptc.org
  9. 9. qcodes © IPTC – www.iptc.org In NAR’s PCL text markup: <headline>The <inline qcode=“org:AP”> Associated Press </inline> representative visited <inline qcode=“poi:pt:oporto”> Porto </inline> </headline> In NITF <hl>The <org idsrc=“org” value=“AP”> Associated Press </org> representative visited <city code-src=“poi” city-code=“pt-oporto”> Porto </city> </hl>
  10. 10. qcodes © IPTC – www.iptc.org <ul><li>NAR makes extensive use of qcodes </li></ul><ul><li>Nothing to stop providers using qcode-like values for existing NITF attributes </li></ul><ul><ul><li><org value=“org:AP”> </li></ul></ul><ul><li>Or could add non backward compatible qcode attribute to relevant elements </li></ul><ul><ul><li><city qcode=“poi:pt:oporto”> </li></ul></ul>
  11. 11. qcodes © IPTC – www.iptc.org <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>
  12. 12. qcodes © IPTC – www.iptc.org <newsItem> <inlineRef idrefs=“e1” qcode=“e:happy” confidence=“77”> <name>Happiness</><description>Mirth.</> <inlineRef idrefs=“p7” qcode=“p:buddha”> <name>Gautama Buddha</></inlineRef> … <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… </nitf></newsItem>
  13. 13. Conformance Levels <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>© IPTC – www.iptc.org
  14. 14. Conformance Levels © IPTC – www.iptc.org G2 “ Power” “ Core” Metadata not in NITF G2 expansion of NITF possible Map to G2 No map to G2
  15. 15. Conformance Levels <ul><li>Terms “Core” and “Power” problematic </li></ul><ul><li>Is the idea of conformance levels helpful? </li></ul><ul><li>Are there different views? Such as </li></ul><ul><ul><li>Vendor / developer: different levels of development effort </li></ul></ul><ul><ul><li>User: Reliable interchange at different levels of complexity </li></ul></ul><ul><li>Expressiveness vs. concision or different clusters of users? </li></ul>© IPTC – www.iptc.org
  16. 16. NITF <ul><li>Any other business? </li></ul><ul><li>Date and place of next meeting: </li></ul><ul><li>Seoul, Korea - June 2009 </li></ul><ul><ul><li>Muito obrigado et até mais ! </li></ul></ul>© IPTC – www.iptc.org

×