By "real", I mean add the ability to map specific CCK fields to known NITF tags. This will be a PITA to build, but it's the only way to really make this module use all the features of NITF, in my opinion. Sure, we can just spit nodes out as bodies and use the NITF bits we can, but there's so much NITF *can* do it would be a real shame to not allow people to leverage all the options. A CCK -> NITF tag mapper is the way forward.