The root element for the document instance. Bill = A proposal for a new law, a change in current law, repeal of a current law, or for a constitutional amendment. Resolution = Formal actions of the legislature which express intent on the part of one or both bodies, but are not codified upon passage. Act = The official name for a bill that has been enrolled for presentation to the governor. Each act is assigned a chapter number. Chapter = Chapter is short for Session Law chapter. This is the final document after action by the legislature, governor, and Secretary of State. Types of legislative bodies. Container for one or more identifier instances. A unique code for the document. Container for one or more title instances. The name given to the document. Container for one or more type instances. The recognized form or genre of the document. Refer to the definition for "document.types" for more details about the values. Container for one or more jurisdiction instances. The jurisdiction associated with the document. The state code associated with the document. (Values=Abbreviation as specified by ISO 3166-2:US.) The state name associated with the document. The legislative body that created the document. (Values="House" or "Senate".) Container for one or more agent instances. The agency, organizational unit, or individual associated with the creation or publication of the document. The agency or organizational unit responsible for making the document available. The agency, organizational unit, and/or individual primarily responsible for the content of the document. Equates to the term "Creator" or "Originator" used in some environments. Container for one or more date instances. Date of publication. Date document became publically available. Use standard ISO 8601 (YYYY-MM-DD). Container for one or more session instances. Identifies a specific assembly of the legislature. Sequential meeting of the legislature in regular session as designated by the state constitution. The year the document was published. The sequential session number in a calendar year. 0 means regular legislative session. Container for one or more description instances. A summary, in free-text prose, of the content of the document. Container for one or more subject instances. The subject matter or topic of the document. Container for one or more relation instances. Container for the parts of one meta.relation instance, the link between one document and another. The version of a document. A companion bill is usually an identical bill introduced in the other body. The number assigned to an enrollment. This number becomes the session law chapter number if the enrollment becomes a Session Law. Container for one or more governor.action instances. This element only applies to enrollments passed by both bodies of the legislature. The governor has several options when considering an enrollment. (Refer to the documentation for allowed values.) Container for one or more management.history instances. Container for the parts of management history, the date and description of management actions performed on the document. Container for the parts of one event instance. The date and time at which a defined management event occurs. Use standard ISO 8601 (YYYY-MM-DD and hh-mm). An event which relates to the management of the document. (See documentation for list of values.) The specific details of the event in free-text prose. Container for one or more rights instances. A description of use restrictions, such as copyright notice, placed on the document. Example: Copyright (C) 2008 by the Office of the Revisor of Statutes, State of Minnesota. All rights reserved. Optional general-purpose "tag/value" pair of metadata elements. This is for use if a standard metadata element is not available within the schema. It should be used only when additional documentation is supplied by the provider to define the purpose of this metadata. XML source, in the provider's native syntax. This is not validated but is simply encapsulated within the CDATA marked section. Use of CDATA is necessary because named entities may be contained within the XML source. An HTML rendition of the document being interchanged. This is not validated but is simply encapsulated within the CDATA marked section. Use of CDATA is necessary because named entities may be contained within the XML source. A block of one or more attachments. These attachments are an encoded version of a binary format, such as PDF or Word or other proprietary delivery format. By encoding it (using Base64 or other "7-bit-safe" format) and enclosing it within a CDATA marked section, the provider may include other types of versions of the document. One attachment. Specify an ID for reference. Specify the type of encoding for applications to use for processing. Specify the source (as MIME type).