NITF 2009 Spring Working Group
-
Upload
stuart-myles -
Category
Technology
-
view
1.280 -
download
1
description
Transcript of NITF 2009 Spring Working Group
![Page 1: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/1.jpg)
NITF Maintenance www.NITF.org
Stuart MylesAssociated Press
Dow Jones
Porto / March 1st, 2009
![Page 2: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/2.jpg)
© IPTC – www.iptc.org 2
Agenda• Approval of minutes
from previous meeting
• Matters Arising
• Chairman’s Report
• NITF and– Adult language– Redlining– qcodes– Conformance levels
• Other business
• The next meeting
![Page 3: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/3.jpg)
© IPTC – www.iptc.org 3
NITF Minutes
• Approval of Minutes from previous meeting:– Held in Nice, October 2008– NM0806.1
– Thanks to John Iobst for standing in
![Page 4: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/4.jpg)
© IPTC – www.iptc.org 4
NITF Matters
• Matters arising?– (I changed jobs)
![Page 5: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/5.jpg)
© IPTC – www.iptc.org 5
Chairman’s Report• NITF = “News Industry Text Format”
• Defines the content and structure of articles• IPTC’s most widely-used XML standard• 428 members on the Y! list, down from 471 in July• 9 emails in Sept and Oct, none since
– 7 about bad language– 1 each on redlining and converting XHTML to NITF
http://www.nitf.org
http://groups.yahoo.com/group/nitf/
![Page 6: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/6.jpg)
Adult Language
• What is the ****ing problem?
• Some providers want to markup potentially offensive terms
• Suggestions were to use <em> or <classifier>, e.g.– What the <classifier id=“ap:naughty”>hell</>
do I know? by Illinois
© IPTC – www.iptc.org 6
![Page 7: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/7.jpg)
Redlining
• How to indicate what text has changed?
Stuart Myles works at Dow Jones
Stuart Myles works at Dow Jones Associated Press
• Does anyone do this? How?
© IPTC – www.iptc.org 7
![Page 8: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/8.jpg)
qcodes
© IPTC – www.iptc.org 8
• The NAR makes extensive use of qcodes
• Should NITF adopt qcodes too?
• qcodes are “qualified codes”
• Scheme identifier followed by a colon followed by a code (which can contain a colon), e.g.
qcode=“org:AP”
qcode=“poi:pt:oporto”
![Page 9: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/9.jpg)
qcodes
© IPTC – www.iptc.org 9
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>
![Page 10: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/10.jpg)
qcodes
© IPTC – www.iptc.org 10
• NAR makes extensive use of qcodes• Nothing to stop providers using qcode-like
values for existing NITF attributes<org value=“org:AP”>
• Or could add non backward compatible qcode attribute to relevant elements<city qcode=“poi:pt:oporto”>
![Page 11: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/11.jpg)
qcodes
© IPTC – www.iptc.org 11
• Proposal: Do not add qcodes to NITF.Instead, use NAR’s inlineRef and NITF’s id.
• NAR’s <inlineRef> mechanism allows qcodes to be applied to any element that sports an XML id attribute
• All NITF elements support id• Including the useful “catchall” <classifier>
![Page 12: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/12.jpg)
qcodes
© IPTC – www.iptc.org 12
<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>
![Page 13: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/13.jpg)
Conformance Levels
• NITF Profiles: “Core”– Inline and structural markup
– No metadata that conflicts with G2– Slimmed-down set of NITF elements– http://tinyurl.com/ywzawr
• NITF Profiles: “Power”– Map Power metadata to G2 metadata– http://tinyurl.com/2rgfx6
© IPTC – www.iptc.org 13
![Page 14: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/14.jpg)
Conformance Levels
© IPTC – www.iptc.org 14
G2
“Power”“Core”
Metadata not in NITF
G2 expansion of NITF possible
Map to G2
No map to G2
![Page 15: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/15.jpg)
Conformance Levels• Terms “Core” and “Power” problematic• Is the idea of conformance levels helpful?• Are there different views? Such as
– Vendor / developer: different levels of development effort
– User: Reliable interchange at different levels of complexity
• Expressiveness vs. concision or different clusters of users?
© IPTC – www.iptc.org 15
![Page 16: NITF 2009 Spring Working Group](https://reader038.fdocuments.net/reader038/viewer/2022110302/546cd7e4b4af9f662c8b5271/html5/thumbnails/16.jpg)
© IPTC – www.iptc.org 16
NITF
Any other business?
Date and place of next meeting:
Seoul, Korea - June 2009
Muito obrigado et até mais!