Hmmm. Interesting. This is not my impression of the use of hierarchy. Having re-read SDN.801 I can see it isn't clear what the purpose of hierarchy is. [Having said that, I've yet to meet anything that is clear in SDN.801 :) ] With your approach, how do I know if a label with classification value of 27 dominates (or not) a label with classification value of 5? Leaving classifications aside, I can still see a reason for hierarchy attribute on categories. If I have a hierarchic category named "Impact" with values "HIGH", "NORMAL" and "LOW" how do I present these to the user appropriately? Do we sya that "convention" is that they are presented in the order in which they are listed in the SPIF? I prefer formality to convention. NB I'm only proposing this as an optional attribute. Regards, Piers -----Original Message----- From: xmlspif-bounce@xxxxxxxxxxxxx [mailto:xmlspif-bounce@xxxxxxxxxxxxx] On Behalf Of Kurt Zeilenga Sent: 30 March 2010 17:16 To: xmlspif@xxxxxxxxxxxxx Subject: [xmlspif] Re: Hierarchic categories On Mar 29, 2010, at 10:59 AM, Piers Chivers wrote: > Hi, > We are meeting requirements where there is a need for more than one hierarchic list of values in a "label". > > As a solution to this would it be possible to add an "hierarchy" attribute to the tagCategory element that has the same meaning as the hierarchy attribute of the securityClassification element? Note that classification hierarchy in SPIFs is only for display purposes (ordering of classifications in UI menus and such). It should not used in evaluation of the ACDF. -- Kurt Classification added by SAFEmail - Labelling, Protective Marking and Release Control for Secure Messaging from Boldon James - www.boldonjames.com/safemail-ics