This describes the XML representation of the UCF's Organizational Function XML Schema Definition (XSD). Each of the elements, types, and attributes that make up the format are described in detail.

The URL for the Organizational Function XML structure is as follows:

http://unifiedcompliance.com/NFI/XSDs/2_2/UCF_Functions_v2_2.xsd

It is not enough for any IT manager to document an information system and state that "this is an X system, and should be protected this or that way." The level of protection afforded to any IT system must depend upon the classification of the records, information in those records, and business functions that those records and that information supports. Hence, it is essentially the information that must be classified, which then defines the classification of the system.

The reason for information classification is to provide guidance to those who will first identify and then protect the confidentiality, integrity, and availability of that information.

In order to determine how to protect information, the organization must understand four key items:

1. The function itself, and its criticality for the organization (this document).

2. The type of tasks that must be performed in order to support the business function.

3. The type of records that fall within each information type.

4. Any special data handling rules that could be applied to those records.

Therefore, this XML specification is one part that defines and relates all four of these key items together into a cohesive whole.

UCF_Function_Item (UCF_Function_Item_Type)

The UCF_Function_List is comprised of the UCF_Function_Item containers. The UCF Function Item defines each individual "record" within the list. Each container is split into two key elements that must be present at all times:

• UCF_Meta_Data

• UCF_Basic_Info

The UCF_Function_Item describes the various functions that an organization might have. Information in and of itself carries certain value. However, the value of information when used during a task can either be value-add or devalued, based upon the organizational function. Therefore, it is important to understand the nature of each function within an organization when determining the classification and value of the information supporting that function.

UCF_Meta_Data (UCF_Meta_Data_Type)

For detailed documentation of Meta Data fields, please refer to the Meta Data documentation. Below is a list of the meta data fields that are included in the Function list.

• UCF_Function_Release_Version

• UCF_Function_SNED

• UCF_Function_ID

• UCF_Function_ID_CheckDigit

• UCF_Function_Live_Status

• UCF_Function_Deprecated_By

• UCF_Function_Deprecation_Notes

• UCF_Function_Date_Added

• UCF_Function_Date_Modified

UCF_Basic_Info (UCF_Basic_Info_Type)

The UCF_Basic_Info element has exactly what you'd expect - the most critical information that pertains to all types of Organizational Functions.

UCF_Function_Name (ucf:non-empty-string)

This is the name of the function itself.

UCF_Function_Description (ucf:non-empty-string)

This is the description of the organizational function.