<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (rybesh)</title>
    <link>https://pinboard.in/u:rybesh/public/</link>
    <description>recent bookmarks from rybesh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://scholarsphere.psu.edu/resources/39688670-949f-4223-a31c-41afbade9135"/>
	<rdf:li rdf:resource="https://github.com/DigiClass/LOD-People/tree/main/sample-data"/>
	<rdf:li rdf:resource="https://github.com/NatLibFi/Skosmos/wiki/Data-Model#deprecated-concepts"/>
	<rdf:li rdf:resource="https://ontobee.org/"/>
	<rdf:li rdf:resource="https://queerdata.forummuenchen.org/en/"/>
	<rdf:li rdf:resource="https://rdf-vocabulary.ddialliance.org/xkos.html"/>
	<rdf:li rdf:resource="https://zenodo.org/record/4953986#.Ydi4pi-B3Ra"/>
	<rdf:li rdf:resource="https://littlesis.org/"/>
	<rdf:li rdf:resource="https://periodo.github.io/edtf-ontology/"/>
	<rdf:li rdf:resource="https://github.com/periodo/edtf-ontology"/>
	<rdf:li rdf:resource="https://twitter.com/rybesh/status/1417207816482398221/photo/1"/>
	<rdf:li rdf:resource="https://github.com/periodo/edtf-ontology/discussions"/>
	<rdf:li rdf:resource="http://gams.uni-graz.at/archive/objects/o:depcha.bookkeeping/methods/sdef:Ontology/get"/>
	<rdf:li rdf:resource="http://www.commonsemantics.com/oa/Open%20Annotation%20Data%20Model%20Primer.html"/>
	<rdf:li rdf:resource="https://pleiades.stoa.org/vocabularies/"/>
	<rdf:li rdf:resource="https://github.com/isawnyu/pleiades-geographer/blob/1af9d06e53e590df6376c24121e4acb5c1b847e3/pleiades/geographer/geo.py#L555-L629"/>
	<rdf:li rdf:resource="https://clld.org/"/>
	<rdf:li rdf:resource="https://shapetrees.github.io/specification/primer"/>
	<rdf:li rdf:resource="https://journal.code4lib.org/articles/14978"/>
	<rdf:li rdf:resource="https://id.ndl.go.jp/information/about_en/"/>
	<rdf:li rdf:resource="https://journal.code4lib.org/articles/14711"/>
	<rdf:li rdf:resource="https://web.archive.org/web/20061115043657/https://www.w3.org/DesignIssues/LinkedData.html"/>
	<rdf:li rdf:resource="https://github.com/priyaradhakrishnan0/ELDEN"/>
	<rdf:li rdf:resource="https://twitter.com/i/web/status/1095484856363085824"/>
	<rdf:li rdf:resource="http://rml.io/yarrrml/"/>
	<rdf:li rdf:resource="https://www.project-freya.eu/en/deliverables/freya_d3-1.pdf"/>
	<rdf:li rdf:resource="https://github.com/LinkedPasts/linked-places"/>
	<rdf:li rdf:resource="http://www.rdfhdt.org/datasets/"/>
	<rdf:li rdf:resource="http://hypergraphql.org/"/>
	<rdf:li rdf:resource="https://www.loc.gov/aba/pcc/bibframe/TaskGroups/formulate_obtain_URI_guide.pdf"/>
	<rdf:li rdf:resource="http://bibfra.me/"/>
	<rdf:li rdf:resource="http://gbv.github.io/beaconspec/beacon.html"/>
	<rdf:li rdf:resource="https://github.com/dhlab-epfl/LinkedBooksMonographs/tree/v1.0"/>
	<rdf:li rdf:resource="http://wiki.dublincore.org/index.php/User_Guide/Publishing_Metadata#dcterms:language"/>
	<rdf:li rdf:resource="http://open-services.net/"/>
	<rdf:li rdf:resource="http://baskauf.blogspot.com/2016/10/linked-data-magic-and-big-data.html"/>
	<rdf:li rdf:resource="http://topbraid.org/spin/rdfsplus.html"/>
	<rdf:li rdf:resource="http://linkeddata.uriburner.com:8000/vapour"/>
	<rdf:li rdf:resource="http://graphite.ecs.soton.ac.uk/checker/"/>
	<rdf:li rdf:resource="http://www.linkedmodel.org/doc/2015/SCHEMA_vaem-v2.0"/>
	<rdf:li rdf:resource="http://linkeddata.uriburner.com/"/>
	<rdf:li rdf:resource="https://www.w3.org/TR/sdw-bp/"/>
	<rdf:li rdf:resource="https://www.w3.org/TR/webmention/"/>
	<rdf:li rdf:resource="https://developers.google.com/knowledge-graph/"/>
	<rdf:li rdf:resource="http://osds.openlinksw.com/"/>
	<rdf:li rdf:resource="http://lov.okfn.org/dataset/lov"/>
	<rdf:li rdf:resource="http://validator.lod-cloud.net/"/>
	<rdf:li rdf:resource="http://www.w3.org/TR/vocab-duv/"/>
	<rdf:li rdf:resource="https://github.com/wragge/lod-books-viewer"/>
	<rdf:li rdf:resource="http://www.w3.org/TR/ldpatch/"/>
	<rdf:li rdf:resource="http://enable-cors.org/"/>
	<rdf:li rdf:resource="http://www.w3.org/Submission/2014/SUBM-shex-primer-20140602/"/>
	<rdf:li rdf:resource="http://www.w3.org/Submission/2014/SUBM-shapes-20140211/"/>
	<rdf:li rdf:resource="https://github.com/cognitect/transit-format#extensibility"/>
	<rdf:li rdf:resource="https://code.google.com/p/void-impl/wiki/SPARQLQueriesForStatistics"/>
	<rdf:li rdf:resource="https://github.com/geojson/geojson-ld/blob/master/time.md"/>
	<rdf:li rdf:resource="https://github.com/LinkedDataFragments/Client"/>
	<rdf:li rdf:resource="http://vimeo.com/36752317"/>
	<rdf:li rdf:resource="http://sites.tufts.edu/liam/2014/02/03/glossary/"/>
	<rdf:li rdf:resource="http://berjon.com/blog/2013/06/linked-data.html"/>
	<rdf:li rdf:resource="http://ribs.csres.utexas.edu/nosqlrdf/nosqlrdf_iswc2013.pdf"/>
	<rdf:li rdf:resource="http://www.w3.org/TR/ldp-ucr/"/>
	<rdf:li rdf:resource="https://github.com/pelagios/pelagios-cookbook/wiki/Pelagios-Gazetteer-Interconnection-Format"/>
	<rdf:li rdf:resource="http://www.morganclaypool.com/doi/abs/10.2200/S00498ED1V01Y201304WBE006"/>
	<rdf:li rdf:resource="http://lists.w3.org/Archives/Public/public-ldp/2013Mar/0112.html"/>
	<rdf:li rdf:resource="http://jenit.github.io/linked-csv/"/>
	<rdf:li rdf:resource="http://openpoi.ogcnetwork.net/"/>
	<rdf:li rdf:resource="http://www.ddialliance.org/system/files/UsingRDFToDescribeAndLinkSocialScienceDataToRelatedResourcesOnTheWeb.pdf"/>
	<rdf:li rdf:resource="http://www.wikidata.org/wiki/Wikidata:Main_Page"/>
	<rdf:li rdf:resource="https://www.wikidata.org/wiki/Wikidata:List_of_properties"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://scholarsphere.psu.edu/resources/39688670-949f-4223-a31c-41afbade9135">
    <title>Hollinger's Edge: The Retrieval Object at the Margins of the Archival Ontology</title>
    <dc:date>2025-12-01T19:11:11+00:00</dc:date>
    <link>https://scholarsphere.psu.edu/resources/39688670-949f-4223-a31c-41afbade9135</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Archival resources are frequently described in two parallel representations: as intellectual groupings that facilitate discovery, and as physical inventories that facilitate retrieval and requesting. At the time a researcher requests to use material, it must be possible to map the intellectual grouping to the corresponding retrieval object. In this paper, we analyze three emerging archival linked data standards (BIBFRAME-ARM, Records in Contexts, and Linked.Art) from the perspective of retrieval. We find that only Linked.Art is currently capable of representing retrieval objects natively, and that neither BIBFRAME-ARM nor Records in Contexts are semantically interoperable with archival inventory management or requesting.]]></description>
