<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?xml-stylesheet type="text/xsl" href="../part2stratml.xsl"?><StrategicPlan><!--This document transformed using a tool developed by Drybridge Technologies for information navigate to http://www.drybridge.com--><!--The schema posted at http://www.schema-archive.com is provided as a courtesy for on-line validation of various standards. You should verify that the schema provided meets your requirements.--><Name>The Linked Data Ecosystem</Name><StrategicPlanCore><Organization><Name>The Linked Data Ecosystem</Name><Acronym>TLDE</Acronym><Identifier>_bb64ecc5-52a8-414d-8bae-4cd9bd08ce14</Identifier></Organization><Mission><Description>To foster development of a scalable and robust platform for decentralized applications to share data.</Description><Identifier>_64979ccf-08a5-42c9-892c-00799c429fff</Identifier></Mission><Goal><Name>Triples</Name><Description>Present all your data in as triples, building everything out of Subject-Property-Value statements. </Description><Identifier>_700ad037-f69d-4b2c-9716-4c1f4819511a</Identifier><SequenceIndicator>1</SequenceIndicator><OtherInformation>This roughly lines up with rock-solid technologies like relational databases and object-oriented programming, and new techniques, including JSON and terascale databases (Google’s BigTable app engine datastore, Amazon’s SimpleDB). The details are ironed out in RDF, a W3C standard first published in 1999, and then rearticulated with clarification in 2004.When you use triples as your building blocks, you have to be more explicit about the structure of your data, and this eases accurate interoperation. The simplicity also supports metadata, reasoning about data, data distribution, and shared infrastructure even among disparate applications.</OtherInformation></Goal><Goal><Name>Web Addresses</Name><Description>Use Web addresses (URLs/URIs/IRIs) to name things. </Description><Identifier>_7f0e11c4-6abf-43ee-a181-95b5783e3a67</Identifier><SequenceIndicator>2</SequenceIndicator><OtherInformation>Each thing that someone might need to refer to — cities, agencies, people, projects, items in inventory, websites, events, etc — should be assigned a universally unambiguous identifier (nothing else uses the same identifier), so that every source of data about that item can be merged, always knowing it’s the same item. It’s okay (and unavoidable, in some cases) to have multiple identifiers for some items; the important thing is to be able to use the same identifier, when we know it.We use Web addresses to build these identifiers, because we already have a structure for making sure there are no unintended duplicates, and because it allows an important element of of centralization. Each time some organization mints a new web-based identifier, it gets the ability to provide (through its web server) some core data about that item. It’s not that their data will always be correct, but it provides a starting point, a seed around which a shared understanding of the item can grow.</OtherInformation></Goal><Goal><Name>Change and Diversity</Name><Description>Build for change and diversity, with backward and forward compatibility, and multiple views on the same data, knowing that the world changes, and our understanding of the world changes.</Description><Identifier>_9e28acfe-0670-4df4-af85-b77ec6ea3ce0</Identifier><SequenceIndicator>3</SequenceIndicator><OtherInformation>This needs its own article, but Why I Want RIF? covers the hardest parts of the territory.  See http://decentralyze.com/2009/07/09/why-i-want-rif/</OtherInformation></Goal><Goal><Name>Public Data Streams</Name><Description>Get more and more public data streams flowing. </Description><Identifier>_555d52a5-b2e3-4fb1-9f4b-f1548d2fb9af</Identifier><SequenceIndicator>4</SequenceIndicator></Goal><Goal><Name>Usability of Data Stream </Name><Description>Make the data streams more and more usable. </Description><Identifier>_b45d89a7-dcbb-41a0-ad0e-be6866054303</Identifier><SequenceIndicator>5</SequenceIndicator></Goal><Goal><Name>Community Support</Name><Description>Support the Community Around a Data Source</Description><Identifier>_ad0a77d9-bb8b-4a62-b913-ffb2bccc2745</Identifier><SequenceIndicator>6</SequenceIndicator><OtherInformation>People need to see what others are doing, and people doing good things need to be rewarded. People need to have some confidence they’ll be rewarded for doing good things. And mostly: the community needs to be arranged so that the more people participate, the better it gets. (See the video of Clay Shirky’s talk at the Summit about how to do this, in general.)  http://www.blip.tv/file/855937/ </OtherInformation><Objective><Name>Definitions of Elements</Name><Description>Clarify what elements of the data feed mean</Description><Identifier>_30c489aa-ddb1-49ca-aea7-e32b22520c15</Identifier><SequenceIndicator>6.1</SequenceIndicator></Objective><Objective><Name>Documentation</Name><Description>Document the accuracy, methodology, etc, of the feed </Description><Identifier>_099f4d67-1325-4064-9306-4d59516774f3</Identifier><SequenceIndicator>6.2</SequenceIndicator></Objective><Objective><Name>Bugs</Name><Description>Find and correct bugs in the data</Description><Identifier>_18410811-f3f3-479d-84f7-a4702e32d88f</Identifier><SequenceIndicator>6.3</SequenceIndicator></Objective><Objective><Name>Software</Name><Description> Develop software which somehow uses the data, and (1) sharing lessons learned in developing the software, (2) making the software available in various forms (web service, commercial download, open source, etc) </Description><Identifier>_3b058020-8cfe-49a3-9304-5d6c843c5b45</Identifier><SequenceIndicator>6.4</SequenceIndicator></Objective><Objective><Name>Links</Name><Description>Link to related feeds</Description><Identifier>_d9bac687-c3bb-4a48-a014-35c7c123b1ab</Identifier><SequenceIndicator>6.5</SequenceIndicator></Objective><Objective><Name>Derived Feeds</Name><Description>Provide derived feeds, reformat, correct, or otherwise improve or re-target data </Description><Identifier>_1a2fafac-d22c-410d-9ff3-2618e2a0352c</Identifier><SequenceIndicator>6.6</SequenceIndicator></Objective><Objective><Name>Merged Feeds</Name><Description>Provide merged feeds, which process data along with other data, to create something new </Description><Identifier>_8b748b2b-6b7e-4aa0-9d03-ddf44a9151dd</Identifier><SequenceIndicator>6.7</SequenceIndicator></Objective><Objective><Name>Summary and Analysis</Name><Description>Summary/Analysis feeds </Description><Identifier>_655192e9-0e32-49da-84f1-4181207187cf</Identifier><SequenceIndicator>6.8</SequenceIndicator></Objective><Objective><Name>Review and Commentary</Name><Description>Review, commentary, support for all these related items </Description><Identifier>_1ca6c9e8-1cee-4fd4-a67d-50268367e1b6</Identifier><SequenceIndicator>6.9</SequenceIndicator></Objective><Objective><Name>Funding</Name><Description>Create career and project-funding opportunities</Description><Identifier>_780a4dae-de45-4d8b-a8af-47fdbc287870</Identifier><SequenceIndicator>6.10</SequenceIndicator></Objective><Objective><Name>Social Events</Name><Description>Conduct social events related to this feed </Description><Identifier>_a84b6fa8-99e1-41ec-a7ac-67ca1ed1a474</Identifier><SequenceIndicator>6.11</SequenceIndicator></Objective></Goal></StrategicPlanCore><AdministrativeInformation><PublicationDate>2010-02-08</PublicationDate><Source>http://decentralyze.com/2009/09/11/linked-government-data/</Source><Submitter><FirstName>Arthur</FirstName><LastName>Colman (www.drybridge.com)</LastName><EmailAddress>colman@drybridge.com</EmailAddress></Submitter></AdministrativeInformation></StrategicPlan>
