Proposed Changes

Suggested Issues To Discuss At Next NITF Maintenance Meeting

List maintained by Alan Karben. Note that the changes proposed have no guarantee of being approved.
Your comments are welcome.

For NITF 3.3 Why is series allowed in both docdata and body.head? Other potential, small-scale items: * add internal and maintenance to news type? * why is ed-urg rated 1-8? why not 1-10? * does from-src need a src-code for the distributer? * do money and num need a norm attribute? * should we add revision-uno alongside the uno? * why the boolean attributes for element p? Documentation improvements: * make tobject stand for "topic object" rather than "text object" in documentation * make sure that documentation lists all tobject vocabularies (like tobject.property.type) * document a list of suggested "class" values (obituary items, etc.) * explain better the difference between doc-id and UNO * do we need a fixture name in addition to a fixture code? More debatable potential changes: * lose <rights> and <rights.*> elements? * add significance=primary,prominent,passing to all inline codes? * should we lose all the postaddr elements?


Copyright © 2002, International Press Telecommunications Council.