<dc:subject>archives linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f8cd98bbfbcb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/DigiClass/LOD-People/tree/main/sample-data">
    <title>LOD-People/sample-data at main · DigiClass/LOD-People</title>
    <dc:date>2025-08-11T15:51:46+00:00</dc:date>
    <link>https://github.com/DigiClass/LOD-People/tree/main/sample-data</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This directory contains sample person data in a range of (currently unspecified) open formats. Data needs to be open licensed, or a sample published under an open license with permission of the rightsholder.]]></description>
<dc:subject>people modeling linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7dba411e36fd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:people"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/NatLibFi/Skosmos/wiki/Data-Model#deprecated-concepts">
    <title>Data Model · NatLibFi/Skosmos Wiki</title>
    <dc:date>2025-08-11T15:45:03+00:00</dc:date>
    <link>https://github.com/NatLibFi/Skosmos/wiki/Data-Model#deprecated-concepts</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Deprecated concepts are concepts that are no longer valid but are kept in the vocabulary for backward compatibility. Skosmos can detect that a concept has been deprecated if the concept data includes:

owl:deprecated true metadata
optionally, dcterms:isReplacedBy relationships pointing to the concepts (one or multiple) that replace this one
Example:

ex:old a skos:Concept ;
  owl:deprecated true ;
  skos:prefLabel "Old concept that has been replaced by a new concept"@en ;
  dct:isReplacedBy ex:new .
Deprecated concepts will not be visible in the alphabetical listing, in the hierarchical view, and cannot be found with the search, unless the option skosmos:showDeprecated is set to true in the vocabularies configuration file. However, deprecated concepts can still be accessed through their URI in both the web user interface and the API.

The concept page of a deprecated concept includes a notification element that informs the user that the concept has been deprecated, and if possible links to the concept that should be used instead (The following link illustrates how Skosmos visualizes deprecated concepts: http://finto.fi/yso/en/page/p3410).]]></description>
<dc:subject>linkeddata deprecation periodo</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:de061b319bb2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:deprecation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:periodo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://ontobee.org/">
    <title>Ontobee</title>
    <dc:date>2022-10-25T22:34:13+00:00</dc:date>
    <link>https://ontobee.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A linked data server designed for ontologies. Ontobee is aimed to facilitate ontology data sharing, visualization, query, integration, and analysis. Ontobee dynamically dereferences and presents individual ontology term URIs to (i) HTML web pages for user-friendly web browsing and navigation, and to (ii) RDF source code for Semantic Web applications. Ontobee is the default linked data server for most OBO Foundry library ontologies. Ontobee has also been used for many non-OBO ontologies.]]></description>
<dc:subject>semanticweb linkeddata ontology catalogs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2ee0cc452a84/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semanticweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:catalogs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://queerdata.forummuenchen.org/en/">
    <title>Remove NA</title>
    <dc:date>2022-10-09T20:17:08+00:00</dc:date>
    <link>https://queerdata.forummuenchen.org/en/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Remove NA project links data science and domain knowledge with the goal of weaving queer data into the web of open, linked data.

]]></description>
<dc:subject>linkeddata history archives inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:aed151c4dfcf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://rdf-vocabulary.ddialliance.org/xkos.html">
    <title>XKOS</title>
    <dc:date>2022-08-14T18:05:58+00:00</dc:date>
    <link>https://rdf-vocabulary.ddialliance.org/xkos.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Semantic technology associated with Linked Open Data (LOD) is gaining much broader use and acceptance. Marrying LOD techniques to those of the international statistical community is the goal. Specifically, the use of the Simple Knowledge Organization System ([SKOS]) for managing statistical classifications and concept management systems is addressed, since SKOS is widely used. LOD is used to create Web artifacts that machines can interpret, so publishing machine readable statistical classifications and other concept management systems as SKOS instances is desired. We found that SKOS is insufficient for the problem. No aspect of SKOS was found to be wrong, just incomplete. Therefore, we propose an extension to SKOS, which we call XKOS.]]></description>
<dc:subject>skos linkeddata vocabulary statistics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c335a595c547/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:skos"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:vocabulary"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:statistics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://zenodo.org/record/4953986#.Ydi4pi-B3Ra">
    <title>WorldKG | Zenodo</title>
    <dc:date>2022-01-08T00:33:46+00:00</dc:date>
    <link>https://zenodo.org/record/4953986#.Ydi4pi-B3Ra</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The WorldKG knowledge graph is a comprehensive large-scale geospatial knowledge graph based on OpenStreetMap that provides a semantic representation of geographic entities from over 188 countries. WorldKG contains a higher number of representations of geographic entities compared to other knowledge graphs and can be used as an underlying data source for various applications such as geospatial question answering, geospatial data retrieval, and other cross-domain semantic data-driven applications.]]></description>
<dc:subject>ncgazetteer geospatial linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:73fd672506a6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ncgazetteer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:geospatial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://littlesis.org/">
    <title>LittleSis - Profiling the powers that be</title>
    <dc:date>2021-09-21T20:20:58+00:00</dc:date>
    <link>https://littlesis.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[LittleSis features interlinked profiles of powerful individuals and organizations in the public and private sectors. Profiles detail a wealth of information vital to any investigation of the ways power and money guide the formulation of public policy, from board memberships to campaign contributions, old school ties to government contracts.

The site currently offers profiles of over 185,000 people and 67,000 organizations in varying stages of completion. These include, but are not limited to:

Politicians: members of Congress since 1979, governors since 1974, Bush and Obama administration officials.
Business people: Fortune 1000 executives and directors, members of the Forbes 400.
Lobbyists who have lobbied on behalf of Fortune 1000 companies.
Government bodies: US House & Senate; agencies ranging from the Department of Defense to the IRS.
Businesses: Fortune 1000 companies, lobbying firms, top law firms, and other private companies.
Non-profits such as foundations, think tanks, and political organizations.]]></description>
<dc:subject>politics data tools analytics linkeddata capitalism networks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:07a007f3d901/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:analytics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:capitalism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:networks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://periodo.github.io/edtf-ontology/">
    <title>Extended Date/Time Format (EDTF) concepts</title>
    <dc:date>2021-07-19T19:40:48+00:00</dc:date>
    <link>https://periodo.github.io/edtf-ontology/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Presenting at #ld42021 on some of the #EDTF as #LinkedData work I've been doing: 

Here's a draft ontology for modeling EDTF expressions using OWL-Time: 

