IPTC NITF Maintenance June 2010
•Download as PPTX, PDF•
0 likes•4,009 views
The document summarizes the minutes from a NITF maintenance meeting. It discusses plans to open up the NITF schema to allow for greater flexibility, including adding support for foreign namespaces to allow information like geo coordinates to be included. An experimental version of the NITF XSD was created to demonstrate adding namespace support in different parts of the NITF document format. Next steps include completing the work on foreign namespace support, aligning NITF with the G2 framework for news content exchange, and publishing test documents.
![© 2010 IPTC (www.iptc.org) All rights reserved 2 Agenda ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
Similar to IPTC NITF Maintenance June 2010
Similar to IPTC NITF Maintenance June 2010 (20)
More from Stuart Myles
More from Stuart Myles (20)
Recently uploaded
Recently uploaded (20)
IPTC NITF Maintenance June 2010
- 1. NITF Maintenancehttp://www.nitf.org Stuart Myles Associated Press San Francisco, CA / 28th June 2010
- 4. Opening up NITF to “foreign” namespaces
- 5. Next StepsApproval of minutes from previous meeting Matters Arising Chairman’s Report
- 6. NITF Matters Approval of minutes from the previous meeting held on the 8 March 2010 (NM1002.1) Matters arising? © 2010 IPTC (www.iptc.org) All rights reserved 3
- 7. Chairman’s Report © 2010 IPTC (www.iptc.org) All rights reserved 4 NITF = “News Industry Text Format” Defines the content and structure of articles 418 members on the Y! list Down from 421 in March 9 emails since March http://www.nitf.org http://groups.yahoo.com/group/nitf/
- 8. Towards NITF 4.0 © 2010 IPTC (www.iptc.org) All rights reserved 5 Open up the schema To give NITF users greater flexibility and control Align NITF with other standards The NITF 4.0 road map: XSD documentation <- Progress to report Namespaces <- Progress to report RDFization <- Now part of a broader IPTC initiative G2ization <- Still to come NITF 4.0 started Spring 2010, target end of 2010 Still on track
- 9. 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 We could update the NITF 3.5 XSD © 2010 IPTC (www.iptc.org) All rights reserved 6
- 10. NITF + Foreign Namespace e.g. Adding Geo Information © 2010 IPTC (www.iptc.org) All rights reserved 7 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”
- 11. Foreign Namespaces A long-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/ © 2010 IPTC (www.iptc.org) All rights reserved 8
- 12. Experimenting with Namespaces I constructed an NITF instance document to help figure out where to add namespaces into NITF 4.0 It is just an experiment, so I’m sure there are bugs and it is incomplete… © 2010 IPTC (www.iptc.org) All rights reserved 9
- 13. 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 10
- 14. NITF <head> Within the <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 11
- 15. NITF <body> Added namespaces to <body.head>… © 2010 IPTC (www.iptc.org) All rights reserved 12
- 16. NITF <body> … and within <media> … © 2010 IPTC (www.iptc.org) All rights reserved 13
- 17. 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 14
- 18. After NITF <body>? I allowed foreign namespaces after the body But does this turn NITF into a “envelope” language? Would it compete with NewsML-G2 or ATOM? And I didn’t experiment with anyAttribute Just add anyAttribute to every NITF element? © 2010 IPTC (www.iptc.org) All rights reserved 15
- 19. NITF 4.0 and IPTC’s G2 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 © 2010 IPTC (www.iptc.org) All rights reserved 16
- 20. Next Steps towards NITF 4.0 Complete the foreign namespace work Add anyAttribute Publish a test document or two G2ization of NITF Publish a test document or two Update the NITF documentation - a long-standing need Could use the NITF chapter of the G2 guidelines That chapter will need updating anyway © 2010 IPTC (www.iptc.org) All rights reserved 17
- 21. NITF Any other business? Date and place of next meeting: Rome, Italy – November 2010 Thanks! © 2010 IPTC (www.iptc.org) All rights reserved 18