Introduction[1] Policy XML is intended to include policy information that is machine readable. There are times when machine readable policy either cannot be encoded in the elements available in the Policy XML specification or policy is difficult to encode for machine consumption. For occasions when policy cannot be encoded for machine consumption, this specification provides elements to express human readable policy. Specification[2] HumanPolicy is the intended root element of the schema. HumanPolicy must include the following four child elements (a) CourtKeys, (b) Name, (c) Description, and (d) RequirementsLevel. HumanPolicy may contain three additional child elements (1) Key, (2) Category, and (3) Address. Child Element(s) | minOccurs | maxOccurs | CourtKey | 1 | unbounded |
[3] HumanPolicy:CourtKeys is a container element for one or more HumanPolicy:CourtKey elements. The HumanPolicy:CourtKeys element is used to associate the policy statement with one or more CourtDetails:CourtKey values. See HumanPolicy:CourtKey element. [4] HumanPolicy:CourtKey provides a means to associate the human readable policy statement with a CourtDetails:CourtKey. The CourtDetails:CourtKey value is a unique identifier that corresponds to a division of a court. A HumanPolicy:CourtKey value must match a CourtDetails:CourtKey value or the court's CourtDetails:OrganizationKey value. If the HumanPolicy:CourtKey value matches the court's CourtDetails:OrganizationKey value, then the policy statement applies to every division of the court. If the HumanPolicy:CourtKey value matches one or more Court:Details:CourtKey values, then the policy statement applies only to those matching court divisions. [5] HumanPolicy:Key is a unique identifier for the policy statement. If there are more than one HumanPolicy elements, then all HumanPolicy:Key values must be unique. [6] HumanPolicy:Name is a short, descriptive name for the policy statement. Child Element(s) | minOccurs | maxOccurs | Paragraph | 1 | unbounded |
[7] HumanPolicy:Description is a detailed description that explains the policy. HumanPolicy:Description has one child element, HumanPolicy:Paragraph, that must occur once and may occur an unlimited number of times. A single paragraph or multiple paragraphs may be used to describe the policy. Child Element(s) | minOccurs | maxOccurs | Vocabulary | 0 | unbounded |
[8] HumanPolicy:Paragraph is a single paragraph that makes up part of the HumanPolicy:Description. HumanPolicy:Paragraph is defined as mixed content and may contain zero or an unlimited number of HumanPolicy:Vocabulary elements. A paragraph can be text only or it can include various vocabulary sprinkled within it. [9] HumanPolicy:Vocabulary is an element that marks-up an important word or series of words, such as a name or a defined term, in a paragraph. The global attributes Class and Type can be used to modify the HumanPolicy:Vocabulary element. The Class attribute functions in the same way as the HTML class attribute and should be used to convey style information for the vocabulary. The Type attribute may also be used to further define or modify the generic HumanPolicy:Vocabulary element.
[10] HumanPolicy:Category provides a means to categorize policy statements. HumanPolicy:Category includes a required Level attribute. The Level attribute may be one of six values Level1, Level2, Level3, Level4, Level5, or Level6. The Level attribute provides the ability to create a hierarchy of categories and subcategories without creating either a recursive element or additional fixed elements necessary for a non-recursive structure. For this type of categorization mechanism to function properly, policy statements must occur in the XML document in logical order based on category level. [11] For example, policy statements must occur with the following levels in document and logical order: Level1[1], Level2[1.1], Level2[1.2], Level1[2], Level2[2.1], Level2[2.2], where Category 1 has two subcategories that correspond to the first three levels in the example (i.e., Level1[1], Level2[1.1], Level2[1.2]) and where Category 2 has two subcategories that correspond to the second three levels in the example (i.e., Level1[2], Level2[2.1], Level2[2.2]). [12] The values Level2 through Level6 must always occur after a lower level. For example, Level2 may only occur after Level1. If the Level attribute is always set to Level1, then this means there is no categorization. [13] HumanPolicy:Address is a URL that points to a resource with additional information. If there are multiple resources that contain additional information, then those resources must be consolidated into one resource referenced by HumanPolicy:Address. [14] HumanPolicy:RequirementsLevel value is a required element that states whether the policy is required, recommended, optional, or informational. The values MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY are to be interpreted as described in Internet Engineering Task Force (IETF) Request for Comments (RFC) 2119 (http://www.ietf.org/rfc/rfc2119.txt). The value Information is not defined by RFC 2119. The Information value means that the policy statement is for informational purposes only and is not a required, recommended, or optional policy. |