Some of the reasoning behind it is explained here:  ]]></description>
<dc:subject>ld42021 LinkedData EDTF</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:913ec0a3d24d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ld42021"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:LinkedData"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:EDTF"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/periodo/edtf-ontology">
    <title>Untitled (https://github.com/periodo/edtf-ontology)</title>
    <dc:date>2021-07-19T19:40:48+00:00</dc:date>
    <link>https://github.com/periodo/edtf-ontology</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Presenting at #ld42021 on some of the #EDTF as #LinkedData work I've been doing: 

Here's a draft ontology for modeling EDTF expressions using OWL-Time: 

Some of the reasoning behind it is explained here:  ]]></description>
<dc:subject>ld42021 LinkedData EDTF</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d31e049b784a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ld42021"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:LinkedData"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:EDTF"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://twitter.com/rybesh/status/1417207816482398221/photo/1">
    <title>(400) https://twitter.com/rybesh/status/1417207816482398221/photo/1</title>
    <dc:date>2021-07-19T19:40:48+00:00</dc:date>
    <link>https://twitter.com/rybesh/status/1417207816482398221/photo/1</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Presenting at #ld42021 on some of the #EDTF as #LinkedData work I've been doing: 

Here's a draft ontology for modeling EDTF expressions using OWL-Time: 

Some of the reasoning behind it is explained here:  ]]></description>
<dc:subject>ld42021 LinkedData EDTF</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:08dcad2b02d9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ld42021"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:LinkedData"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:EDTF"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/periodo/edtf-ontology/discussions">
    <title>Untitled (https://github.com/periodo/edtf-ontology/discussions)</title>
    <dc:date>2021-07-19T19:40:48+00:00</dc:date>
    <link>https://github.com/periodo/edtf-ontology/discussions</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Presenting at #ld42021 on some of the #EDTF as #LinkedData work I've been doing: 

Here's a draft ontology for modeling EDTF expressions using OWL-Time: 

Some of the reasoning behind it is explained here:  ]]></description>
<dc:subject>ld42021 LinkedData EDTF</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:46bee6cca48c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ld42021"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:LinkedData"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:EDTF"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gams.uni-graz.at/archive/objects/o:depcha.bookkeeping/methods/sdef:Ontology/get">
    <title>DEPCHA - Digital Edition Publishing Cooperative for Historical Accounts</title>
    <dc:date>2021-03-13T15:52:27+00:00</dc:date>
    <link>http://gams.uni-graz.at/archive/objects/o:depcha.bookkeeping/methods/sdef:Ontology/get</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The "Bookkeeping Ontology", a conceptual model being based on the REA model and CIDOC CRM, is developed in an ontology engineering process in which historians, software developers and digital humanists were involved. It formalizes the interpretation of a transaction (bk:Transaction) as combination of transfers (bk:Transfer) of measurable objects (bk:Measurable) from one accounting object (bk:Between) to another. bk:Between defines an abstract class, which unites bookkeeping categories (bk:Accounts,e.g. a cash account) and actors (individual bk:Partye.g. Washington or an unknown group of individuals bk:Group e.g. four farmers). Its physical representation in a historical source is an entry in a written accounting record (bk:Entry). The bk:Entry is an information fragment of a bk:Transaction often naming only one party, while the other party is implicit in the textual context of the entry. Further information on the temporal (bk:when), spatial (bk:where) dimension of a bk:Transaction as, well as the status (bk:status) of it (e.g. "partly paid", "settled"), can be expressed optionally. In regard to a research question a bk:Transaction can be assigned to a specific context. Every transaction consists (bk:consistsOf) at least one transfer (bk:Transfer). A single bk:Transfer describes the action of transferring a bk:Measurable in one direction (bk:from or bk:to). bk:Measurable is defined as everything that can be quantified. It has subclasses for economic goods (bk:EconomicGood, as labor: bk:Service or as physical things: bk:Commodity) and money (bk:MonetaryValues). bk:Measurable is describe by its quantity (bk:quantity) and the unit of calculation (bk:unit). The bk:Entry is described by the transcription fragment of the original source (bk:text). bk:EconomicGoodscan be categorized (what is measured) and can be assigned a price. A bk:Transfercan be carried out by (bk:by) someone who conducts the transfer process in place of the business partner (bk:Agent). When writing it down into the ledger, accounting categories (bk:debit and bk:credit) are coded optionally.]]></description>
<dc:subject>business accounting history ontology modeling linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cee464724981/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accounting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.commonsemantics.com/oa/Open%20Annotation%20Data%20Model%20Primer.html">
    <title>Open Annotation Draft Data Model</title>
    <dc:date>2021-02-22T18:48:12+00:00</dc:date>
    <link>http://www.commonsemantics.com/oa/Open%20Annotation%20Data%20Model%20Primer.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document provides an intuitive introduction and guide to the Open Annotation Data Model [OA-DM], an interoperable framework for creating associations between related resources, annotations, using a methodology which conforms to the Architecture of the World Wide Web. This primer explains the fundamental Open Annotation Data Model concepts and provides examples of its use. The primer is intended as a starting point for those wishing to create or use Open Annotation Data Model compliant annotation data.

]]></description>
<dc:subject>annotation standards tutorial linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:86c0beb60ec5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:annotation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://pleiades.stoa.org/vocabularies/">
    <title>Pleiades Vocabularies</title>
    <dc:date>2021-01-15T15:02:09+00:00</dc:date>
    <link>https://pleiades.stoa.org/vocabularies/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Controlled vocabularies employed by Pleiades including time periods and place categories]]></description>
<dc:subject>gazetteer ncgazetteer linkeddata modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:16f6ce7fa935/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:gazetteer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ncgazetteer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/isawnyu/pleiades-geographer/blob/1af9d06e53e590df6376c24121e4acb5c1b847e3/pleiades/geographer/geo.py#L555-L629">
    <title>How Pleiades sets representative points for places without geometry</title>
    <dc:date>2021-01-15T15:01:03+00:00</dc:date>
    <link>https://github.com/isawnyu/pleiades-geographer/blob/1af9d06e53e590df6376c24121e4acb5c1b847e3/pleiades/geographer/geo.py#L555-L629</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[There's a cascading set of selection criteria for connection types to use in the absence of published location objects for the place.

For Magnesia, it's using a subset of the inbound connections: those with type "part of (regional)":
https://pleiades.stoa.org/places/540923

The map shows all the inbound connections with green bowties, so you get not only the markers for "part of (regional)" that were used for reprPoint calc, but also "bounds" and the one "founded by" across to Aegean to the east (that's Magnesia on the Meander).]]></description>
<dc:subject>gazetteer ncgazetteer modeling linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e3a253cefc51/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:gazetteer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ncgazetteer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://clld.org/">
    <title>CLLD - Cross-Linguistic Linked Data</title>
    <dc:date>2021-01-04T22:58:50+00:00</dc:date>
    <link>https://clld.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Cross-Linguistic Linked Data project is developing and curating interoperable data publication structures using Linked Data principles as integration mechanism for distributed resources.

]]></description>
<dc:subject>linguistics database linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1e16878cd2c6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linguistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://shapetrees.github.io/specification/primer">
    <title>Shape Trees Primer</title>
    <dc:date>2020-11-02T22:16:44+00:00</dc:date>
    <link>https://shapetrees.github.io/specification/primer</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This primer introduces shape trees and describes how Semantic Web Applications use them to consistently interoperate over constellations of data structures organized in resource hierarchies used by protocols such as LDP and Solid.]]></description>
<dc:subject>linkeddata SHACL rdf standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c0f28ee2cb24/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:SHACL"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://journal.code4lib.org/articles/14978">
    <title>The Code4Lib Journal – Persistent identifiers for heritage objects</title>
    <dc:date>2020-02-17T21:36:54+00:00</dc:date>
    <link>https://journal.code4lib.org/articles/14978</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Persistent identifiers (PID’s) are essential for getting access and referring to library, archive and museum (LAM) collection objects in a sustainable and unambiguous way, both internally and externally. Heritage institutions need a universal policy for the use of PID’s in order to have an efficient digital infrastructure at their disposal and to achieve optimal interoperability, leading to open data, open collections and efficient resource management.

