Download to read offline
Uploaded byStuart Myles
Nitf 2010-11
The document discusses plans to update the News Industry Text Format (NITF) schema to version 4.0. Key points include: 1) NITF 4.0 will make the schema more flexible and open by allowing "foreign namespaces" to integrate other standards like geospatial data. 2) An experimental NITF 4.0 XSD adds documentation and allows namespaces in elements like <head>, <body.head>, and <media>. 3) Feedback is requested on the experimental schema before finalizing NITF 4.0 by the end of 2010. Integration with the NewsML-G2 framework may come later.
More Related Content
More from Stuart Myles
Nitf 2010-11
- 1. NITF 4.0 http://www.nitf.org Stuart Myles AssociatedPress Rome / 3rd November 2010
- 2. NITF © 2010 IPTC(www.iptc.org) All rights reserved 2 • News Industry Text Format • “A solution for sharing news” • Developed by News Publishers, for News Publishers • Defines the content and structure of news articles • Currently, NITF v3.5 in DTD and XSD http://www.nitf.org http://groups.yahoo.com/group/nitf/
- 3. Towards NITF 4.0 ©2010 IPTC (www.iptc.org) All rights reserved 3 • Open up the schema – To give NITF users greater flexibility and control – Align NITF with other standards • The original NITF 4.0 road map: – XSD documentation <- Progress to report – Namespaces <- Progress to report – RDFization <- Now part of a broader IPTC initiative – G2ization <- No progress • NITF 4.0 started Spring 2010, target end of 2010
- 4. XSD Documentation • Currently,only the NITF 3.5 DTD has documentation • An “experimental” NITF XSD with documentation mechanically copied over: http://groups.yahoo.com/group/nitf/files/schema/nitf-3-5.xsd • Comments requested, none received… http://groups.yahoo.com/group/nitf/message/772 © 2010 IPTC (www.iptc.org) All rights reserved 4
- 5. NITF + ForeignNamespace e.g. Adding Geo Information © 2010 IPTC (www.iptc.org) All rights reserved 5 • Maps are popular ways to display news • It would be handy to be able to use GEORSS to add latitude and longitude information into an NITF article • Unfortunately, NITF doesn’t allow “foreign namespaces”
- 6. Foreign Namespaces • Along-standing criticism of NITF is that it is closed to foreign namespaces e.g. http://snee.com/xml/xml2005/industryschemas.html#d50e406 • NITF 3.5 added more complete support for foreign namespaces in enriched text – but not yet elsewhere • We decided to turn NITF 4.0 into a more open schema • An experimental XSD can be found at http://groups.yahoo.com/group/nitf/files/schema/ http://www.iptc.org/std-dev/NITF/4.0/ © 2010 IPTC (www.iptc.org) All rights reserved 6
- 7. Experimenting with Namespaces Iconstructed some NITF instance documents to help figure out where to add namespaces into NITF 4.0 © 2010 IPTC (www.iptc.org) All rights reserved 7
- 8. Testing is Important! •The NITF 3.5 XSD foreign namespace support didn’t work as expected • I wanted to be able to add some XHTML but couldn’t at first • I had to change the processContents style to “lax” © 2010 IPTC (www.iptc.org) All rights reserved 8
- 9. NITF <head> • Withinthe <head> it makes sense to add expansion slots within <docdata> and at the end of <head> • Everywhere else is already generic (iim, pubdata) or too specific © 2010 IPTC (www.iptc.org) All rights reserved 9
- 10. NITF <body> • Addednamespaces to <body.head>… © 2010 IPTC (www.iptc.org) All rights reserved 10
- 11. NITF <body> • …and within <media> … © 2010 IPTC (www.iptc.org) All rights reserved 11
- 12. NITF <body> • …and within <block>. • I experimented with namespaces outside of “containers” in the <body> but triggered XSD errors. • Also, what would this “mean”? © 2010 IPTC (www.iptc.org) All rights reserved 12
- 13. After NITF <body>? •I allowed foreign namespaces after the body • This would turn NITF into a “envelope” language • Other languages (ATOM, NewsML-G2) sport this model – Could be useful as a general-purpose expansion – Perhaps as a way to carry additional metadata such as codes © 2010 IPTC (www.iptc.org) All rights reserved 13
- 14. NITF Attributes • Iadded foreign namespace attributes to the commonNITFAttributes group • Used in many – but far from all - NITF elements © 2010 IPTC (www.iptc.org) All rights reserved 14 • Adding foreign namespace attributes to the globalNITFAttributes group would cover the rest of the NITF elements
- 15. NITF and IPTC’sG2 • G2 is a unified framework for packaging and exchanging news content • Standard model for news metadata regardless of the content or media type • However, NITF predates the G2 framework • With work, NITF can join the G2 family, just like SportsML • The biggest change will be the inline adoption of QCodes – Colon separated scheme:code syntax for controlled vocabularies • Proposal: proceed with NITF 4.0 without G2 support, to avoid delay – G2 support is too big to rush © 2010 IPTC (www.iptc.org) All rights reserved 15
- 16. NITF 4.0 • Theexperimental NITF 4.0 schema and a couple of example documents were distributed to the NITF Yahoo! email list for comment and are available at http://www.iptc.org/std-dev/NITF/4.0/ • After the deadline for submitting documents to this meeting, I got a little feedback, asking for additions – What is the formal procedure? Can we vote and make changes? • NITF v 3.4 started the move to XML Schema in 2007 • Adding documentation and opening up to “foreign namespaces” completes the transition to XML Schema © 2010 IPTC (www.iptc.org) All rights reserved 16
- 17. NITF Any other business? Dateand place of next meeting: Spring 2011 Grazie! © 2010 IPTC (www.iptc.org) All rights reserved 17