'Info classification' requirement for HNAP2.3 about pygeometa HOT 6 CLOSED

Information Category: mandatory
Geography: mandatory
Content: optional, can have multiple values
Program: optional, can have multiple values
GC Security Level: mandatory

1. for program and GC Security Level as discussed in #19 you can use an XML injection as a post-process for napec based elements
2. for the information category, geography and content classifications how about 3 more hnap-specific MCF parameters?
   • hnap_category_information_en, hnap_category_information_fr
   • hnap_category_geography_en, hnap_category_geography_fr
   • hnap_category_content_en, hnap_category_content_fr

from pygeometa.

@tomkralidis

1. Agreed, GC Security Level can be dealt with via post-pygeometa xml injection just like issue #19, I'll try to take care of this
2. Ok for the new hnap-specific parameters for info+geo+content. Since these will have different values based on the dataset, it needs to be specified in the MCF itself, I'm letting you implement that part

from pygeometa.

@alexandreleroux implemented in master, can you verify?

from pygeometa.

@tomkralidis thanks, after fixing typos, I confirms it works.

Leaving ticket open to address:

1. GC Security Level
2. Update pygeometa's hnap documentation for the 3 new hnap_category_* parameters

from pygeometa.

gc security level addressed by xml injection implemented for #19 . Need to update documentation accordingly

from pygeometa.

After validation, this is a requirement on top of the HNAP schema and should be handled outside of pygeometa. Closing

from pygeometa.