Here the discussion is limited to PID’s that institutions can assign to objects they own or administer themselves. PID’s for people, subjects etc. can be used by heritage institutions, but are generally managed by other parties.

The first part of this article consists of a general theoretical description of persistent identifiers. First of all, I discuss the questions of what persistent identifiers are and what they are not, and what is needed to administer and use them. The most commonly used existing PID systems are briefly characterized. Then I discuss the types of objects PID’s can be assigned to. This section concludes with an overview of the requirements that apply if PIDs should also be used for linked data.

The second part examines current infrastructural practices, and existing PID systems and their advantages and shortcomings. Based on these practical issues and the pros and cons of existing PID systems a list of requirements for PID systems is presented which is used to address a number of practical considerations. This section concludes with a number of recommendations.]]></description>
<dc:subject>identifiers linkeddata culturalheritage</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d248f7a57257/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:culturalheritage"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://id.ndl.go.jp/information/about_en/">
    <title>About Web NDL Authorities « Web NDL Authoritiesについて</title>
    <dc:date>2019-10-09T23:59:46+00:00</dc:date>
    <link>https://id.ndl.go.jp/information/about_en/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Web NDL Authorities is a service by the National Diet Library (NDL), Japan, to access authority data created and maintained by the NDL.

In addition to being able to search authority data via “keyword search”, “classification number search” and “authority ID search”, you can download individual files of all types of the authority data and batch files of the National Diet Library Subject Headings (NDLSH).

Web NDL Authorities provides a variety of search functions, including search for the relevant bibliographic data by author or subject headings in collaboration with NDL Search.

Web NDL Authorities is based technically on the Semantic Web, which assigns semantically clear data to information resources on the Web. Each record in the authority data can be referenced via a URI in conformance to the Resource Description Framework (RDF) data model, and is searchable via SPARQL.

Authority data is automatically updated daily with new additions, corrections, and deletions. Additionally, notifications are provided via RSS feed for newly established subject headings within the NDLSH.]]></description>
<dc:subject>japan linkeddata libraries authority</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:807c21059dc9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:japan"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authority"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://journal.code4lib.org/articles/14711">
    <title>The Code4Lib Journal – Design reusable SHACL shapes and implement a linked data validation pipeline</title>
    <dc:date>2019-08-14T10:53:20+00:00</dc:date>
    <link>https://journal.code4lib.org/articles/14711</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In July 2017, W3C published SHACL as the standard to validate RDF. Since then, data modellers have the possibility to provide validation services based on SHACL shapes together with their models, however there are considerations to be taken in account when creating them. This paper aims to list such considerations and shows an example of a validation pipeline to address them.]]></description>
<dc:subject>linkeddata shacl validation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:41b8e0dbfa1f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:shacl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:validation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://web.archive.org/web/20061115043657/https://www.w3.org/DesignIssues/LinkedData.html">
    <title>Linked Data - Design Issues</title>
    <dc:date>2019-04-22T16:01:25+00:00</dc:date>
    <link>https://web.archive.org/web/20061115043657/https://www.w3.org/DesignIssues/LinkedData.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Original post on “Linked Data” by TBL.]]></description>
<dc:subject>linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:00279fd3993c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/priyaradhakrishnan0/ELDEN">
    <title>priyaradhakrishnan0/ELDEN</title>
    <dc:date>2019-04-01T12:02:36+00:00</dc:date>
    <link>https://github.com/priyaradhakrishnan0/ELDEN</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Entity Linking (EL) systems aim to automati- cally map mentions of an entity in text to the corresponding entity in a Knowledge Graph (KG). Degree of connectivity of an entity in the KG directly affects an EL system’s abil- ity to correctly link mentions in text to the entity in KG. This causes many EL systems to perform well for entities well connected to other entities in KG, bringing into focus the role of KG density in EL. In this paper, we propose Entity Linking using Densified Knowledge Graphs (ELDEN). ELDEN is an EL system which first densifies the KG with co-occurrence statistics from a large text cor- pus, and then uses the densified KG to train entity embeddings. Entity similarity measured using these trained entity embeddings result in improved EL. ELDEN outperforms state- of-the-art EL system on benchmark datasets. Due to such densification, ELDEN performs well for sparsely connected entities in the KG too. ELDEN’s approach is simple, yet effec- tive. We have made ELDEN’s code and data publicly available.]]></description>
<dc:subject>nlp entitydetection linkeddata extraction</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2472d80dd871/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nlp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:entitydetection"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:extraction"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://twitter.com/i/web/status/1095484856363085824">
    <title>Twitter</title>
    <dc:date>2019-02-13T23:53:09+00:00</dc:date>
    <link>https://twitter.com/i/web/status/1095484856363085824</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[RT @susanirenebrown: The LINCS #LinkedData Cyberinfrastructure project will convert, connect, enhance, & make accessible heterogeneous a… ]]></description>
<dc:subject>LinkedData</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a18712633efb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:LinkedData"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://rml.io/yarrrml/">
    <title>YARRRML</title>
    <dc:date>2018-10-30T01:15:40+00:00</dc:date>
    <link>http://rml.io/yarrrml/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[YARRRML is a human readable text-based representation for declarative Linked Data generation rules. It is a subset of YAML, a widely used data serialization language designed to be human-friendly. It can already be used to represent R2RML and RML rules.]]></description>
<dc:subject>linkeddata tools inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:41cd613e4026/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.project-freya.eu/en/deliverables/freya_d3-1.pdf">
    <title>Survey of Current PID Services Landscape</title>
    <dc:date>2018-09-19T20:17:00+00:00</dc:date>
    <link>https://www.project-freya.eu/en/deliverables/freya_d3-1.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Partner organisations involved in the FREYA project were briefed to provide, within the first six months of the project, an assessment of the landscape of established and emerging persistent identifiers (PIDs) used in scholarly research at the time. This is important because seeking PID maturity (consensus around what specifically needs identifying and which PID type is most relevant to assign to an entity), linking PIDs across entities; and growing overlay services and the PID infrastructure will enable increased discoverability of research outputs themselves, as well as an understanding of the return on research investments.

FREYA partners include “big data” producers and handlers as well as publishers, and represent a diverse array of research disciplines including the life sciences, physical, environmental and social sciences, arts and humanities, in Europe and more globally.

The evaluation has been distilled into a report comprised of a landscape scan and a maturity matrix evaluation of PID services.]]></description>
<dc:subject>identifiers linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0a5525390b71/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/LinkedPasts/linked-places">
    <title>LinkedPasts/linked-places: Linked Places format and Annotation model</title>
    <dc:date>2018-09-19T20:02:55+00:00</dc:date>
    <link>https://github.com/LinkedPasts/linked-places</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Linked Places format supercedes the Pelagios Gazetteer Interconnection Format (PGIF) as a template for contributions to both Pelagios and World-Historical Gazeetteer. Although these place data aggregation projects have distinctive features, both are building software tools and services to allow everyone to:

search across different gazetteers
find enough information to identify and disambiguate places
annotate data with stable URIs to the most appropriate gazetteer
Our goal is not to define The One unified data model to represent gazetteers. Historical research projects producing gazetteer data have distinctive data models reflecting their source data and project-specific requirements. Linked Places format provides a uniform way to build links between different gazetteers, along with just enough additional metadata to support the three requirements above.

The Linked Places format and the earlier PGIF are both valid RDF, the cornerstone format for Linked Open Data and the Semantic Web. Linked Places differs from PGIF in these ways:


