IPTC NITF Maintenance June 2010

4,468 views

Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

IPTC NITF Maintenance June 2010

  1. 1. NITF Maintenancehttp://www.nitf.org<br />Stuart Myles<br />Associated Press<br />San Francisco, CA / 28th June 2010<br />
  2. 2. © 2010 IPTC (www.iptc.org) All rights reserved<br />2<br />Agenda<br /><ul><li>Towards NITF 4.0
  3. 3. XSD documentation
  4. 4. Opening up NITF to “foreign” namespaces
  5. 5. Next Steps</li></ul>Approval of minutes from previous meeting<br />Matters Arising<br />Chairman’s Report<br />
  6. 6. NITF Matters<br />Approval of minutes from the previous meeting<br />held on the 8 March 2010 (NM1002.1) <br />Matters arising? <br />© 2010 IPTC (www.iptc.org) All rights reserved<br />3<br />
  7. 7. Chairman’s Report<br />© 2010 IPTC (www.iptc.org) All rights reserved<br />4<br />NITF = “News Industry Text Format”<br />Defines the content and structure of articles<br />418 members on the Y! list<br />Down from 421 in March<br />9 emails since March<br />http://www.nitf.org<br />http://groups.yahoo.com/group/nitf/<br />
  8. 8. Towards NITF 4.0<br />© 2010 IPTC (www.iptc.org) All rights reserved<br />5<br />Open up the schema<br />To give NITF users greater flexibility and control<br />Align NITF with other standards<br />The NITF 4.0 road map:<br />XSD documentation <- Progress to report<br />Namespaces <- Progress to report<br />RDFization <- Now part of a broader IPTC initiative<br />G2ization <- Still to come<br />NITF 4.0 started Spring 2010, target end of 2010<br />Still on track<br />
  9. 9. XSD Documentation<br />Currently, only the NITF 3.5 DTD has documentation<br />An “experimental” NITF XSD with documentation mechanically copied over:<br />http://groups.yahoo.com/group/nitf/files/schema/nitf-3-5.xsd<br />Comments requested, none received…<br />http://groups.yahoo.com/group/nitf/message/772<br />We could update the NITF 3.5 XSD<br />© 2010 IPTC (www.iptc.org) All rights reserved<br />6<br />
  10. 10. NITF + Foreign Namespace e.g. Adding Geo Information<br />© 2010 IPTC (www.iptc.org) All rights reserved<br />7<br />Maps are popular ways to display news<br />It would be handy to be able to use GEORSS to add latitude and longitude information into an NITF article<br />Unfortunately, NITF doesn’t allow “foreign namespaces”<br />
  11. 11. Foreign Namespaces<br />A long-standing criticism of NITF is that it is closed to foreign namespaces<br />e.g. http://snee.com/xml/xml2005/industryschemas.html#d50e406<br />NITF 3.5 added more complete support for foreign namespaces in enriched text – but not yet elsewhere<br />We decided to turn NITF 4.0 into a more open schema<br />An experimental XSD can be found at<br />http://groups.yahoo.com/group/nitf/files/schema/<br />© 2010 IPTC (www.iptc.org) All rights reserved<br />8<br />
  12. 12. Experimenting with Namespaces<br />I constructed an NITF instance document to help figure out where to add namespaces into NITF 4.0<br />It is just an experiment, so I’m sure there are bugs and it is incomplete…<br />© 2010 IPTC (www.iptc.org) All rights reserved<br />9<br />
  13. 13. Testing is Important!<br />The NITF 3.5 XSD foreign namespace support didn’t work as expected<br />I wanted to be able to add some XHTML but couldn’t at first<br />I had to change the processContents style to “lax”<br />© 2010 IPTC (www.iptc.org) All rights reserved<br />10<br />
  14. 14. NITF <head><br />Within the <head> it makes sense to add expansion slots within <docdata> and at the end of <head><br />Everywhere else is already generic (iim, pubdata) or too specific<br />© 2010 IPTC (www.iptc.org) All rights reserved<br />11<br />
  15. 15. NITF <body><br />Added namespaces to <body.head>…<br />© 2010 IPTC (www.iptc.org) All rights reserved<br />12<br />
  16. 16. NITF <body><br />… and within <media> …<br />© 2010 IPTC (www.iptc.org) All rights reserved<br />13<br />
  17. 17. NITF <body><br />… and within <block>.<br />I experimented with namespaces outside of “containers” in the <body> but triggered XSD errors.<br />Also, what would this “mean”?<br />© 2010 IPTC (www.iptc.org) All rights reserved<br />14<br />
  18. 18. After NITF <body>?<br />I allowed foreign namespaces after the body<br />But does this turn NITF into a “envelope” language?<br />Would it compete with NewsML-G2 or ATOM?<br />And I didn’t experiment with anyAttribute<br />Just add anyAttribute to every NITF element?<br />© 2010 IPTC (www.iptc.org) All rights reserved<br />15<br />
  19. 19. NITF 4.0 and IPTC’s G2<br />G2 is a unified framework for packaging and exchanging news content<br />Standard model for news metadata regardless of the content or media type<br />However, NITF predates the G2 framework<br />With work, NITF can join the G2 family, just like SportsML<br />The biggest change will be the inline adoption of QCodes<br />Colon separated scheme:code syntax for controlled vocabularies<br />© 2010 IPTC (www.iptc.org) All rights reserved<br />16<br />
  20. 20. Next Steps towards NITF 4.0<br />Complete the foreign namespace work<br />Add anyAttribute<br />Publish a test document or two<br />G2ization of NITF<br />Publish a test document or two<br />Update the NITF documentation - a long-standing need<br />Could use the NITF chapter of the G2 guidelines<br />That chapter will need updating anyway<br />© 2010 IPTC (www.iptc.org) All rights reserved<br />17<br />
  21. 21. NITF<br />Any other business?<br />Date and place of next meeting:<br />Rome, Italy – November 2010<br />Thanks!<br />© 2010 IPTC (www.iptc.org) All rights reserved<br />18<br />

×