Conceptual Requirements
The StratML conceptual requirements are to support the existing functionality provided by StratML Part1 and Part2, as well as to add features and concepts still being discussed but encompassing the specifications of GPRAMA and Performance.gov, which are better described by theproposed data element mappings, for example.

Implementation Requirements
The main implementation objective for StratML Part3 is the flexibility and modularity to better support the more elaborate strategic plan, performance plan, and performance report requirements while ensuring that users, authors, stakeholders, and developers are not burden by sophistication and complexity that they may not require at times.

Implementation Objective
Providing the implied flexibility and modularity implies:

• Logical Structure, Hierarchy, and Relations: Making the document structure logical rather than physical, where nested document sections, for example, may not be physically nested, but rather logically related, by use of relationship elements. Not only the document sections are hierarchically related, not only relevant sections can be iterated as required, but each of the relations can be defined, described, and qualified, including support for access control.
• External documents: More so, StratML Part3 relation sections are also used to define, describe, and qualify relations with external resources, including other strategy and performance plans or reports.
• Physical Structure: StratML Part3 document physical structure is a flat list of structurally similar elements, each with specific attributes and no sub-elements or embedded elements, like a database record dataset. some elements define relations while the others define the other document sections. Applications use relation elements to implement the specified structure and offer users the structured business view.
• Generalized Sections: Defining a singleStratML element, the StratML Part3 schema defines all acceptable section types, acceptable attributes for all section types, as well as the acceptable value ranges and characteristics for each acceptable attribute.
• Required Attributes: Some attributes are required for all sections (e.g. elements) starting with identification and classification (e.g. type). All others are optional although many are recommended.
• Generalized References: The StratML Part3 schema defines a generalized referencing scheme for the main reference types:
• Identification: Identity referencing (e.g. Primary keys, GUID)
• Electronics: Electronic (e.g. Web) document and asset referencing (e.g. URIs)
• Time: Period, Date, and Time referencing (e.g. ISO 8601)
• Space: Spacial references (e.g. addresses, geo-location)
• StrategicPlanCore: The StrategicPlanCore elements of StratML Part1 and Part2, which contained no specific information and were only used as section containers, are undefined and not required for Part3

More Information
More information is also also available from other sections of theStratML portal, as well as by requesting it fromStratML (at) DNAOS (dot) com", where questions, comments, and suggestions are appreciated and answered.