it is designed primarily around JSON-LD syntax, which makes it both valid RDF (XML, Turtle, etc.) and JSON
it is valid GeoJSON, therefore readily rendered in many web mapping applications; in fact, it is an implementation of GeoJSON-T, an experimental extension to GeoJSON that standardizes the representation of temporal attributes
it provides for optional temporal scoping of names, geometry, place type, and place relations]]></description>
<dc:subject>gazetteer linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3fd1c08bdfbf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:gazetteer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.rdfhdt.org/datasets/">
    <title>Datasets – RDF HDT</title>
    <dc:date>2018-09-19T20:00:41+00:00</dc:date>
    <link>http://www.rdfhdt.org/datasets/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[We provide some of the most useful/popular datasets from the LOD cloud in HDT for you to use them easily. If the dataset you need is not available here, you can create your own or kindly ask the data provider to publish their datasets in HDT format for all the community to enjoy.]]></description>
<dc:subject>semweb data linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e8975ebf189b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://hypergraphql.org/">
    <title>HyperGraphQL | GraphQL interface for querying and serving linked data on the Web.</title>
    <dc:date>2018-04-05T17:55:53+00:00</dc:date>
    <link>http://hypergraphql.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[HyperGraphQL is a GraphQL interface for querying and serving linked data on the Web. It is designed to support federated querying and exposing data from multiple linked data services using GraphQL query language and schemas. The core of the response is a JSON-LD object, which extends the standard JSON with the JSON-LD context enabling semantic disambiguation of the contained data.]]></description>
<dc:subject>graphql jsonld linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a742fe7a05bb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:graphql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:jsonld"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.loc.gov/aba/pcc/bibframe/TaskGroups/formulate_obtain_URI_guide.pdf">
    <title>FORMULATING AND OBTAINING URIs: A GUIDE TO COMMONLY USED VOCABULARIES AND REFERENCE SOURCES</title>
    <dc:date>2018-02-28T00:12:00+00:00</dc:date>
    <link>https://www.loc.gov/aba/pcc/bibframe/TaskGroups/formulate_obtain_URI_guide.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document has been established as a guide for metadata practitioners interested in capturing Uniform Resource Identifiers (URIs, and specifically HTTP URIs that provision for linked data) from data sources on the web in their bibliographic data; it is not a policy document. Specific implementations of the MARC 21 subfields 0 , 1, and 4 are free to choose to capture URIs from data sources listed below or others identified by their institutions. Inclusion of a particular data source in this document is not necessarily an endorsement, but rather an acknowledgment that they are commonly used by the library, archives and museum communities for the purposes of bibliographic description.]]></description>
<dc:subject>library linkeddata standard</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e15adc6a36a2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standard"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bibfra.me/">
    <title>BIBFRAME Lite + Supporting Vocabularies</title>
    <dc:date>2018-01-08T14:52:54+00:00</dc:date>
    <link>http://bibfra.me/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This site demonstrates Zepheira's approach to modular, layered vocabulary management that support our open source transformation tools and Linked Data training product offerings. These vocabularies are not intended to replace or compete with other Linked Data namespaces. These vocabularies serve as a basis for further scoping by BIBFRAME profiles. Our hope is by sharing this approach, others may consider similar practices for effective vocabulary management and distributed governance, and to demonstrate the flexibility of BIBFRAME. This work is ongoing and actively being shaped by participants of Zepheira's Practical Practitioner series.]]></description>
<dc:subject>linkeddata bibframe cataloging</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:93193614dc66/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bibframe"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cataloging"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gbv.github.io/beaconspec/beacon.html">
    <title>BEACON link dump format</title>
    <dc:date>2017-12-02T19:38:11+00:00</dc:date>
    <link>http://gbv.github.io/beaconspec/beacon.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[BEACON is a data interchange format for large numbers of uniform links. A BEACON link dump consists of

a set of links (Section 2.1) and
a set of meta fields (Section 4).]]></description>
<dc:subject>linking metadata standard rdf linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:bbbe296105d3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standard"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/dhlab-epfl/LinkedBooksMonographs/tree/v1.0">
    <title>dhlab-epfl/LinkedBooksMonographs at v1.0</title>
    <dc:date>2017-03-09T14:23:20+00:00</dc:date>
    <link>https://github.com/dhlab-epfl/LinkedBooksMonographs/tree/v1.0</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A dataset of citations extracted from monographs about the history of Venice, created in the context of the LinkedBooks project.

The creation of the dataset and its characteristics are discussed in the article: Colavizza, G., Romanello, M. and Kaplan, F. "The References of References: A Method to Enrich Humanities Library Catalogs with Citation Data." in International Journal on Digital Libraries, Springer (forthcoming 2017).]]></description>
<dc:subject>linkeddata books library cataloging</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:95161bdd829b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cataloging"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://wiki.dublincore.org/index.php/User_Guide/Publishing_Metadata#dcterms:language">
    <title>dcterms:language</title>
    <dc:date>2017-02-16T15:21:15+00:00</dc:date>
    <link>http://wiki.dublincore.org/index.php/User_Guide/Publishing_Metadata#dcterms:language</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The range of dcterms:language it the class dcterms:LinguisticSystem. All values used with dcterms:language have to be instances of this class. Therefore the property may only be used with non-literal values.]]></description>
<dc:subject>metadata standards linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f7ca415f4015/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://open-services.net/">
    <title>Open Services for Lifecycle Collaboration</title>
    <dc:date>2016-11-22T18:33:51+00:00</dc:date>
    <link>http://open-services.net/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[OSLC (Open Services for Lifecycle Collaboration) is an open and extensible framework that accelerates innovation by removing integration bottlenecks between all the disparate applications that contribute to the entire product lifecycle. OSLC replaces highly coupled, proprietary, server-to-server replication integrations with uncoupled, standards-based, “write once integrate everywhere” solutions. Building on WWW standards to define a minimal set of capabilities that support the most common integration scenarios, OSLC defines an approach for resource and capability discovery and UI enablement.]]></description>
<dc:subject>linkeddata architecture webservices standards inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1db3ddcb328a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://baskauf.blogspot.com/2016/10/linked-data-magic-and-big-data.html">
    <title>Steve Baskauf's blog: Linked Data &quot;Magic&quot; and &quot;Big&quot; data</title>
    <dc:date>2016-11-01T01:11:57+00:00</dc:date>
    <link>http://baskauf.blogspot.com/2016/10/linked-data-magic-and-big-data.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[RT @baskaufs: I have blogged about fun I had trying to load 132 million triples from @thegetty TGN into @blazegraph:  #linkedData]]></description>
<dc:subject>linkedData</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1cf7aeee0f32/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkedData"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://topbraid.org/spin/rdfsplus.html">
    <title>RDFS Plus in SPARQL</title>
    <dc:date>2016-05-22T21:16:25+00:00</dc:date>
    <link>http://topbraid.org/spin/rdfsplus.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A set of OWL RL rules to formalize the semantics of RDFS Plus.]]></description>
<dc:subject>rdf owl inference semweb linkeddata sparql</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5044abf84b86/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:owl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sparql"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://linkeddata.uriburner.com:8000/vapour">
    <title>Vapour, a Linked Data validator</title>
    <dc:date>2016-02-23T20:42:16+00:00</dc:date>
    <link>http://linkeddata.uriburner.com:8000/vapour</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Vapour is a validation service to check whether semantic web data is correctly published according to the current best practices, as defined by the Linked Data principles, the Best Practice Recipes and the Cool URIs.]]></description>
<dc:subject>linkeddata tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:fd8def31e940/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://graphite.ecs.soton.ac.uk/checker/">
    <title>RDF Triple-Checker</title>
    <dc:date>2016-02-23T20:41:45+00:00</dc:date>
    <link>http://graphite.ecs.soton.ac.uk/checker/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This tool helps find typos and common errors in RDF data.]]></description>
