<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="stratml.xsl"?>
<StrategicPlan><id></id><Name>ORGPedia Project</Name><Description></Description><OtherInformation>As a result of the burgeoning movement to open up access to public data, government agencies are making unprecedented quantities of information about regulated businesses available online in reusable formats. From data about corporate compliance with health, environment and safety regulations to data about companies that receive assignments of patents to financial disclosures from publicly traded companies, the opportunity now exists to &#8220;mash up&#8221; and visualize disparate data about organizations. The Numbering Challenge -- Despite the sudden availability of so much data, it is currently impossible to combine this information and transform it into new knowledge about the social life of organizations because of the disparate and non-transparent numbering schemes used for tracking organizations. Today there are multiple schemes in place for entity identification, many of them considered inadequate, some of them proprietary, and none of which &#8220;talk&#8221; to one another. The complexity of corporate structures presents unique challenges in designing a universal mapping (e.g. comparing accounting vs. tax structures). As a result, most systems today serve specific purposes and user communities. The Office of Financial Research has issued an RFC in response to its own stated desire to: &#8220;standardize how parties to financial contracts are identified in the data it collects.&#8221; The Office expressed an explicit &#8220;preference to adopt through rulemaking a universal standard for identifying parties to financial contracts that is established and implemented by private industry and other relevant stakeholders through a consensus process.&#8221; In parallel, the SEC is collaborating in a ISO standard-setting process to develop a legal entity numbering scheme. Currently, Federal agencies alone are spending at least $52.8 million in taxpayer dollars annually on Dun and Bradstreet, the owner of the proprietary identifier system used by many government entities.</OtherInformation><StrategicPlanCore><Organization><Name>ORGPedia</Name><Acronym>ORGP</Acronym><Identifier>_b7672678-8c88-11e0-8b05-734c7a64ea2a</Identifier><Description></Description><Stakeholder><Name></Name><Description></Description></Stakeholder></Organization><Vision><Description>[B]y amassing and visualizing formerly disparate data sets about the ownership, structure, performance and regulatory compliance of organizations, we can achieve reduced compliance and investment costs, improved corporate accountability, greater consumer protection, and create an important new research and reporting test bed that will foster critical, data-driven journalism and scholarship about the life of organizations.</Description><Identifier>_b76728e4-8c88-11e0-8b05-734c7a64ea2a</Identifier></Vision><Mission><Description>To design and create an open corporate identification system.</Description><Identifier>_b76729e8-8c88-11e0-8b05-734c7a64ea2a</Identifier></Mission><Value><Name></Name><Description></Description></Value><Goal><Name>Corporate Identification System</Name><Description>Design and create an open corporate identification system to enable datasets about companies to be compared.</Description><Identifier>_b7672aa6-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>Currently, different agencies use different numbering schemes. An open ID will enable taxonomies to &#8220;talk&#8221; to one another.</OtherInformation><Objective><Name>Assumptions</Name><Description>[Document] assumptions about what must be built.</Description><Identifier>_b7672ba0-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>1.1</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>Some Assumptions About What We Need to Build</OtherInformation></Objective><Objective><Name>Governance Structure</Name><Description>[Build] a multi-disciplinary, independent and legitimate governance structure.</Description><Identifier>_b7672c5e-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>1.1.1</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>1. A multi-disciplinary, independent and legitimate governance structure to oversee the growth and development of the project and to address difficult questions, such as the appropriate policy for enabling correction of inaccurate information, privacy and trade secret protection and strategies to attract engagement and participation.</OtherInformation></Objective><Objective><Name>Network of Experts</Name><Description>[Build] a network of experts who can address policy prescriptions.</Description><Identifier>_b7672d12-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>1.1.2</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>2. A network of experts who can address policy prescriptions for tagging government mandated data collections to ensure that this data can be mashed up.</OtherInformation></Objective><Objective><Name>ID System</Name><Description>[Build] an open, non-proprietary system for assigning unique persistent identifiers for organizations and corporations.</Description><Identifier>_b7672dda-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>1.1.3</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>3. An open, non-proprietary system for assigning unique persistent identifiers for organizations and corporations with whom Federal and state governments interact. These include government contractors, grant recipients, academic institutions, regulated facilities/plants, financial and banking entities, patent holders.</OtherInformation></Objective><Objective><Name>Ownership and Governance Relationships</Name><Description>Enable the public to identify ownership and governance relationships.</Description><Identifier>_b7672ea2-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>1.1.4</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>4. Such a system must enable the public to identify both &#8220;parent&#8221; and &#8220;child&#8221; entities; ownership and governance relationships. We need to be able to track changes over time; e.g. changes in ownership, joint ventures and mergers, births and deaths of entities, name changes, state registrations, doing business as names and related trademarks.</OtherInformation></Objective><Objective><Name>Persistence and Interoperability</Name><Description>Provide a persistent and universal federal identifier and interoperate with other common domestic and international identifier schemes.</Description><Identifier>_b7672f74-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>1.1.5</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>5. This taxonomy must both provide a persistent and universal federal identifier and, at the same time, interoperate with other common domestic and international identifier schemes used in legacy systems, such as: * IRS EINs * DUNS numbers * CUSIPS * Census identifiers</OtherInformation></Objective><Objective><Name>Universality and Interoperability</Name><Description>[Build] both a universal identifier and a system that allows other common numbering schemes to interoperate.</Description><Identifier>_b7673050-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>1.1.6</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>6. As these disparate efforts proceed, we want to be sure that we are not further entrenching ourselves in systems that don&#700;t allow indicators to &#8220;talk to&#8221; one another. We want to be sure that we have both a universal identifier and a system that allows other common numbering schemes to interoperate.</OtherInformation></Objective><Objective><Name>Extensibility and Participation</Name><Description>Design an extensible system that will encourage others to participate</Description><Identifier>_b7673140-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>1.1.7</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>7. Since all such numbering schemes cannot be identified up front, we want to design an extensible system that will encourage others to participate in the ecosystem. It should support linking, tagging and enhancements for scalability.</OtherInformation></Objective><Objective><Name>Data Dictionary</Name><Description>Develop a data dictionary to standardize approaches to dealing with different terms.</Description><Identifier>_b7673230-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>1.1.8</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>8. ORGPedia will develop a data dictionary to standardize approaches to dealing with different terms, such as Inc. and Incorporated, abbreviations and other common elements in the description of organizations.</OtherInformation></Objective><Objective><Name>Data Harvesting Tools</Name><Description>Help develop tools by which data can be harvested from federal and state databases using web services approaches.</Description><Identifier>_b767332a-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>1.1.9</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>9. This standardization will help with developing tools by which data can be harvested from federal and state databases using web services approaches. A web services/linked data approach will help to power organizational lookups and thereby improve accuracy and reliability.</OtherInformation></Objective><Objective><Name>Simplicity and Standards</Name><Description>[Make] the numbering standard and the website itself lightweight and standards-based.</Description><Identifier>_b7673424-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>1.1.10</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>10. Both the numbering standard and the website itself should be lightweight and standards-based. We should build quickly and grow the system rather than anticipate every eventuality.</OtherInformation></Objective><Objective><Name>Numbering Scheme</Name><Description>Offer an open numbering scheme to organize and structure authenticated data about corporations scraped from government databases.</Description><Identifier>_b767353c-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>1.1.11</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>11. At its core, ORGPedia will offer an open numbering scheme to organize and structure authenticated data about corporations scraped from government databases. This will enable the data presented to be used for systematic research. At the same time, ORGPedia will enlist public participation to review data quality and spot errors in public data sets as well as to contribute additional data (e.g. about a company&#700;s products, its sustainability or child labor practices).</OtherInformation></Objective></Goal><Goal><Name>Online Platform</Name><Description>Design and create an online platform to mash up and visualize authenticated government datasets already collected about firms and organizations pursuant to statute or regulation.</Description><Identifier>_b7673654-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation></OtherInformation><Objective><Name></Name><Description></Description><Identifier>_b7673780-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator></SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation></OtherInformation></Objective></Goal><Goal><Name>API</Name><Description>Design and create an Application Programming Interface (API) and supporting software libraries to make it easy for third parties to incorporate ORGPedia into their own systems.</Description><Identifier>_b76738b6-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>3</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation></OtherInformation><Objective><Name></Name><Description></Description><Identifier>_b7673a00-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator></SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation></OtherInformation></Objective></Goal><Goal><Name>Community</Name><Description>Design and create a community to encourage public participation in reviewing, annotating and contributing to collected government data whether by companies and organizations or by third parties.</Description><Identifier>_b7673b36-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>4</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation></OtherInformation><Objective><Name>Workshops</Name><Description>Host five workshops.</Description><Identifier>_b7673c76-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>4.1</SequenceIndicator><Stakeholder><Name>Institute for Information Law and Policy</Name><Description>The Institute for Information Law and Policy is hosting 5 workshops to bring together experts whose know-how will be vital to designing a successful open corporate intelligence system.</Description></Stakeholder><OtherInformation>The aim of these workshops is to understand the needs of these different communities; elicit the questions that must be addressed for the project to succeed; identify interested partners; and draft a specification for the development of ORGPedia. Each workshop will discuss design, and governance and also have a specific thematic focus.</OtherInformation></Objective><Objective><Name>Opportunities and Impediments</Name><Description>Address the impact on government and research as well as who needs to participate.</Description><Identifier>_b7673dd4-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>4.1.1</SequenceIndicator><Stakeholder><Name>SLOAN FOUNDATION</Name><Description></Description></Stakeholder><OtherInformation>SLOAN FOUNDATION, MARCH 30 &#8211; Opportunities and Impediments &#8211; will address the impact on government and research as well as who needs to participate in order to sustain a legitimate and robust platform and community.</OtherInformation></Objective><Objective><Name>Accountability, Open Data, and Open IDs</Name><Description>Promote corporate accountability with open data and open identifiers.</Description><Identifier>_b7673f28-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>4.1.2</SequenceIndicator><Stakeholder><Name>SUNLIGHT FOUNDATION</Name><Description></Description></Stakeholder><OtherInformation>SUNLIGHT FOUNDATION, APRIL 8 &#8211; Promoting Corporate Accountability with Open Data and Open Identifiers &#8211; will bring together regulators and groups with an interest in corporate compliance to discuss the impact of the project on government and consumers.</OtherInformation></Objective><Objective><Name>Open Business Intelligence</Name><Description>Convene those who create and those who depend upon business intelligence in the financial services community to articulate what&#700;s needed.</Description><Identifier>_b767409a-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>4.1.3</SequenceIndicator><Stakeholder><Name>Financial Services Community</Name><Description></Description></Stakeholder><OtherInformation>Open Business Intelligence in the 21st Century &#8211; will convene those who create and those who depend upon business intelligence in the financial services community to articulate what&#700;s needed.</OtherInformation></Objective><Objective><Name>Numbering Ontology and Platform</Name><Description>Design a numbering ontology and platform.</Description><Identifier>_b767420c-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>4.1.4</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>Designing an Open Numbering Ontology and Platform &#8211; will focus on refining the specification and identifying candidate technologies.</OtherInformation></Objective><Objective><Name>International Challenges</Name><Description>Take the discussion outside the United States and test the assumptions developed.</Description><Identifier>_b7674392-8c88-11e0-8b05-734c7a64ea2a</Identifier><SequenceIndicator>4.1.5</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>International Challenges &#8211; will take the discussion outside the United States and test the assumptions developed until this point. This workshop will be held in London.</OtherInformation></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate></StartDate><EndDate></EndDate><PublicationDate>2011-06-02</PublicationDate><Source>http://dotank.nyls.edu/orgpedia-files/backgrounder.pdf</Source><Submitter><FirstName>Owen</FirstName><LastName>Ambur</LastName><PhoneNumber></PhoneNumber><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></StrategicPlan>