<?xml version="1.0" encoding="UTF-8"?>
<StrategicPlan xmlns="urn:ISO:std:iso:17469:tech:xsd:stratml_core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ISO:std:iso:17469:tech:xsd:stratml_core http://xml.govwebs.net/stratml/references/StrategicPlanISOVersion20140401.xsd"><Name>What Relevant Data is StratML Well Suited to Provide for Data-Driven Models and Simulations?</Name><Description/><OtherInformation/><StrategicPlanCore><Organization><Name>Dazza Greenwood</Name><Acronym>DG</Acronym><Identifier>_aa3140e2-73e1-11e6-94b1-9c5f42b9d64e</Identifier><Description/><Stakeholder><Name/><Description/></Stakeholder></Organization><Vision><Description/><Identifier>_aa314268-73e1-11e6-94b1-9c5f42b9d64e</Identifier></Vision><Mission><Description>To evaluate the readiness and value of StratML as an additional dimension of entity-level information for statistical modeling, simulation environments and other business or strategy focused data analytics.</Description><Identifier>_aa31434e-73e1-11e6-94b1-9c5f42b9d64e</Identifier></Mission><Value><Name/><Description/></Value><Goal><Name>Purposes, Outcomes &amp; Metrics</Name><Description>Enable or support standard meta-data on expected outcomes, success metrics and intended purposes</Description><Identifier>_aa3144de-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>... I'm interested in the aspect of StratML that enables or supports standard meta-data on expected outcomes, success metrics and intended purposes because I keep running into the need to codify that as part of public law and regulations in a standard, machinable way.</OtherInformation><Objective><Name>Codification</Name><Description>Codify such meta-data as part of public law and regulations in a standard, machinable way.</Description><Identifier>_aa3145b0-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>1.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Tracking</Name><Description>Track the human-readable goals, performance and results intended/expected from automated legal entities</Description><Identifier>_aa31466e-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name>Automated Legal Entities</Name><Description/></Stakeholder><OtherInformation>I'm also interested in that aspect as a possible short cut to tracking the human-readable goals, performance and results intended/expected from automated legal entities (ie purely digital and substantially autonomous shell corps, holding companies, single-purpose subsidiaries, etc).</OtherInformation><Objective><Name/><Description/><Identifier>_aa3147cc-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Goals, Roles, Functions &amp; Deliverables</Name><Description>Label or otherwise designate the goals/roles and expected functions/deliverables of entities.</Description><Identifier>_aa3148bc-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>3</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>Also, I've been underwhelmed or outright confused by how vendor systems and researchers/grad students go about labeling or otherwise designating the goals/roles and expected functions/deliverables of entities in various predictive analytics engines or "what-if" decision support systems (eg agent-based modeling, simulation environments and advanced test harnesses in the context of all-digital markets/exchanges, payment networks, supply/value chains and data or service integration oriented federations (primarily identity federations like IDfederation.org but also other larger-scale multi-organizational transaction-focused or communications-focused networks).  </OtherInformation><Objective><Name>Attention</Name><Description>Enable attention to goals/actions/outputs.</Description><Identifier>_aa31495c-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>3.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>It can be hard to remember or keep in active attention what the assumed or expected goals/actions/outputs are supposed to be for all the players especially as the data in dynamic reports, dashboards and sims, gets more complex, multi-dimensional and dynamic.</OtherInformation></Objective><Objective><Name>Metadata Extraction</Name><Description>Extract choice field types and other meta-data or data-model type designations to keep straight and immediately knowable via a little "mouse-over" action or label/legend glance-based display.</Description><Identifier>_aa314a24-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>3.1.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>I'm thinking maybe I can extract some choice field types and other meta-data or data-model type designations from StratML to keep straight and immediately knowable via a little "mouse-over" action or label/legend glance-based diplay.  Especially when changing assumptions or cycling through various vantage-points or algorithmic models etc I find it hard to keep that stuff top-of-mind and in it appears to me that StratML has been applied as a source of stated organizational strategy, expected goals and enumerated objectives for use by performance measurement and results-based management.</OtherInformation></Objective><Objective><Name>Decision Support, Situational Awareness &amp; Data Science</Name><Description>Enable advanced data-driven business decision support, situational awareness and other ways people can use data-science to understand quickly, navigate accurately and operate successfully within vast and changing information-intensive environments.</Description><Identifier>_aa314aec-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>3.1.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Assuming that is true and it is serviceable for that job, then I think it can be used for some of the more advanced data-driven business decision support, situational awareness and other ways people can use data-science to understand quickly, navigate accurately and operate successfully within vast and changing information-intensive environments.</OtherInformation></Objective><Objective><Name>Integrations &amp; Workflows</Name><Description>Support automated cross-boundary service integrations, distributed event-based or process-based workflows</Description><Identifier>_aa314bc8-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>3.1.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Eventually, this sort of more standard organization-level data feed would also be really valuable for more usable and interoperable implementations of automated cross-boundary service integrations, , distributed event-based or process-based workflows and  tied to organizations expected behavior and actions or interactions, goals/drivers/inhibitors, objectives/outcomes and inputs/outputs.</OtherInformation></Objective><Objective><Name>Standard</Name><Description>Support a standard approach to express the expected performance and outcomes/outputs of various entities in complex reports and visualizations.</Description><Identifier>_aa314cae-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>3.1.4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Moreover, as I work increasingly with Blockchain enabled systems and other deeply automated or partly autonomous  systems with ever fewer human review, decision and approval points an aspect of the data needed for performance review is highly valuable.  Namely, it would be incredibly valuable to have a standard approach (including by simple, flat standard markup) to express the expected performance and outcomes/outputs of various entities in complex reports and visualizations.</OtherInformation></Objective><Objective><Name>Entity Attributes</Name><Description>Provide a valid, verifiable, reliable, repeatable and reusable taxonomy, data model or a simple markup (ie StratML) to capture, store, discover, access and use meta-data on basic, frequently needed entity attributes.</Description><Identifier>_aa314d8a-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>3.1.5</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>I could really use (and increasingly need) a valid, verifiable, reliable, repeatable and reusable taxonomy, data model or a simple markup (ie StratML) to capture, store, discover, access and use meta-data on basic, frequently needed entity attributes.</OtherInformation></Objective><Objective><Name>Roles</Name><Description>Document entity roles-in-marketplaces</Description><Identifier>_aa314e66-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>3.1.5.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Specifically, the sorts of attributes that would be very important if readily and continuously available include entity role-in-marketplace, function-in-system, relationship-in-model, position-in-network and similar info so it is machine readable and readily computable for a wide variety of arbitrary purposes.  Some of this is directly mapped to the existing standard or could be a dialect of StratML.  Some could be custom elements and attributes of the type markup languages make easy to add-in, such as designation of augmenting sets of tags and labels which can themselves be related to defined characterizations or to broader/deeper narrative via anchored divs and delineated spans of content.</OtherInformation></Objective><Objective><Name>Functions</Name><Description>Document functions-in-systems</Description><Identifier>_aa314f4c-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>3.1.5.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Relationships</Name><Description>Document relationships-in-models</Description><Identifier>_aa315032-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>3.1.5.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Positions</Name><Description>Document positions-in-networks</Description><Identifier>_aa315118-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>3.1.5.4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Reporting</Name><Description>Self report</Description><Identifier>_aa3151fe-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>3.1.6</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name>Public Agencies</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Private Sector Entities</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Third Parties</Name><Description/></Stakeholder><OtherInformation>It is great if at least some StratML is self-reported by public agencies (eg as part of the self-asserted reporting requirements for which the entity is responsible) and especially by private sector entities but if I am correct that the markup can be used for the purposes I'm contemplating when it is applied after the fact or as an added dimensional layer sourced from internal staff or by partner or purchased services of third party analysts or other intermediaries and value-added data providers. So long as there is a standard and regular flow of this type of meta-data about entities, there is real value to feed that into downstream algorithms, statistical models and applications.</OtherInformation></Objective></Goal><Goal><Name>Modeling, Description &amp; Prediction</Name><Description>Statistically model, describe and predict actions/behaviors and roles/goals of individual entities clusters of entities and even populations</Description><Identifier>_aa3152e4-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>4</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>I've been monkeying around with, researching, prototyping and increasingly involving in deploying or setting policy for deployments of complex data-driven systems that statistically model, describe and predict actions/behaviors and roles/goals of individual entities clusters of entities and even populations in various systems and the sort of info apparently captured in parts of StratML would potentially be really helpful for making that readily actionable by human decision makers including executives, managers, operators and other monitors or explorers of the information.  All those who rely on currently hard to understand displays of real-time or near-realt-time information readouts would have a leg up if this sort of info could be attached to or logically associated with sets of entities in a standard expected way.  The contexts I'd use this for are varied and growing, commonly including city or state resource allocation and service planning, as well as industrial oversight and operations in Telecom, Financial Sector and Entertainment for Medical/Payment/Insurance/Pubic Health, lots of education/research/academic systems and especially in context of B2B standard business practices, operations, supplies and commercial systems.  