<dc:subject>linkeddata tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2bcbf9ed4f30/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.linkedmodel.org/doc/2015/SCHEMA_vaem-v2.0">
    <title>Vocabulary for Attaching Essential Metadata (VAEM) - Version 2.0</title>
    <dc:date>2016-02-23T15:52:28+00:00</dc:date>
    <link>http://www.linkedmodel.org/doc/2015/SCHEMA_vaem-v2.0</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The purpose of VAEM is to provide, by import, a foundation for commonly needed resources for metadata on an ontology.

VAEM stands for "Vocabulary for Attaching Essential Metadata". What VAEM regards as essential metadata is data about dates and times, confidentiality, and other characterisitic qualifiers of the ontology, but also references to where a ontology is documented and where to find ontology registration for governance, attribution and provenance. VAEM makes use of some properties from the DC terms vocabulary using the namespace prefix "dct".]]></description>
<dc:subject>metadata standards linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d5840aa0294f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://linkeddata.uriburner.com/">
    <title>URIBurner</title>
    <dc:date>2016-02-18T01:01:01+00:00</dc:date>
    <link>http://linkeddata.uriburner.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A data virtualization service that transforms data hosted in a variety of data spaces and formats into standards compliant Linked Data Objects for uniform access, integration and management.

The underlying technology is Virtuoso's in-built Linked Data Middleware (aka Sponger) that uses URLs as data source names for its powerful data ingestion and transformation services that result in highly navigable Linked Data Object graphs.

Post transformation, each Data Object is endowed with a dereferenceable identifier (Name) that resolves to its actual representation via its URL (Address). The Sponger then re-presents Data Object descriptions via HTML documents (the default behavior) or in a variety of raw data graph forms that include: CSV, N-Triples, Turtle, N3, RDF/XML, JSON, CXML, OData (Atom and JSON) etc.]]></description>
<dc:subject>linkeddata rdf semweb identifiers tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e22d5eca99fe/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/TR/sdw-bp/">
    <title>Spatial Data on the Web Best Practices</title>
    <dc:date>2016-01-20T13:23:58+00:00</dc:date>
    <link>https://www.w3.org/TR/sdw-bp/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document advises on best practices related to the publication and usage of spatial data on the Web; the use of Web technologies as they may be applied to location. The best practices are intended for practitioners, including Web developers and geospatial experts, and are compiled based on evidence of real-world application. These best practices suggest a significant change of emphasis from traditional Spatial Data Infrastructures by adopting a Linked Data approach.]]></description>
<dc:subject>spatial web data linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cffc46171fa5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:spatial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/TR/webmention/">
    <title>Webmention</title>
    <dc:date>2016-01-13T13:46:28+00:00</dc:date>
    <link>https://www.w3.org/TR/webmention/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Webmention is a simple way to notify any URL when you link to it on your site. From the receiver's perspective, it's a way to request notifications when other sites link to it.]]></description>
<dc:subject>web standards notification linkeddata periodo</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c9f29563e6a9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:notification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:periodo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developers.google.com/knowledge-graph/">
    <title>Google Knowledge Graph Search API  |  Knowledge Graph Search API  |  Google Developers</title>
    <dc:date>2015-12-18T19:54:29+00:00</dc:date>
    <link>https://developers.google.com/knowledge-graph/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Knowledge Graph Search API lets you find entities in the Google Knowledge Graph. The API uses standard schema.org types and is compliant with the JSON-LD specification.]]></description>
<dc:subject>google linkeddata api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5a3a3b861d06/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://osds.openlinksw.com/">
    <title>OpenLink Structured Data Sniffer Home Page</title>
    <dc:date>2015-12-07T13:55:57+00:00</dc:date>
    <link>http://osds.openlinksw.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The OpenLink Structured Data Sniffer (OSDS) is a browser extension for Chrome and Opera (with Firefox, Safari, and Microsoft Edge ports planned) that unveils metadata oriented structured data embedded within HTML documents.]]></description>
<dc:subject>linkeddata tools inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ade573d4370c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://lov.okfn.org/dataset/lov">
    <title>Linked Open Vocabularies</title>
    <dc:date>2015-08-02T17:05:23+00:00</dc:date>
    <link>http://lov.okfn.org/dataset/lov</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[LOV provides a choice of several hundreds vocabularies, based on quality requirements including URI stability and availability on the Web, use of standard formats and publication best practices, quality metadata and documentation, identifiable and trustable publication body, proper versioning policy.]]></description>
<dc:subject>linkeddata semweb vocabularies catalogs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3c77a6b5eed7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:vocabularies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:catalogs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://validator.lod-cloud.net/">
    <title>Data Hub LOD Datasets</title>
    <dc:date>2015-07-28T18:59:52+00:00</dc:date>
    <link>http://validator.lod-cloud.net/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This website gives an overview of Linked Data sources cataloged on Data Hub and their completeness level for inclusion in the LOD cloud. It furthermore offers a validator for your Data Hub entry with step-by-step guidance.]]></description>
<dc:subject>linkeddata metadata catalogs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1d46f9457a42/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:catalogs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/TR/vocab-duv/">
    <title>Dataset Usage Vocabulary</title>
    <dc:date>2015-06-26T17:56:53+00:00</dc:date>
    <link>http://www.w3.org/TR/vocab-duv/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This vocabulary is meant to fill a niche that helps standardize the way Web published dataset usage be conveyed and shared. At this time is no clear standard way to describe dataset usage on the Web. Without a means to systematically describe dataset usage, searching and conveying techniques are application specific and discovery and collaboration across the Web is more difficult. This vocabulary also recommends and requires data publishers to provide a mechanism of receiving data usage from data consumers in the form of feedback,citation and data correction.

]]></description>
<dc:subject>data description standards linkeddata vocabularies</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8dcfcaba0479/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:vocabularies"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/wragge/lod-books-viewer">
    <title>wragge/lod-books-viewer</title>
    <dc:date>2015-04-10T12:43:25+00:00</dc:date>
    <link>https://github.com/wragge/lod-books-viewer</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[AngularJS app for displaying a historical narrative enriched with Linked Open Data.]]></description>
<dc:subject>linkeddata narrative interface</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:014ff5991a42/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:narrative"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/TR/ldpatch/">
    <title>Linked Data Patch Format</title>
    <dc:date>2014-10-06T21:33:38+00:00</dc:date>
    <link>http://www.w3.org/TR/ldpatch/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Linked Data Patch Format (LD Patch) defines a language for expressing a sequence of operations to apply to Linked Data resources; it is suitable for use with the HTTP PATCH method.

]]></description>
<dc:subject>linkeddata editing standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8064a45ba55c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://enable-cors.org/">
    <title>enable cross-origin resource sharing</title>
    <dc:date>2014-09-30T18:07:08+00:00</dc:date>
    <link>http://enable-cors.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Cross-Origin Resource Sharing (CORS) is a specification that enables truly open access across domain-boundaries. If you serve public content, please consider using CORS to open it up for universal JavaScript/browser access.]]></description>
<dc:subject>ajax web javascript linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cea86f546ab7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ajax"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/Submission/2014/SUBM-shex-primer-20140602/">
    <title>Shape Expressions 1.0 Primer</title>
    <dc:date>2014-09-12T12:57:38+00:00</dc:date>
    <link>http://www.w3.org/Submission/2014/SUBM-shex-primer-20140602/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Shape Expressions can be used to validate documents, communicate expected graph patterns for interfaces, and generate user interface forms and interface code. The syntax and semantics of Shape Expressions are designed to be familiar to users of regular expressions. The conspicuous differences are that regular expressions correlate an ordered pattern of atomic characters and logical operators against an ordered sequence of characters. Shape Expressions correlate an ordered pattern of pairs of predicate and object classes (called NameClass and ValueClass) and logical operators against an unordered set of arcs in a graph. The logical operators in Shape Expressions, grouping, conjunction, disjunction and cardinality constraints, are defined to behave as closely as possible to their counterparts in regular expressions and grammar languages like BNF.]]></description>
