<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type='text/xsl' href='/Content/StratML.xslt'?>
<PerformancePlanOrReport>
  <Name>StratML</Name>
  <Description>This project is to describe, develop and promote StratML as an international standard.</Description>
  <OtherInformation>
  </OtherInformation>
  <!--Strategic Plan Core-->
  <StrategicPlanCore>
    <Vision>
      <Description>
      </Description>
      <Identifier>Vision_1072ae7b-dc0e-4a8c-b9c4-ff2b9d1452e8</Identifier>
    </Vision>
    <Mission>
      <Description>
      </Description>
      <Identifier>Mission_1072ae7b-dc0e-4a8c-b9c4-ff2b9d1452e8</Identifier>
    </Mission>
    <Value>
      <Name>Machine-readability</Name>
      <Description>Machine-readable data is data (or metadata) which is in a format that can be understood by a computer.</Description>
    </Value>
    <Value>
      <Name>International</Name>
      <Description>
      </Description>
    </Value>
    <Value>
      <Name>Accountability</Name>
      <Description>
      </Description>
    </Value>
    <Value>
      <Name>Strategic Alignment</Name>
      <Description>Strategic alignment is about marshalling all of the organization’s resources to achieve its goals and objectives. Practically speaking – beyond establishing a clear, concise, and inspirational vision statement – that means organizational leaders should:

1. Render the organization’s strategic plan in open, standard, machine-readable StratML format;
2. Populate the goal and objective identifier elements with globally unique identifiers (GUIDs) or other identifiers that are standardized, unique, and well-known within the organization;
3. Enable referencing of those identifiers in metadata associated with each record/document/piece of content, thereby creating linkages to the goal(s) and objective(s) it supports and thus strategic alignment, literally speaking; and
4. Make available to the organization’s stakeholders a content/document/records management application/service that supports the StratML standard and makes it easy (semi-automatic) for users to provide the necessary metadata.
(from http://xml.fido.gov/stratml/references/AIIM-BP-StratML.pdf)</Description>
    </Value>
    <Value>
      <Name>Transparency</Name>
      <Description>
      </Description>
    </Value>
    <Value>
      <Name>Standardised</Name>
      <Description>
      </Description>
    </Value>
    <Goal>
      <Name>Revenue</Name>
      <Description>Develop revenue opportunities for StratML implementations</Description>
      <Identifier>Goal_a434e768-eec7-41cf-a4b3-58a09a7e975d</Identifier>
      <SequenceIndicator>1</SequenceIndicator>
      <OtherInformation>
      </OtherInformation>
    </Goal>
    <Goal>
      <Name>Outreach</Name>
      <Description>Spread the word about StratML</Description>
      <Identifier>Goal_9d93b65f-669a-4613-a537-04e64d396bb6</Identifier>
      <SequenceIndicator>2</SequenceIndicator>
      <OtherInformation>
      </OtherInformation>
    </Goal>
    <Goal>
      <Name>REST Services</Name>
      <Description>Develop RESTful services for StratML</Description>
      <Identifier>Goal_10e758fd-1fb2-49f6-ab0e-c5d83e23925a</Identifier>
      <SequenceIndicator>3</SequenceIndicator>
      <OtherInformation>Provide indexes giving access to StratML documents using restful naming and delivery conventions in HTML, Json and XML.

Jason Lind has provided a RESTful service for the IRS charity data. Simply execute a GET at https://stratml.services/api/PartTwo or https://stratml.services/api/PartOne to discover the id's and then https://stratml.services/api/PartTwo/{id} and https://stratml.services/api/PartOne/{id} to get the underlying document.

Chris Fox has provided a RESTful service for projects whose StratML has been made public in StratNavApp.com. Simply execute a GET at https://www.stratnavapp.com/StratML/part1, or https://www.stratnavapp.com/StratML/part2, or https://www.stratnavapp.com/StratML/part3, to discover the IDs and then https://www.stratnavapp.com/StratML/part1/{id}, https://www.stratnavapp.com/StratML/part2/{id}, or https://www.stratnavapp.com/StratML/part3/{id} to get the content. For styled content, it is https://www.stratnavapp.com/StratML/part1/{id}/Styled, https://www.stratnavapp.com/StratML/part2/{id}/Styled, or https://www.stratnavapp.com/StratML/part3/{id}/Styled</OtherInformation>
      <Stakeholder StakeholderTypeType="Individual">
        <Name>Chris Fox</Name>
        <Description>
        </Description>
        <Role>
          <Name>
          </Name>
          <Description>Developed a StratML REST service at https://StratNavApp.com</Description>
          <RoleType>Performer</RoleType>
        </Role>
      </Stakeholder>
      <Stakeholder StakeholderTypeType="Individual">
        <Name>Jason Lind</Name>
        <Description>
        </Description>
        <Role>
          <Name>
          </Name>
          <Description>Developed a StratML REST service at https://stratml.services</Description>
          <RoleType>Performer</RoleType>
        </Role>
      </Stakeholder>
    </Goal>
    <Goal>
      <Name>Improvement</Name>
      <Description>Continue to improve the StratML Standard</Description>
      <Identifier>Goal_de71940d-7a38-4ca5-943d-7fdce7312bd9</Identifier>
      <SequenceIndicator>4</SequenceIndicator>
      <OtherInformation>
      </OtherInformation>
    </Goal>
    <Goal>
      <Name>Developer Resources</Name>
      <Description>Develop and improve resources for StratML developers</Description>
      <Identifier>Goal_d3378b25-557f-4c04-ab00-d04be162fec2</Identifier>
      <SequenceIndicator>5</SequenceIndicator>
      <OtherInformation>The forms-based UIs that have been developed thus for creating and editing StratML files are listed with hyperlinks at http://stratml.us/#Forms

The prototypical StratML services available thus far are listed at http://stratml.us/#Services

A listing of some of the types of tools, apps, and services that will be required is available in StratML format at http://stratml.us/carmel/iso/SMLTASwStyle.xml 

The schemas themselves are documented at:
- http://stratml.us/#Part1 
- http://stratml.us/#Part2 
- http://stratml.us/#Part3</OtherInformation>
      <Stakeholder StakeholderTypeType="Individual">
        <Name>Owen Ambur</Name>
        <Description>
        </Description>
        <Role>
          <Name>StratML Committee Chair</Name>
        </Role>
      </Stakeholder>
    </Goal>
    <Goal>
      <Name>ISO Status</Name>
      <Description>Achieve International Standards Organisation (ISO) status</Description>
      <Identifier>Goal_a3c95862-e129-461e-a43c-287253b4666a</Identifier>
      <SequenceIndicator>6</SequenceIndicator>
      <OtherInformation>Part 1 is already an ISO standard ( (ISO 17469-1). Parts 2 and 3 have yet to achieve ISO standard.</OtherInformation>
      <Stakeholder StakeholderTypeType="Organization">
        <Name>International Standards Organisation (ISO)</Name>
        <Description>
        </Description>
      </Stakeholder>
    </Goal>
    <Goal>
      <Name>Stakeholder Consultation &amp; Linkages</Name>
      <Description>Stakeholder Consultation &amp; Linkages</Description>
      <Identifier>Goal_7ce42994-74a7-4d98-b990-7460f3b44078</Identifier>
      <SequenceIndicator>7</SequenceIndicator>
      <OtherInformation>One of the problems with strategic planning as it is commonly conducted is that stakeholders are not actively engaged. An even more basic problem is that many organizations have not even explicitly identified their stakeholders, much less linked their goals to them. Again, Congress has recognized that problem and established a good practice. The eGov Act requires agencies to work together to link their performance goals to key stakeholder groups.9 The Government Performance and Results Act (GPRA) Intentions
- What do we want to accomplish? What are our longer-term goals and near-term objectives? Stakeholders
- Who is trying to do it and for the benefit of whom? Results
- How do we know if progress is being made and when success has been achieved?

requires that stakeholders be consulted.

10 However, as currently practiced, such consultation leaves much to be desired.

(from http://xml.fido.gov/stratml/references/AIIM-BP-StratML.pdf)</OtherInformation>
    </Goal>
    <Goal>
      <Name>Capability/Process Maturity</Name>
      <Description>Capability/Process Maturity</Description>
      <Identifier>Goal_3b56684b-636e-4aa2-8759-425bd21d7697</Identifier>
      <SequenceIndicator>8</SequenceIndicator>
      <OtherInformation>All of the existing “social” networking services are immature for business-quality usage. However, combined with an open standard like StratML, business networking services can help organizations engage their stakeholders far more efficiently and effectively (maturely) than ever before possible. 11

(from http://xml.fido.gov/stratml/references/AIIM-BP-StratML.pdf)</OtherInformation>
    </Goal>
    <Goal>
      <Name>Agility</Name>
      <Description>Agility</Description>
      <Identifier>Goal_48cfed9b-5e4d-42ec-99b6-71b4748adc52</Identifier>
      <SequenceIndicator>9</SequenceIndicator>
      <OtherInformation>Another problem is that strategic plans are typically updated every three to five years, with considerable time, effort, money, and fanfare invested in publishing them in lovely glossy format … at which point they become “shelfware,” outdated before the ink is dry. Maintaining plans in machine-readable StratML format on the Web facilitates updating to accommodate the increasing pace of change.

(from http://xml.fido.gov/stratml/references/AIIM-BP-StratML.pdf)</OtherInformation>
    </Goal>
    <Goal>
      <Name>Data Centricity (Rather than Software Centricity)</Name>
      <Description>Data Centricity (Rather than Software Centricity)</Description>
      <Identifier>Goal_942543c4-1a35-4373-905a-86e711eb8ac8</Identifier>
      <SequenceIndicator>10</SequenceIndicator>
      <OtherInformation>Naturally, as long as their customers let them get away with it, software and service providers want to build into their offerings means of locking users into doing business with them on a long-term basis – particularly by using proprietary data formats, “owning” and controlling their users’ data, and making it difficult and costly for them to switch to other products and services. Customer loyalty should be based upon superior service, not proprietary data-based vendor lock-in.

(from: http://xml.fido.gov/stratml/references/AIIM-BP-StratML.pdf)</OtherInformation>
    </Goal>
    <Goal>
      <Name>Data Standards (Semantics &amp; Structure)</Name>
      <Description>Data Standards (Semantics &amp; Structure)</Description>
      <Identifier>Goal_9cafea1d-e706-4cff-86b2-e5374b3c7a36</Identifier>
      <SequenceIndicator>11</SequenceIndicator>
      <OtherInformation>Business data and documents should be relatively persistent and maintained in open, standard formats – like StratML – throughout their full life cycles. By contrast, software and services should be fungible, based upon quality and value, which may change as rapidly as the technology supporting it. Switching costs should be low. Software and service providers should compete on the basis of real value-add and superior service, rather than artificially imposed proprietary exploitation of users’ data.

(from http://xml.fido.gov/stratml/references/AIIM-BP-StratML.pdf)</OtherInformation>
    </Goal>
    <Goal>
      <Name>Interoperability</Name>
      <Description>Interoperability</Description>
      <Identifier>Goal_1609ff44-5771-48e9-9e9a-1d6cef7f0179</Identifier>
      <SequenceIndicator>12</SequenceIndicator>
      <OtherInformation>By virtue of compliance with open data standards, information should flow seamlessly across organizational and system boundaries, free of software dependencies.

(from http://xml.fido.gov/stratml/references/AIIM-BP-StratML.pdf)</OtherInformation>
    </Goal>
    <Goal>
      <Name>Discoverability</Name>
      <Description>Discoverability</Description>
      <Identifier>Goal_e229d178-93f5-45ce-82e2-5f174722a224</Identifier>
      <SequenceIndicator>13</SequenceIndicator>
      <OtherInformation>It should be quick and easy for users to query and discover content/documents/records based upon the goals/objectives with which they are aligned as well as stakeholder groups they support, and vice versa (top-down &amp; bottom-up).

(from http://xml.fido.gov/stratml/references/AIIM-BP-StratML.pdf)</OtherInformation>
    </Goal>
    <Goal>
      <Name>Metrics</Name>
      <Description>Metrics</Description>
      <Identifier>Goal_6532d810-9f72-4f40-89e3-297b5967e35b</Identifier>
      <SequenceIndicator>14</SequenceIndicator>
      <OtherInformation>Performance indicators should automatically be gleaned, aggregated, and reported from records created in the routine course of the business process (rather than as a separate after-the-fact, madeup/make-work reporting process). To accommodate that requirement, the original, authoritative records themselves should be created and maintained in open, standard, machine-readable format so that the process of auditing data maintained in databases can be automatically conducted as anytime.

(from http://xml.fido.gov/stratml/references/AIIM-BP-StratML.pdf)</OtherInformation>
    </Goal>
    <Goal>
      <Name>Partnership</Name>
      <Description>Partnership</Description>
      <Identifier>Goal_44cfb1bc-374e-446d-9bac-78a9a6ee5343</Identifier>
      <SequenceIndicator>15</SequenceIndicator>
      <OtherInformation>Performance partnerships should be formed around common values and shared objectives, which should be cross-referenced in each organization’s performance plan. The stratml:Reference elements can be used to do so, by citing the identifiers of the shared objectives. Value-added service providers can reference that data to support each of the performance partners by helping them manage their own outputs while monitoring those of their partner(s).

(from http://xml.fido.gov/stratml/references/AIIM-BP-StratML.pdf)</OtherInformation>
    </Goal>
    <Goal>
      <Name>International</Name>
      <Description>Achieve International use</Description>
      <Identifier>Goal_0c4a02d1-442c-40fd-9858-7f125ca18315</Identifier>
      <SequenceIndicator>16</SequenceIndicator>
      <OtherInformation>Section 10 of the GPRA Modernization Act (GPRAMA) requires U.S. federal agencies to publish their strategic and performance plans and reports in machine-readable format, like StratML.

We are not yet aware of any other countries or international organisations with a similar requirement.</OtherInformation>
    </Goal>
    <Goal>
      <Name>Charitable Fundraising</Name>
      <Description>Facilitate the identification and selection of charitable causes to which donors may wish to contribute</Description>
      <Identifier>Goal_1850678b-8735-490d-bbb2-e91f1dd26b5f</Identifier>
      <SequenceIndicator>17</SequenceIndicator>
      <OtherInformation>
      </OtherInformation>
      <Stakeholder StakeholderTypeType="Generic_Group">
        <Name>Charitable Donors</Name>
        <Description>
        </Description>
      </Stakeholder>
      <Stakeholder StakeholderTypeType="Generic_Group">
        <Name>Charities</Name>
        <Description>
        </Description>
      </Stakeholder>
      <Stakeholder StakeholderTypeType="Generic_Group">
        <Name>Charity portals / aggregators</Name>
        <Description>
        </Description>
      </Stakeholder>
      <Objective>
        <Name>Build a portal(s) which allows donors to search and evaluate charitable organisations using data submitted by them in StratML format</Name>
        <Description>Build a portal(s) which allows donors to search and evaluate charitable organisations using data submitted by them in StratML format</Description>
        <Identifier>Objective_4552298b-0b2e-466d-9fab-a119ff095a69</Identifier>
        <SequenceIndicator>1</SequenceIndicator>
        <OtherInformation>
        </OtherInformation>
      </Objective>
      <Objective>
        <Name>Encourage charitable organisations to submit plans and performance plans to the portal(s) in StratML format</Name>
        <Description>Encourage charitable organisations to submit plans and performance plans to the portal(s) in StratML format</Description>
        <Identifier>Objective_26aefe2b-6ea6-42e4-943b-8dffc0ce356c</Identifier>
        <SequenceIndicator>2</SequenceIndicator>
        <OtherInformation>
        </OtherInformation>
      </Objective>
      <Objective>
        <Name>Encourage donors to use the portal(s) to identify and select charitable causes to support</Name>
        <Description>Encourage donors to use the portal(s) to identify and select charitable causes to support</Description>
        <Identifier>Objective_f5560ba9-3509-4397-8c46-ea1edd10cb4e</Identifier>
        <SequenceIndicator>3</SequenceIndicator>
        <OtherInformation>
        </OtherInformation>
      </Objective>
    </Goal>
    <Framework>
      <SWOT>
        <Strength>
          <Name>Some training and promotional materials have already been produced</Name>
          <Description>See http://stratml.us/references/StratMLTraining.htm</Description>
        </Strength>
        <Strength>
          <Name>C.More than 4,000 StratML Documents have been created and are freely available for usage in tools, apps, and services demonstrating the utility of the standard.</Name>
          <Description>Most are available at http://stratml.us/drybridge/index.htm, with a few more at http://strategiclearningapp.com/Project/PublicStratMLList</Description>
        </Strength>
        <Strength>
          <Name>StratML provides a standard vocabulary and schema for strategic and performance plans and reports</Name>
          <Description>As such it provides a benchmark for the completeness of a strategy.

See Michael Taylor's blog post on this subject.</Description>
        </Strength>
        <Strength>
          <Name>StratML Part 1, Strategic Plans, is an ISO Standard</Name>
          <Description>
          </Description>
        </Strength>
        <Strength>
          <Name>StratML Part 2, Performance Plans &amp; Reports, was approved as an ANSI standard</Name>
          <Description>
          </Description>
        </Strength>
        <Weakness>
          <Name>The existing prototypical query services do not take advantage of the structure and semantics of the schema.</Name>
          <Description>The greatest unmet need is for a robust, faceted query service for the StratML collection, which now comprises &gt;3,400 documents.  In particular, it would be good to be able to selectively query the names and/or descriptions of Goals, Objectives, Values, and Stakeholders.

MarkLogic had such a prototypical query service, whose history is documented at http://xml.fido.gov/stratml/index.htm#MarkLogic.  Unfortunately, the guy who developed it left the company and his prototype was not maintained.  However, a couple screen shots are available at http://xml.fido.gov/stratml/references/MarkLogicStratMLQueryPrototype.htm and the StratML collection is now considerably larger and Part 1 is now an international standard.  So such a service is more needed and, presumably, would be more valuable.

Owen makes use of a site-specific search on Google, but this only works on a single site at a time, and won't pick up any StratML posted elsewhere. One would have thought that this was a problem that needs to be solved by someone like Google who would have the capability to index StratML/XML documents across all domains.

StratNavApp includes a Google site-specific search which covers Owen's site and the public StratML available on StratNavApp (i.e. two sites, but not more) - see here - but otherwise suffers the same limitations of the capability mentioned in the previous paragraph. </Description>
        </Weakness>
        <Weakness>
          <Name>AIM will charge for StratML training</Name>
          <Description>Fees may deter people from learning about StratML.

Is there an opportunity for providing complimentar free materials?</Description>
        </Weakness>
        <Weakness>
          <Name>StratML does not incorporate any graphical elements</Name>
          <Description>Much of the strategic discourse I encounter relies heavily on graphical elements. Such graphical elements range from:
- simple text formatting, such as bullet points, lists, tables, charts, graphs, etc., which enhance the readability of information, to
- graphical representations of key strategy concepts, such as Balanced Scorecard Strategy Maps (which show the causal relationships between goals) and Porter Activity Maps (which show the interdependencies and tradeoffs between the key activities which underpin and organisations strategic positioning).

Both of these types can be reduced to XML, but are not allowed for in StratML. A simple solution would be to allow HTML, or a subset thereof, in the description fields within StratML.

StratML forces strategic discourse this to be reduced to plain (albeit very structured) text only.

Although this might ultimately improve the quality of strategic discourse, it might also slow its rate of adoption. This is an area for consideration for future inclusion in the StratML standard.</Description>
        </Weakness>
        <Weakness>
          <Name>"StratML" generates low levels of search</Name>
          <Description>See, for example, Google Trends analysis at https://www.google.co.uk/trends/explore#q=stratml , which shows that very few people do Google Searches containing the term "StratML".</Description>
        </Weakness>
        <Weakness>
          <Name>The StratML applications developed thus far are prototypical in nature and lack features compelling enough to attract high-volume usage</Name>
          <Description>Most of the emphasis thus far seems to have been on generating StratML, rather than on consuming it.

What is probably required is one or more aggregating portals which bring together subsets of StratML output (e.g. US charitable organisations, or UK political candidates) with tools to work with the data to achieve specific objectives.</Description>
        </Weakness>
        <Weakness>
          <Name>Posting most StratML on a US Government domain may deter international / non-US adoption</Name>
          <Description>
          </Description>
        </Weakness>
        <Weakness>
          <Name>StratML lacks any representation of action plans to achieve strategic goals and objectives</Name>
          <Description>
          </Description>
        </Weakness>
        <Opportunity>
          <Name>US Federal agencies are required to publish their strategic and performance plans and reports in a machine readable format</Name>
          <Description>Section 10 of the GPRA Modernization Act (GPRAMA) requires U.S. federal agencies to publish their strategic and performance plans and reports in machine-readable format, like StratML.  http://xml.fido.gov/stratml/references/PL111-532StratML.htm#SEC10</Description>
        </Opportunity>
        <Opportunity>
          <Name>The Standards Board that is taking over AIIM's standards program, under which StratML has been specified and moved through the ANSI &amp; ISO processes, is planning to develop a strategic plan of its own.</Name>
          <Description>
          </Description>
        </Opportunity>
        <Threat>
          <Name>HTML5 and RDFa might be positioned as an alternative for exposing the semantics of strategic plans</Name>
          <Description>Colin McKenzie suggested that proposing HTML5 plus RDFa might be proposed for devliering the semantics for strategy, instead of "author first" XML. [We might need Colin to elaborate on this to understand its merits, and more importantly, where we think StratML is the stronger contender.]</Description>
        </Threat>
        <Threat>
          <Name>AIIM is withdrawing from standards development, how will the standard continue to progress?</Name>
          <Description>On 8 September, Owen mentioned that AIIM is withdrawing from standards development activities. Who will see parts 2 and 3 through the ANSI process?</Description>
        </Threat>
      </SWOT>
    </Framework>
  </StrategicPlanCore>
  <!--Administrative Information-->
  <AdministrativeInformation>
    <Identifier>StrategyPlan_1072ae7b-dc0e-4a8c-b9c4-ff2b9d1452e8</Identifier>
    <StartDate>
    </StartDate>
    <EndDate>
    </EndDate>
    <PublicationDate>2025-10-29</PublicationDate>
    <Source>https://www.stratnavapp.com/StratML/Part3/1072ae7b-dc0e-4a8c-b9c4-ff2b9d1452e8/Styled</Source>
    <Submitter>
      <Identifier>Submitter_1072ae7b-dc0e-4a8c-b9c4-ff2b9d1452e8</Identifier>
      <GivenName>
      </GivenName>
      <Surname>
      </Surname>
      <PhoneNumber>
      </PhoneNumber>
      <EmailAddress>
      </EmailAddress>
    </Submitter>
  </AdministrativeInformation>
</PerformancePlanOrReport>