As the world becomes a data-driven, connected and digital environment everybody needs easier ways to get from entity *identifiers* in the context of these systems and to a higher quality, more efficient and better fit for purpose displays and descriptions of identity *attributes* relating to expected or assumed purposes, goals and objectives (to judge incentives/aversions and probably reactions to situations) and also more tactical information about capabilities derived from standard listings/labels of anticipated commitments to maintain given levels of performance, expected activities and intended parameters for outputs and other outcomes resulting from actions the entity is responsible to successfully complete.  If we could use an existing standard of a dumbed-down markup language as a start, this sort of meta-data would be a source of fuel for any number of creative algorithms and other analytics potentially enabling generation of key business intelligence and feeding much more effective visualizations and usable interfaces and action-oriented instruments (buttons/knobs/etc) for surviving and thriving in rapidly changing complex business and market landscapes. 

We need to make info about entities computable for purpose and that includes standard ways to express more subtle attributes about strategy, goals, performance, schedules, capabilities, roles, actions and outputs.  To the extent StratML provides a start for some of that, I'd like to test how valuable it could be to wrangle some existing data sets and test how much more insight and potential for better decisions and outcomes may be possible (especially using US Federal agency info but also SEC filings in XBRL, national data on loans, healthcare market info, blockchain sources info and other data sets I've got laying around or in active use and that yearn to be computable in the service of as yet unasked creative questions.</OtherInformation><Objective><Name>Action</Name><Description>Making such data readily actionable by human decision makers including executives, managers, operators and other monitors or explorers of the information.</Description><Identifier>_aa3153d4-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>4.1</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Standardization</Name><Description>Associate such information with sets of entities in a standard expected way.</Description><Identifier>_aa3154e2-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator>4.2</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name/><Description>Enable entity *identifiers* in the context of these systems and to a higher quality, more efficient and better fit for purpose displays and descriptions of identity *attributes* relating to expected or assumed purposes, goals and objectives (to judge incentives/aversions and probably reactions to situations) and also more tactical information about capabilities derived from standard listings/labels of anticipated commitments to maintain given levels of performance, expected activities and intended parameters for outputs and other outcomes resulting from actions the entity is responsible to successfully complete.  </Description><Identifier>_aa3155d2-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator/><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Algorithms, Analytics, Business Intelligence, Visualization &amp; UIs</Name><Description>Fuel creative algorithms and other analytics potentially enabling generation of key business intelligence and feeding much more effective visualizations and usable interfaces and action-oriented instruments (buttons/knobs/etc) for surviving and thriving in rapidly changing complex business and market landscapes.</Description><Identifier>_aa3156d6-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator/><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Computability</Name><Description>Make info about entities computable for purpose and that includes standard ways to express more subtle attributes about strategy, goals, performance, schedules, capabilities, roles, actions and outputs.</Description><Identifier>_aa3157ee-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator/><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Testing</Name><Description>Test how valuable it could be to wrangle some existing data sets and test how much more insight and potential for better decisions and outcomes may be possible</Description><Identifier>_aa3158e8-73e1-11e6-94b1-9c5f42b9d64e</Identifier><SequenceIndicator/><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate>2016-08-19</StartDate><PublicationDate>2016-09-05</PublicationDate><Source>https://groups.google.com/forum/#!topic/Computable/Er9uUnKxQq8</Source><Submitter><GivenName>Owen</GivenName><Surname>Ambur</Surname><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></StrategicPlan>