<dc:subject>linkeddata semweb validation cleaning testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c8542a9d339a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:validation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cleaning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/Submission/2014/SUBM-shapes-20140211/">
    <title>Resource Shape 2.0</title>
    <dc:date>2014-09-12T12:38:17+00:00</dc:date>
    <link>http://www.w3.org/Submission/2014/SUBM-shapes-20140211/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document describes the Resource Shape specification, a high-level RDF vocabulary for describing the shape of RDF resources. Here the term RDF resource is used to denote a resource that has an RDF document among its set of available representations. The term shape is used because it is often useful to visualize an RDF document as a topological object, namely as a graph consisting of nodes interconnected by arcs. Throughout this document the terms RDF resource, RDF document, and RDF graph are used more or less interchangeably albeit somewhat imprecisely.

The shape of an RDF graph includes both a description of its expected contents (properties, types) within some operational context (e.g. GET, POST) and the integrity constraints that must be satisfied by the contents in that context.]]></description>
<dc:subject>linkeddata semweb validation testing cleaning</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:269de295060f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:validation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cleaning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/cognitect/transit-format#extensibility">
    <title>cognitect/transit-format · GitHub</title>
    <dc:date>2014-07-24T19:07:42+00:00</dc:date>
    <link>https://github.com/cognitect/transit-format#extensibility</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Would also be interesting to define a "triple" type for Transit to use it as a serialization for #linkeddata ]]></description>
<dc:subject>linkeddata</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1874a8f5b29e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://code.google.com/p/void-impl/wiki/SPARQLQueriesForStatistics">
    <title>SPARQLQueriesForStatistics - void-impl - Collection of SPARQL queries for computing voiD statistics - voiD vocabulary and implementations - Google Project Hosting</title>
    <dc:date>2014-06-24T21:20:42+00:00</dc:date>
    <link>https://code.google.com/p/void-impl/wiki/SPARQLQueriesForStatistics</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This page collects SPARQL queries for computing various statistics that can be expressed using the voiD vocabulary.

]]></description>
<dc:subject>metadata vocabulary linkeddata sparql</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0b839af67185/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:vocabulary"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sparql"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/geojson/geojson-ld/blob/master/time.md">
    <title>geojson-ld/time.md at master · geojson/geojson-ld</title>
    <dc:date>2014-06-16T16:14:48+00:00</dc:date>
    <link>https://github.com/geojson/geojson-ld/blob/master/time.md</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[With the addition of temporal items, GeoJSON features can become event-like and such features will be used in the following examples.

The concept of temporal extent is developed in parallel to the existing concept of spatial extent. The temporal items can therefore be safely ignored by GeoJSON processors.]]></description>
<dc:subject>geojson linkeddata jsonld temporal timeline</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4f0f9c4b08c1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:geojson"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:jsonld"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:temporal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:timeline"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/LinkedDataFragments/Client">
    <title>LinkedDataFragments/Client</title>
    <dc:date>2014-02-28T19:10:35+00:00</dc:date>
    <link>https://github.com/LinkedDataFragments/Client</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The issue with the current Linked Data Fragments is that they are either so powerful that their servers suffer from low availability rates (as is the case with SPARQL), or either don't allow efficient querying.

Instead, this client solves queries by accessing basic Linked Data Fragments. 
Each basic Linked Data Fragment offers:

data that corresponds to a basic triple pattern (example).
metadata that consists of the (approximate) total triple count (example).
controls that lead to all other fragments of the same dataset (example).]]></description>
<dc:subject>linkeddata publishing inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c1e1272f2861/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://vimeo.com/36752317">
    <title>Linked Open Data - What is it? on Vimeo</title>
    <dc:date>2014-02-21T19:03:16+00:00</dc:date>
    <link>http://vimeo.com/36752317</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Simple animation to explain what Linked Open Data is and why it's a good thing, both for users and for data providers.
]]></description>
<dc:subject>linkeddata inls520 * inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:567af0e1d61b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:*"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sites.tufts.edu/liam/2014/02/03/glossary/">
    <title>Beginner’s glossary to linked data » LiAM: Linked Archival Metadata</title>
    <dc:date>2014-02-04T02:18:43+00:00</dc:date>
    <link>http://sites.tufts.edu/liam/2014/02/03/glossary/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is a beginner’s glossary to linked data. It is a part of the yet-to-be published LiAM Guidebook on linked data in archives.
]]></description>
<dc:subject>linkeddata reference inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8ef309f5c242/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://berjon.com/blog/2013/06/linked-data.html">
    <title>Don't Make Me Think (About Linked Data) — Robin Berjon</title>
    <dc:date>2014-01-16T18:48:29+00:00</dc:date>
    <link>http://berjon.com/blog/2013/06/linked-data.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[So start with JSON. It works well in every sane language (and several insane ones). Throw in at least some of what's in JSON Schema for validation purposes. You're working on the Web so the natural way of interacting with data is HTML forms. So tweak what you have to work well with the sort of constraints and types that can be expressed in forms, for common Web editing tasks, notably taking client-side validation into account. At that point you likely have something that can usefully be mapped to typical storage (e.g. Mongo, Couch, or your garden variety ORM/RDB) but might require a few extra bits of information (e.g. that a given field ought to be unique — which in turn can be used in the form to check availability immediately, etc.).

You then need a way to link between entities. JSON Ref can be a good choice here (http://tools.ietf.org/html/draft-pbryan-zyp-json-ref-03). You likely don't want links everywhere, just at predictable places in your data model. Note that this has the interesting property that you do in fact end up with a graph, but it's a graph built of familiar, largely self-contained tree objects that are easy to manipulate by people who like yours truly have been using basic programming data structures forever.]]></description>
<dc:subject>linkeddata json</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8478d4c01035/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:json"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ribs.csres.utexas.edu/nosqlrdf/nosqlrdf_iswc2013.pdf">
    <title>NoSQL Databases for RDF: An Empirical Evaluation</title>
    <dc:date>2013-12-09T02:06:15+00:00</dc:date>
    <link>http://ribs.csres.utexas.edu/nosqlrdf/nosqlrdf_iswc2013.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A systematic attempt at characterizing and comparing NoSQL stores for RDF processing. Describes four different NoSQL stores and compares their key characteristics when running standard RDF benchmarks on a popular cloud infrastructure using both single-machine and distributed deployments.]]></description>
<dc:subject>nosql rdf performance semweb linkeddata database</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3cfc788a3152/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nosql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/TR/ldp-ucr/">
    <title>Linked Data Platform Use Cases and Requirements</title>
    <dc:date>2013-10-31T18:12:04+00:00</dc:date>
    <link>http://www.w3.org/TR/ldp-ucr/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[To foster the development of the Linked Data Platform specification, this document includes a set of user stories, use cases, scenarios and requirements that motivate a simple read-write Linked Data architecture, based on HTTP access to web resources that describe their state using RDF. The starting point for the development of these use cases is a collection of user stories that provide realistic examples describing how people may use read-write Linked Data. The use cases themselves are captured in a narrative style that describes a behavior, or set of behaviors based on, and using scenarios from, these user stories. The aim throughout has been to avoid details of protocol (specifically the HTTP protocol), and use of any specific vocabulary that might be introduced by the LDP specification.]]></description>
<dc:subject>linkeddata rest inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:694f6a55428c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/pelagios/pelagios-cookbook/wiki/Pelagios-Gazetteer-Interconnection-Format">
    <title>Pelagios Gazetteer Interconnection Format · pelagios/pelagios-cookbook Wiki</title>
    <dc:date>2013-10-01T16:46:53+00:00</dc:date>
    <link>https://github.com/pelagios/pelagios-cookbook/wiki/Pelagios-Gazetteer-Interconnection-Format</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In order to enable interoperation between gazetteers, Pelagios defines a common “baseline model” – a conceptual and syntactical least common denominator that all our gazetteers map to. It is important to note that this model is independent from the gazetteer’s internal data model, and follows our general strategy of “connectivity through common references” which standardizes how to create links between things, rather than standardizing how things should be represented. The baseline model contains the absolute minimum information we need to:

identify and disambiguate places
build a searchable index outside of the gazetteer, so we can relate search queries in a 3rd party
application (such as the Pelagios API) to the original entry in the source gazetteer
Just like the Pelagios annotations (which link data on the Web to places in a gazetteer), the gazetteer baseline model (which links places in one gazetteer to places in another) must be provided as RDF or CSV dump file(s).]]></description>
<dc:subject>gazetteer linkeddata data model</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:176acf916162/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:gazetteer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:model"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.morganclaypool.com/doi/abs/10.2200/S00498ED1V01Y201304WBE006">
    <title>Morgan &amp; Claypool Publishers - Synthesis Lectures on the Semantic Web: Theory and Technology - 3(3):1 - Abstract</title>
    <dc:date>2013-10-01T14:51:51+00:00</dc:date>
    <link>http://www.morganclaypool.com/doi/abs/10.2200/S00498ED1V01Y201304WBE006</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The surge of interest in the REpresentational State Transfer (REST) architectural style, the Semantic Web, and Linked Data has resulted in the development of innovative, flexible, and powerful systems that embrace one or more of these compatible technologies. However, most developers, architects, Information Technology managers, and platform owners have only been exposed to the basics of resource-oriented architectures. This book is an attempt to catalog and elucidate several reusable solutions that have been seen in the wild in the now increasingly familiar "patterns book" style. These are not turn key implementations, but rather, useful strategies for solving certain problems in the development of modern, resource-oriented systems, both on the public Web and within an organization's firewalls.]]></description>
<dc:subject>semweb linkeddata rest patterns inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:921097a9d8f8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:patterns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://lists.w3.org/Archives/Public/public-ldp/2013Mar/0112.html">
    <title>Re: Section 4: LDPR/non-LDPR formal definitions from James Leigh on 2013-03-26 (public-ldp@w3.org from March 2013)</title>
    <dc:date>2013-06-04T13:21:20+00:00</dc:date>
    <link>http://lists.w3.org/Archives/Public/public-ldp/2013Mar/0112.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Designing Callimachus applications that use named graphs as containers
is discouraged. In Callimachus, named graphs are for importing/updating
data that is managed elsewhere in a different system (like an external
vocabulary or dataset).

http://callimachusproject.org/]]></description>
<dc:subject>linkeddata ldp graph database</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c3b35983fd98/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ldp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:graph"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://jenit.github.io/linked-csv/">
    <title>Linked CSV</title>
    <dc:date>2013-05-19T17:25:24+00:00</dc:date>
    <link>http://jenit.github.io/linked-csv/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Many open data sets are essentially tables, or sets of tables, which follow the same regular structure. This document describes a set of conventions for CSV files that enable them to be linked together and to be interpreted as RDF.]]></description>
<dc:subject>linkeddata csv</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d9fbaefd857b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:csv"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://openpoi.ogcnetwork.net/">
    <title>OpenPOIs Registry</title>
    <dc:date>2013-05-19T15:35:47+00:00</dc:date>
    <link>http://openpoi.ogcnetwork.net/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[What is a POI?

POI is a common term for points of interest, or places of interest. Wikipedia's definition is pretty good.
What is the OpenPOIs Registry?

A database of points of interest information containing names and point locations for millions of businesses and civic places across the globe. Access is free and the data is open to all to use.

Why create yet another POI database?

We're all about connecting the Web: Most POI databases are meant to provide rich, detailed information about the places in their database. The intent of OpenPOI Registry is to be a comprehensive directory of links to other POI databases having the actual information about the places themselves. OpenPOI Registry is kind of like a phone book for POIs. We don't store a lot of data. But we can tell you the best places to get data.
We love historians and researchers: OpenPOI Registry is the only service committed to serving the needs of historical data. We will support time-based queries and historical data storage, so that you can find all the information about a place, not just what's there today.
How can I get the data?

The database can be queried by bounding box or by name via simple WFS requests. Each POI also has an elegant, permanent, RESTful URI.
What format is this data in?

All queries return data in either XML or JSON format conforming to the draft W3C POIWG specification. ]]></description>
<dc:subject>place database linkeddata spatial locative</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a34323115f15/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:place"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:spatial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:locative"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.ddialliance.org/system/files/UsingRDFToDescribeAndLinkSocialScienceDataToRelatedResourcesOnTheWeb.pdf">
    <title>Using RDF to Describe and Link Social Science Data to Related Resources on the Web</title>
    <dc:date>2013-05-18T20:32:14+00:00</dc:date>
    <link>http://www.ddialliance.org/system/files/UsingRDFToDescribeAndLinkSocialScienceDataToRelatedResourcesOnTheWeb.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document focuses on how best to relate Resource Description Framework (RDF)-described datasets to other related resources and objects (publications, geographies, organizations, people, etc.) in the Semantic Web. This includes a description of what would be needed to make these types of relationships most useful, including which RDF vocabularies should be used, potential link predicates, and possible data sources. RDF provides a good model for describing social science data because it supports formal semantics that provide a dependable basis for reasoning about the meaning of an RDF expression. In particular, it supports defined notions of entailment which provide a basis for defining reliable rules of inference in RDF data. 

Our findings are discussed in the context of social science data and more specifically, how to leverage existing metadata models to use alongside linked data. We provide a case for leveraging the Data Documentation Initiative (DDI) to enable semantic linking of social science data to other data and related resources on the Web. This document is organized into five use cases, which we consider in turn. Use cases include: linking related publications to data, linking data about people and organizations to research data, linking geography, linking to related studies, and linking data to licenses. We briefly discuss emerging or known issues surrounding the potential use of linked data within each of the defined use cases. Following these, we list more topics that could develop into additional use cases. Appendix A lists elements from the DDICodebook and DDI-Lifecycle specifications that are relevant to each use case.]]></description>
<dc:subject>linkeddata socialscience data opendata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d1f0d84dc96b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:socialscience"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opendata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.wikidata.org/wiki/Wikidata:Main_Page">
    <title>Wikidata</title>
    <dc:date>2013-05-09T17:33:10+00:00</dc:date>
    <link>http://www.wikidata.org/wiki/Wikidata:Main_Page</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Wikidata is a free knowledge base that can be read and edited by humans and machines alike. It is for data what Wikimedia Commons is for media files: it centralizes access to and management of structured data, such as interwiki references and statistical information. Wikidata contains data in every language supported by the MediaWiki software.]]></description>
<dc:subject>wikipedia data opendata linkeddata wikidata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4de999fda86e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wikipedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opendata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wikidata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.wikidata.org/wiki/Wikidata:List_of_properties">
    <title>Wikidata:List of properties - Wikidata</title>
    <dc:date>2013-04-29T18:53:41+00:00</dc:date>
    <link>https://www.wikidata.org/wiki/Wikidata:List_of_properties</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is the list of properties in Wikidata. Each statement at an item page links to a property, and assigns it a value.]]></description>
<dc:subject>wikidata linkeddata vocabulary ontology property types reference</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:edcfdebb058b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wikidata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:vocabulary"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:property"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:types"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>