<?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://developer.mozilla.org/en-US/docs/Web/API/Media_Session_API"/>
	<rdf:li rdf:resource="https://github.com/comunica/comunica/blob/master/packages/bus-http/lib/ActorHttp.ts#L33-L43"/>
	<rdf:li rdf:resource="https://langchain.readthedocs.io/en/latest/"/>
	<rdf:li rdf:resource="https://steampipe.io/docs"/>
	<rdf:li rdf:resource="https://fastapi.tiangolo.com/"/>
	<rdf:li rdf:resource="https://sqlite.org/vtab.html"/>
	<rdf:li rdf:resource="https://github.com/OpenRefine/OpenRefine/wiki/Data-Extension-API"/>
	<rdf:li rdf:resource="https://www.fcc.gov/ecfs/public-api-docs.html#documents"/>
	<rdf:li rdf:resource="https://choo.io/"/>
	<rdf:li rdf:resource="https://cloud.google.com/apis/design/"/>
	<rdf:li rdf:resource="http://apievangelist.com/"/>
	<rdf:li rdf:resource="http://tomcrane.github.io/scratch/osd/iiif-sizes.html"/>
	<rdf:li rdf:resource="https://developers.google.com/knowledge-graph/"/>
	<rdf:li rdf:resource="https://github.com/codeforscience/webdata/issues/5"/>
	<rdf:li rdf:resource="http://www.amundsen.com/blog/archives/1163"/>
	<rdf:li rdf:resource="https://github.com/resource-blueprint/resource-blueprint"/>
	<rdf:li rdf:resource="https://www.runscope.com/docs/radar"/>
	<rdf:li rdf:resource="http://hackage.haskell.org/package/api-tools"/>
	<rdf:li rdf:resource="http://simperium.com/"/>
	<rdf:li rdf:resource="http://www.markus-lanthaler.com/hydra/"/>
	<rdf:li rdf:resource="http://promises-aplus.github.io/promises-spec/"/>
	<rdf:li rdf:resource="https://github.com/mikeal/jaws"/>
	<rdf:li rdf:resource="http://jsonapi.org/"/>
	<rdf:li rdf:resource="https://developers.google.com/drive/manage-comments"/>
	<rdf:li rdf:resource="http://hublog.hubmed.org/archives/001965.html"/>
	<rdf:li rdf:resource="http://www.mnot.net/blog/2012/12/04/api-evolution"/>
	<rdf:li rdf:resource="http://codeartisan.blogspot.com/2012/08/hypermedia-programming-lists.html"/>
	<rdf:li rdf:resource="http://www.hathitrust.org/bib_api"/>
	<rdf:li rdf:resource="http://www.hathitrust.org/data_api"/>
	<rdf:li rdf:resource="http://www.hathitrust.org/data"/>
	<rdf:li rdf:resource="https://github.com/jed/hyperspider"/>
	<rdf:li rdf:resource="http://hublog.hubmed.org/archives/001958.html"/>
	<rdf:li rdf:resource="http://www.gbv.de/wikis/cls/DAIA_-_Document_Availability_Information_API"/>
	<rdf:li rdf:resource="http://developer.echonest.com/sandbox/emi/"/>
	<rdf:li rdf:resource="http://www.bizcoder.com/index.php/2012/03/05/a-tekpub-api/"/>
	<rdf:li rdf:resource="http://twitter.com/javascripts/widgets/widget.js"/>
	<rdf:li rdf:resource="http://mcavage.github.com/node-restify/"/>
	<rdf:li rdf:resource="http://amundsen.com/media-types/collection/format/"/>
	<rdf:li rdf:resource="https://wiki.digitalmethods.net/Dmi/DmiWinterSchool2012APIecology"/>
	<rdf:li rdf:resource="http://ql.io/"/>
	<rdf:li rdf:resource="http://soundadvice.id.au/blog/2011/12/06/#httpEvolvability"/>
	<rdf:li rdf:resource="https://github.com/flatiron/api-easy"/>
	<rdf:li rdf:resource="https://github.com/bnoguchi/everyauth"/>
	<rdf:li rdf:resource="https://github.com/jgorset/facepy"/>
	<rdf:li rdf:resource="http://webintents.org/"/>
	<rdf:li rdf:resource="http://www.elasticsearch.org/guide/reference/api/search/facets/"/>
	<rdf:li rdf:resource="http://code.google.com/p/linked-data-api/wiki/Specification"/>
	<rdf:li rdf:resource="http://wikipedia-miner.sourceforge.net/"/>
	<rdf:li rdf:resource="http://authority.ddbc.edu.tw/docs/open_content/"/>
	<rdf:li rdf:resource="https://cga-download.hmdc.harvard.edu/publish_web/Geo_Tools/timeRS/"/>
	<rdf:li rdf:resource="http://code.google.com/p/implementing-rest/"/>
	<rdf:li rdf:resource="http://librdf.org/docs/api/redland-storage-module-virtuoso.html"/>
	<rdf:li rdf:resource="http://kenai.com/projects/suncloudapis/pages/Home"/>
	<rdf:li rdf:resource="http://groups.csail.mit.edu/uid/turkit/"/>
	<rdf:li rdf:resource="http://accentuate.us/languages"/>
	<rdf:li rdf:resource="http://datajs.codeplex.com/"/>
	<rdf:li rdf:resource="http://blog.nodejitsu.com/rest-easy-test-any-api-in-nodejs"/>
	<rdf:li rdf:resource="https://github.com/cloudhead/cradle"/>
	<rdf:li rdf:resource="http://disqus.com/api/docs/"/>
	<rdf:li rdf:resource="http://www.oembed.com/"/>
	<rdf:li rdf:resource="http://text-processing.com/"/>
	<rdf:li rdf:resource="http://swift.ushahidi.com/extend/silcc/"/>
	<rdf:li rdf:resource="http://code.google.com/apis/ajax/playground/"/>
	<rdf:li rdf:resource="http://hookbox.org/"/>
	<rdf:li rdf:resource="http://code.google.com/apis/predict/"/>
	<rdf:li rdf:resource="http://code.google.com/apis/storage/"/>
	<rdf:li rdf:resource="http://www.w3.org/TR/rdfa-api/"/>
	<rdf:li rdf:resource="http://developers.facebook.com/docs/api"/>
	<rdf:li rdf:resource="http://incubator.apache.org/libcloud/"/>
	<rdf:li rdf:resource="http://platform.beta.mapquest.com/usage/directions/overview.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://developer.mozilla.org/en-US/docs/Web/API/Media_Session_API">
    <title>Media Session API - Web APIs | MDN</title>
    <dc:date>2025-08-11T16:15:50+00:00</dc:date>
    <link>https://developer.mozilla.org/en-US/docs/Web/API/Media_Session_API</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Media Session API provides a way to customize media notifications. It does this by providing metadata for display by the user agent for the media your web app is playing.

]]></description>
<dc:subject>audio media web api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4c10119a5e1f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:audio"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:media"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/comunica/comunica/blob/master/packages/bus-http/lib/ActorHttp.ts#L33-L43">
    <title>comunica/packages/bus-http/lib/ActorHttp.ts at master · comunica/comunica</title>
    <dc:date>2023-07-14T17:14:14+00:00</dc:date>
    <link>https://github.com/comunica/comunica/blob/master/packages/bus-http/lib/ActorHttp.ts#L33-L43</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Example of transforming WhatWG streams into Node streams.]]></description>
<dc:subject>javascript streaming nodejs api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1c73fc5863d9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:streaming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nodejs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://langchain.readthedocs.io/en/latest/">
    <title>Welcome to LangChain — 🦜🔗 LangChain 0.0.116</title>
    <dc:date>2023-03-20T00:57:54+00:00</dc:date>
    <link>https://langchain.readthedocs.io/en/latest/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Large language models (LLMs) are emerging as a transformative technology, enabling developers to build applications that they previously could not. But using these LLMs in isolation is often not enough to create a truly powerful app - the real power comes when you are able to combine them with other sources of computation or knowledge.

This library is aimed at assisting in the development of those types of applications.]]></description>
<dc:subject>llm api nlp query tools ai</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:53165156a945/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:llm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nlp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:query"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ai"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://steampipe.io/docs">
    <title>Learn Steampipe | Documentation | Steampipe</title>
    <dc:date>2022-12-07T14:31:44+00:00</dc:date>
    <link>https://steampipe.io/docs</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Steampipe exposes APIs and services as a high-performance relational database, giving you the ability to write SQL-based queries to explore dynamic data.]]></description>
<dc:subject>data api sql</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:74ec04a2c473/</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:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sql"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://fastapi.tiangolo.com/">
    <title>FastAPI</title>
    <dc:date>2020-11-15T23:48:29+00:00</dc:date>
    <link>https://fastapi.tiangolo.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[FastAPI is a modern, fast (high-performance), web framework for building APIs with Python 3.6+ based on standard Python type hints.]]></description>
<dc:subject>python rest api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5004bf13beeb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://sqlite.org/vtab.html">
    <title>The Virtual Table Mechanism Of SQLite</title>
    <dc:date>2020-10-10T20:59:24+00:00</dc:date>
    <link>https://sqlite.org/vtab.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A virtual table is an object that is registered with an open SQLite database connection. From the perspective of an SQL statement, the virtual table object looks like any other table or view. But behind the scenes, queries and updates on a virtual table invoke callback methods of the virtual table object instead of reading and writing on the database file.

The virtual table mechanism allows an application to publish interfaces that are accessible from SQL statements as if they were tables.]]></description>
<dc:subject>database sqlite API</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1783069a0bd0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sqlite"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:API"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/OpenRefine/OpenRefine/wiki/Data-Extension-API">
    <title>Data Extension API · OpenRefine/OpenRefine Wiki</title>
    <dc:date>2017-09-12T12:03:11+00:00</dc:date>
    <link>https://github.com/OpenRefine/OpenRefine/wiki/Data-Extension-API</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This page proposes a new optional API for reconciliation services, allowing clients to pull properties of reconciled records.]]></description>
<dc:subject>reconciliation api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6078d93557ad/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reconciliation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.fcc.gov/ecfs/public-api-docs.html#documents">
    <title>ECFS Public API documentation</title>
    <dc:date>2017-08-31T19:45:51+00:00</dc:date>
    <link>https://www.fcc.gov/ecfs/public-api-docs.html#documents</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Upload any document you want to be served from the FCC's servers.]]></description>
<dc:subject>wtf security api inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f3b7e5e45adb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wtf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://choo.io/">
    <title>Choo</title>
    <dc:date>2017-07-15T00:31:57+00:00</dc:date>
    <link>https://choo.io/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Choo operates on raw DOM nodes using an advanced diffing algorithm. Not only is this fast, it also means that all elements you build can be rendered directly on the DOM. Elements built for choo will work as long as the DOM continues to exist.]]></description>
<dc:subject>javascript api framework DOM</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:92f1b5ddb557/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:DOM"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cloud.google.com/apis/design/">
    <title>API Design Guide  |  Cloud APIs  |  Google Cloud Platform</title>
    <dc:date>2017-03-05T15:43:26+00:00</dc:date>
    <link>https://cloud.google.com/apis/design/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is a general design guide for networked APIs. It has been used inside Google since 2014 and is the guide we follow when designing Cloud APIs and other Google APIs. It is shared here to inform outside developers and to make it easier for us all to work together.

External developers may find it particularly useful when designing gRPC APIs for use with Google Cloud Endpoints, and we strongly recommend such developers use these design principles. However, we don't mandate its use for any non-Google developer and you can use Cloud Endpoints and/or gRPC without following the guide.

This guide applies to both REST APIs and RPC APIs, with specific focus on gRPC APIs. gRPC APIs use Protocol Buffers to define their API surface and API Service Configuration to configure their API services, including HTTP mapping, logging, and monitoring. HTTP mapping features are used by Google APIs and gRPC Cloud Endpoints APIs for JSON/HTTP to Protocol Buffers/RPC transcoding.

This guide is a living document and additions to it will be made over time as new style and design patterns are adopted and approved. In that spirit, it is never going to be complete and there will always be ample room for the art and craft of API design.]]></description>
<dc:subject>api design documentation architecture inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cfdd0c9895bd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://apievangelist.com/">
    <title>API Evangelist</title>
    <dc:date>2016-10-01T13:44:05+00:00</dc:date>
    <link>http://apievangelist.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[My name is Kin Lane, the API Evangelist, and this is my domain, where I work to better understand the world of the Application Programming Interface, or just API. APIs are touching almost every aspect of our increasingly digital lives, providing access to the bits and bytes that make our personal and professional worlds work. I work daily to publish the news, organizations, individuals, tools, and other common patterns I come across as part of my research.]]></description>
<dc:subject>api inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e8e62e6749bd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tomcrane.github.io/scratch/osd/iiif-sizes.html">
    <title>Tile-less IIIF</title>
    <dc:date>2016-01-24T22:16:46+00:00</dc:date>
    <link>http://tomcrane.github.io/scratch/osd/iiif-sizes.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Flickr, Wikimedia Commons and many other large repositories of images have several sizes available for a given image - a "legacy image pyramid". If these repostories can:

describe the sizes available for an image in an info.json for that image
return the appropriate sized image in response to a request that conforms to the IIIF Image API
...then all their images are opened up to the IIIF Universe. This does not require an image server. It requires a shim to translate, proxying the IIIF requests on to the existing static images, and generating an info.json from the image metadata.]]></description>
<dc:subject>javascript images interface API</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f3b0e61503b3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:images"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:API"/>
</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="https://github.com/codeforscience/webdata/issues/5">
    <title>Browser file and network I/O</title>
    <dc:date>2015-12-03T01:05:47+00:00</dc:date>
    <link>https://github.com/codeforscience/webdata/issues/5</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A tour of the state of I/O in the browser as it relates to data processing/data science users.]]></description>
<dc:subject>web browser api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:dfca5432d34f/</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:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.amundsen.com/blog/archives/1163">
    <title>mca blog [three keys to runtime governance: protocol, format, and vocabulary]</title>
    <dc:date>2015-11-08T02:42:33+00:00</dc:date>
    <link>http://www.amundsen.com/blog/archives/1163</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[three keys form the base of design-time governance.

ok, let me introduce you to my "three keys of DTG". these are not the ONLY things that need the focus on IT governance, but they are the bare minimum -- the essential building blocks. the starting point from which all other DTG springs:

1. Protocol Governance
2. Format Governance
3. Vocabulary Governance]]></description>
<dc:subject>http api vocabulary description</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d05522c72a01/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:vocabulary"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/resource-blueprint/resource-blueprint">
    <title>resource-blueprint/resource-blueprint</title>
    <dc:date>2014-09-30T18:02:15+00:00</dc:date>
    <link>https://github.com/resource-blueprint/resource-blueprint</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The following highlights the API design concepts underlying a Resource Blueprint.

Semantically define data and affordances (link relations).
Define state-machines representing a resource.
Includes transitions in different states (business rules) and the conditions (permissions) for their inclusion in a response.
Ideally, this should ultimately draw the state-machine as part of the design process.
Will be used mock the API to act as a true hypermedia API based on state.
Specify supported media-types.
The API Blueprint parser will generate sample representations based on the semantics, state-machine and known media-types.
Specify the entry point to the resource.
Adding metadata to elements that could be used to define a profile (e.g. ALPS) from the blueprint and other uses in the machine-readable output of the API Blueprint parser.
Enter protocol specific information as an implementation detail well after having designed the actual API.
Initially only supports HTTP protocol.
The only actual URI you will see in the human-readable version is the entry point, even though you can enter URIs in the blueprint.
APIs associated with specific resources can be designed individually as parts of an overall API that may span several resource blueprints to represent the overall API application state-machine.]]></description>
<dc:subject>api documentation hypermedia statemachine inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0d02913967d7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypermedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:statemachine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.runscope.com/docs/radar">
    <title>Getting Started with API Monitoring and Testing · Runscope API Tools Documentation · Runscope</title>
    <dc:date>2014-09-30T17:31:28+00:00</dc:date>
    <link>https://www.runscope.com/docs/radar</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A Runscope Radar test is a group of one or more HTTP requests executed sequentially. For each request in the sequence you can define  Assertions on expected response data and  Variables containing extracted response data to be used in subsequent requests.]]></description>
<dc:subject>api testing inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8acb79ebc61a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://hackage.haskell.org/package/api-tools">
    <title>Hackage: api-tools: DSL for generating API boilerplate and docs</title>
    <dc:date>2014-04-01T11:07:58+00:00</dc:date>
    <link>http://hackage.haskell.org/package/api-tools</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[api-tools provides a compact DSL for describing an API. It uses Template Haskell to generate the corresponding data types and assorted tools for working with it, including Aeson and QuickCheck instances for converting between JSON and the generated types and writing unit tests.]]></description>
<dc:subject>haskell rest api hypermedia</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9fe553ea5ebc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:haskell"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypermedia"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://simperium.com/">
    <title>Simperium</title>
    <dc:date>2014-03-29T11:09:49+00:00</dc:date>
    <link>http://simperium.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Use a Simperium library and write a few lines of code. Simperium can then move any JSON data across multiple versions of your app and your backend services.

Our hosted service manages persistence, security, conflicts, scaling, versioning, and backups.]]></description>
<dc:subject>cloud data api editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:17823af8ab8f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.markus-lanthaler.com/hydra/">
    <title>Hydra: Hypermedia-Driven Web APIs</title>
    <dc:date>2014-01-17T15:12:50+00:00</dc:date>
    <link>http://www.markus-lanthaler.com/hydra/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Hydra is an effort to simplify the development of interoperable, hypermedia-driven Web APIs. The two fundamental building blocks of Hydra are JSON‑LD and the Hydra Core Vocabulary.

JSON‑LD is the serialization format used in the communication between the server and its clients. The Hydra Core Vocabulary represents the shared vocabulary between them. By specifying a number of concepts which are commonly used in Web APIs it can be used as the foundation to build Web services that share REST's benefits in terms of loose coupling, maintainability, evolvability, and scalability. Furthermore it enables the creation of generic API clients instead of requiring specialized clients for every single API.]]></description>
<dc:subject>json-ld hypermedia api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:27d17bc9369d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:json-ld"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypermedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://promises-aplus.github.io/promises-spec/">
    <title>Promises/A+</title>
    <dc:date>2013-05-30T14:47:33+00:00</dc:date>
    <link>http://promises-aplus.github.io/promises-spec/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A promise represents a value that may not be available yet. The primary method for interacting with a promise is its then method.]]></description>
<dc:subject>api development specification async javascript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4685f04bafeb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:async"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/mikeal/jaws">
    <title>mikeal/jaws · GitHub</title>
    <dc:date>2013-05-24T12:47:23+00:00</dc:date>
    <link>https://github.com/mikeal/jaws</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Jaws has the most aggressive caching semantics of any HTTP API I know of. The full body of every GET request is cached by URL in an LRU cache and held indefinitely.

The only way to clear something from cache is to flush it by URL or matching route.]]></description>
<dc:subject>http api cache</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e17a73270cc1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cache"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://jsonapi.org/">
    <title>JSON API</title>
    <dc:date>2013-05-06T15:38:58+00:00</dc:date>
    <link>http://jsonapi.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A media type for APIs that serve JSON.
]]></description>
<dc:subject>json rest api inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:bd6cd2f80b00/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:json"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developers.google.com/drive/manage-comments">
    <title>Google Drive SDK — Google Developers</title>
    <dc:date>2013-03-02T21:03:07+00:00</dc:date>
    <link>https://developers.google.com/drive/manage-comments</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Drive API allows you to add comments to files in Google Drive. You can let your users insert comments and replies in shared files and carry on discussion threads in the comments. By supporting these features in your app, you create an environment where users can share files and edit them collaboratively.]]></description>
<dc:subject>documents annotation collaboration api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3daea2db9153/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documents"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:annotation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://hublog.hubmed.org/archives/001965.html">
    <title>Open, Social, Academic Bookmarking: Save to App.net</title>
    <dc:date>2013-02-05T00:50:18+00:00</dc:date>
    <link>http://hublog.hubmed.org/archives/001965.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[a cloud-based file system with arbitrary metadata, a browser extension for creating items and attaching files, a web-based reading interface, the ability to subscribe to other people's posts.]]></description>
<dc:subject>bibliography metadata api</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:6d60bfcc3a29/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bibliography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.mnot.net/blog/2012/12/04/api-evolution">
    <title>mnot’s blog: Evolving HTTP APIs</title>
    <dc:date>2012-12-04T14:18:32+00:00</dc:date>
    <link>http://www.mnot.net/blog/2012/12/04/api-evolution</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[One of the most vexing problems that still seems to be facing people when I talk to them about HTTP APIs is how to handle versioning and extensibility — i.e., how they evolve.]]></description>
<dc:subject>http api versioning</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8b44a95c5d61/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:versioning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://codeartisan.blogspot.com/2012/08/hypermedia-programming-lists.html">
    <title>codeartisan: Hypermedia Programming: Lists</title>
    <dc:date>2012-09-22T04:05:13+00:00</dc:date>
    <link>http://codeartisan.blogspot.com/2012/08/hypermedia-programming-lists.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The humble list is one of our simplest and yet most powerful data structures--so much so that we will even routinely write them out by hand. We put them on sticky notes to help us remember things we need to do or things we need to buy from the grocery store. We even use them for entertainment. In this post I'll explain how to represent and manipulate lists using hypermedia techniques.

The most straightforward list representation actually doesn't look that different than a handwritten to-do list; the text/uri-list media type just consists of one URI per line. This makes the format incredibly concise, since there is very little syntactic structure (just interleaved line breaks!), while making it completely general through the use of globally unambiguous identifiers.

Now let's talk about manipulating this list with HTTP.]]></description>
<dc:subject>web hypermedia data structure inls520 REST api inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:00d4acc10234/</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:hypermedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:structure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:REST"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.hathitrust.org/bib_api">
    <title>HathiTrust Bibliographic API | HathiTrust Digital Library</title>
    <dc:date>2012-09-10T18:15:37+00:00</dc:date>
    <link>http://www.hathitrust.org/bib_api</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This API returns bibliographic, rights, and volume information when given a single or multiple standard identifiers (ISBN, LCCN, OCLC, etc.). It is intended for use to retrive information about small numbers of items at a time. Bulk retrieval should be done using OAI or the HathiTrust tab-delimited inventory files, as described at http://www.hathitrust.org/data. Note that use of the data may be subject to third-party agreements, such as OCLC's Record Use policy. Permission must be sought for bulk retrieval of OCLC records by non-OCLC members.]]></description>
<dc:subject>HathiTrust bibliography data api digital libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:06a14396aea2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:HathiTrust"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bibliography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digital"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.hathitrust.org/data_api">
    <title>HathiTrust Data API | HathiTrust Digital Library</title>
    <dc:date>2012-09-10T18:14:34+00:00</dc:date>
    <link>http://www.hathitrust.org/data_api</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document describes a RESTful API to provide access to HathiTrust repository data and metadata resources. The HathiTrust Repository Data (HTD) API is referred to simply as API in this document.]]></description>
<dc:subject>HathiTrust data api digital libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f6d36553eb85/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:HathiTrust"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digital"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.hathitrust.org/data">
    <title>Data Availability and APIs | HathiTrust Digital Library</title>
    <dc:date>2012-09-10T18:12:46+00:00</dc:date>
    <link>http://www.hathitrust.org/data</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[HathiTrust distributes information about items in the repository (and items themselves where possible) through a variety of mechanisms.]]></description>
<dc:subject>hathitrust digital libraries data api metadata bibliography</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2acfa3c986f3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hathitrust"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digital"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bibliography"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/jed/hyperspider">
    <title>jed/hyperspider</title>
    <dc:date>2012-08-24T13:30:19+00:00</dc:date>
    <link>https://github.com/jed/hyperspider</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[hyperspider is a declarative HATEOAS API crawler for node.js. Give it a list of url patterns, and it will recursively crawl your hypertext HTTP API, streaming back every matching endpoint.]]></description>
<dc:subject>hypermedia api nodejs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e757d856a2b0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypermedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nodejs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://hublog.hubmed.org/archives/001958.html">
    <title>HubLog: Using Google Fusion Tables to provide an API to data files</title>
    <dc:date>2012-08-15T12:41:38+00:00</dc:date>
    <link>http://hublog.hubmed.org/archives/001958.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This example imports a large TSV file (all the data from the CUFTS Knowledgebase) into a Google Fusion Table, then uses the Fusion Table API to provide a JSON API for querying.]]></description>
<dc:subject>data sharing api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:11362a5d13a0/</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:sharing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.gbv.de/wikis/cls/DAIA_-_Document_Availability_Information_API">
    <title>DAIA - Document Availability Information API – Verbund-Wiki GBV</title>
    <dc:date>2012-05-23T21:58:22+00:00</dc:date>
    <link>http://www.gbv.de/wikis/cls/DAIA_-_Document_Availability_Information_API</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Document Availability Information API (DAIA) defines a data model with serializations in JSON and XML to encode information about the current availability of documents. This document defines the serialization formats DAIA/JSON and DAIA/XML and a HTTP query API to query DAIA information.]]></description>
<dc:subject>libraries api webservices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:038603b21ad8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://developer.echonest.com/sandbox/emi/">
    <title>EMI Partnership | The Echo Nest Developer Center</title>
    <dc:date>2012-03-26T15:36:52+00:00</dc:date>
    <link>http://developer.echonest.com/sandbox/emi/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[EMI and The Echo Nest have partnered to bring developers a unique opportunity to work with content from some of the biggest artists in the world. This content is organized into various sandboxes. Some sandboxes provide access to thousands of audio tracks from multiple artists. Other sandboxes focus on a single artist, providing broader content types like audio, video, artwork, photos and more.

The intent is to provide the developer community with the resources to create new and innovative applications and services. If you have an interesting concept, then EMI will partner with you to help bring that idea to market.]]></description>
<dc:subject>music resources api musicology digitalhumanities</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:86a1e4d48ae5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:music"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:resources"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:musicology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.bizcoder.com/index.php/2012/03/05/a-tekpub-api/">
    <title>A Tekpub API | Bizcoder</title>
    <dc:date>2012-03-06T22:53:43+00:00</dc:date>
    <link>http://www.bizcoder.com/index.php/2012/03/05/a-tekpub-api/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[On a number of occasions I have found a diagram like the one below is useful for visualizing an API.  It lets me see how a client will surf the API to get at the information it wants.  This is not any kind of official diagramming methodology.  I just use class diagrams and use the associations to represent links between resources and the classes represent a “kind of resource”.  I use that vague term because one box in this diagram may represent multiple actual resources in our real system.]]></description>
<dc:subject>rest api inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f2f3a73340b5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://twitter.com/javascripts/widgets/widget.js">
    <title>twitter.com/javascripts/widgets/widget.js</title>
    <dc:date>2012-03-02T13:55:29+00:00</dc:date>
    <link>http://twitter.com/javascripts/widgets/widget.js</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Full documented source of the Twitter search widget.]]></description>
<dc:subject>twitter javascript api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:842a944f94d6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mcavage.github.com/node-restify/">
    <title>API Guide | restify</title>
    <dc:date>2012-02-13T17:25:33+00:00</dc:date>
    <link>http://mcavage.github.com/node-restify/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[restify is a node.js module built specifically to enable you to build correct REST web services. It borrows heavily from express (intentionally) as that is more or less the de facto API for writing web applications on top of node.js.]]></description>
<dc:subject>nodejs rest framework api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:814f86283de7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nodejs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://amundsen.com/media-types/collection/format/">
    <title>Collection+JSON - Document Format : Media Types</title>
    <dc:date>2012-02-06T17:34:00+00:00</dc:date>
    <link>http://amundsen.com/media-types/collection/format/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Collection+JSON is a JSON-based read/write hypermedia-type designed to support management and querying of simple collections.]]></description>
<dc:subject>json api standards hypermedia</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0225d565944d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:json"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypermedia"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://wiki.digitalmethods.net/Dmi/DmiWinterSchool2012APIecology">
    <title>API Ecology</title>
    <dc:date>2012-01-30T13:54:10+00:00</dc:date>
    <link>https://wiki.digitalmethods.net/Dmi/DmiWinterSchool2012APIecology</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The concept of the mashup implies the combination of different data sources or functions. Practically, this often means that a mashup makes use of several APIs and tries to produce new insights or new functionalities by mixing them together. The patterns of combination are not random: one can imagine that certain APIs are brought together more often than others. This (short) project proposes to examine this dynamic more closely.]]></description>
<dc:subject>webservices api networks infoviz</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3f46794d2efe/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:networks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:infoviz"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ql.io/">
    <title>ql.io</title>
    <dc:date>2011-12-29T16:45:46+00:00</dc:date>
    <link>http://ql.io/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[ql.io is a declarative, evented, data-retrieval and aggregation gateway for quickly consuming HTTP APIs. ql.io re-uses concepts and syntax from SQL and JSON to create an imperative style language. Scripts written in this language can make HTTP requests to retrieve data, perform joins between API responses, project responses, or even make requests in a loop.]]></description>
<dc:subject>http api webservices rest composition inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:759599e43bba/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:composition"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://soundadvice.id.au/blog/2011/12/06/#httpEvolvability">
    <title>Best Practices for HTTP API evolvability</title>
    <dc:date>2011-12-29T16:42:43+00:00</dc:date>
    <link>http://soundadvice.id.au/blog/2011/12/06/#httpEvolvability</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[REST is the architectural style of the Web, and closely related to REST is the concept of a HTTP API. A HTTP API is a programmer-oriented interface to a specific service, and is known by other names such as a RESTful service contract, resource-oriented architecture, or a URI Space.

I say closely related because most HTTP APIs do not comply with the uniform interface constraint in it's strictest sense, which would demand that the interface be "standard" - or in practice: Consistent enough between different services that clients and services can obtain significant network effects. I won't dwell on this!

One thing we know is that these APIs will change, so what can we do at a technical level to deal with these changes as they occur?]]></description>
<dc:subject>http rest webservices evolution design web api inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:015c3aee1538/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:evolution"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/flatiron/api-easy">
    <title>flatiron/api-easy - GitHub</title>
    <dc:date>2011-11-09T21:04:03+00:00</dc:date>
    <link>https://github.com/flatiron/api-easy</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[APIeasy is designed to be a simple way to test RESTful APIs in node.js and Javascript. The primary design goal was to reduce the number of lines of test code required to fully cover all primary and edge use cases of a given API over HTTP.]]></description>
<dc:subject>rest api testing nodejs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5761a6293ff4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nodejs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/bnoguchi/everyauth">
    <title>bnoguchi/everyauth - GitHub</title>
    <dc:date>2011-08-15T16:54:35+00:00</dc:date>
    <link>https://github.com/bnoguchi/everyauth</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Authentication and authorization (password, facebook, & more) for your node.js Connect and Express apps.]]></description>
<dc:subject>nodejs oauth authentication facebook api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:60b5855e7544/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nodejs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:oauth"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authentication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/jgorset/facepy">
    <title>jgorset/facepy - GitHub</title>
    <dc:date>2011-08-15T16:36:52+00:00</dc:date>
    <link>https://github.com/jgorset/facepy</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Facepy is a client for Facebook's Graph API that doesn't suck.]]></description>
<dc:subject>facebook python api webservices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3b3105393b9f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://webintents.org/">
    <title>Web Intents</title>
    <dc:date>2011-08-09T21:20:39+00:00</dc:date>
    <link>http://webintents.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Web Intents is a framework for client-side service discovery and inter-application communication. Services register their intention to be able to handle an action on the user's behalf. Applications request to start an Action of a certain verb (share, edit, view, pick etc) and the system will find the appropriate Services for the user to use based on the user's preference.]]></description>
<dc:subject>webservices api standard hypermedia</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:bb30dd12e68e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standard"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypermedia"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.elasticsearch.org/guide/reference/api/search/facets/">
    <title>elasticsearch - guide - Search API - Facets</title>
    <dc:date>2011-07-20T14:49:25+00:00</dc:date>
    <link>http://www.elasticsearch.org/guide/reference/api/search/facets/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Facets provide aggregated data based on a search query. In the simple case, a facet can return facet counts for various facet values for a specific field. ElasticSearch supports more advanced facet implementations, such as statistical or date histogram facets.]]></description>
<dc:subject>faceted search api howto facets analysis elasticsearch inls520 IR</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e6f705102128/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:faceted"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:facets"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:analysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:elasticsearch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:IR"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/p/linked-data-api/wiki/Specification">
    <title>Specification - linked-data-api - Linked Data API Specification - API and formats to simplify use of linked data by web-developers - Google Project Hosting</title>
    <dc:date>2011-06-17T19:26:39+00:00</dc:date>
    <link>http://code.google.com/p/linked-data-api/wiki/Specification</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document defines a vocabulary and processing model for a configurable API layer intended to support the creation of simple RESTful APIs over RDF triple stores.]]></description>
<dc:subject>linkeddata api rdf data webservices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:41c39e1b3c78/</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:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://wikipedia-miner.sourceforge.net/">
    <title>Wikipedia Miner - Home</title>
    <dc:date>2011-06-14T15:50:56+00:00</dc:date>
    <link>http://wikipedia-miner.sourceforge.net/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Wikipedia Miner is a toolkit for navigating and making use of the structure and content of Wikipedia. It aims to make it easy for you to integrate Wikipedia's knowledge into your own applications, by:

providing simplified, object-oriented access to Wikipedia's structure and content.
measuring how terms and concepts in Wikipedia are connected to each other.
detecting and disambiguating Wikipedia topics when they are mentioned in documents.]]></description>
<dc:subject>wikipedia datamining api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6d285d07f37e/</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:datamining"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://authority.ddbc.edu.tw/docs/open_content/">
    <title>DDBC Authority Open Content Project | Introduction</title>
    <dc:date>2011-06-13T15:46:21+00:00</dc:date>
    <link>http://authority.ddbc.edu.tw/docs/open_content/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The DDBC Time Authority Database is one of a group of Authority Databases provided by Dharma Drum Buddhist College (DDBC). The time authority database contains detailed Chinese calendar data from beginning of the Qin dynasty to the current day. The major purpose of this database is to provide complete Chinese calendar information that can be used by external services and applications. It does, however, have its own web-based query interface and can be used as a standalone service.]]></description>
<dc:subject>time periodization vocabulary api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9522f79dd591/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:periodization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:vocabulary"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cga-download.hmdc.harvard.edu/publish_web/Geo_Tools/timeRS/">
    <title>time period referencing system User Guide</title>
    <dc:date>2011-06-13T15:44:10+00:00</dc:date>
    <link>https://cga-download.hmdc.harvard.edu/publish_web/Geo_Tools/timeRS/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[timeRS - Time Referencing System - is a project under development that will provide a Java API and commandline application for converting files with named periods and dates into a JSON format that can be browsed with the Simile Timeline API. The timeRS application will convert dates in several specified input formats into standardized ISO8601 and Julian Day Number formats.

timeRS will expedite the creation of customized timelines for named periods and events, and will provide an example of the Simile configuration that facilitates data entry of timeline object values into external databases. By browsing the timeline, users will be able to click on a relevant timeline object which will pass the values for that object to a RESTful data entry form (by default a Wiki page in Simile Timeline).]]></description>
<dc:subject>time periodization timeline api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:676d38c3a9eb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:periodization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:timeline"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/p/implementing-rest/">
    <title>implementing-rest - Exploring the implementation aspects of the REST architectural style. - Google Project Hosting</title>
    <dc:date>2011-05-11T12:45:35+00:00</dc:date>
    <link>http://code.google.com/p/implementing-rest/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is a place for exploring aspects of implementing applications using the REST architectural style. This may include statements about existing frameworks and libraries, general discussions about the nature of the style and how it may be expressed and/or encouraged via a programming framework, etc.]]></description>
<dc:subject>rest architecture api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7da5ea4fcdcc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://librdf.org/docs/api/redland-storage-module-virtuoso.html">
    <title>Store 'virtuoso'</title>
    <dc:date>2011-05-06T21:05:05+00:00</dc:date>
    <link>http://librdf.org/docs/api/redland-storage-module-virtuoso.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Virtuoso Redland RDF Provider is an implementation of the Storage API, Model and Query interfaces of the Redland framework for RDF. This provider enables the execution of queries via the Redland Rasqal query engine or via Virtuoso query engine directly against the Virtuoso OpenSource Quad Store.]]></description>
<dc:subject>rdf database python api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:eabb6cdc9c62/</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:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kenai.com/projects/suncloudapis/pages/Home">
    <title>The APIs for the Sun Cloud: Wiki: Home — Project Kenai</title>
    <dc:date>2011-05-06T15:33:06+00:00</dc:date>
    <link>http://kenai.com/projects/suncloudapis/pages/Home</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This wiki specifies a RESTful API for creating and managing cloud resources, including compute, storage, and networking components.]]></description>
<dc:subject>rest api cloud example mediatypes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d2f33f5867dc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:example"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:mediatypes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://groups.csail.mit.edu/uid/turkit/">
    <title>TurKit Homepage</title>
    <dc:date>2011-04-28T14:41:16+00:00</dc:date>
    <link>http://groups.csail.mit.edu/uid/turkit/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[TurKit is a Java/JavaScript API for running iterative tasks on Mechanical Turk. You can safely re-execute TurKit programs without re-running costly side effects on Mechanical Turk, like creating new HITs, but still write your program in a straightforward imperative manner—there is no need to unravel the program into a state machine.]]></description>
<dc:subject>amazon crowdsourcing api javascript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a86942dffd24/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:crowdsourcing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://accentuate.us/languages">
    <title>Languages - Accentuate.us - Really Easy Computer Input</title>
    <dc:date>2011-04-15T18:36:40+00:00</dc:date>
    <link>http://accentuate.us/languages</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Accentuate.us uses statistics to predict where special characters are needed on a language-by-language basis.]]></description>
<dc:subject>language input python tools webservices api machinelearning</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e3dcbbca940f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:input"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:machinelearning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://datajs.codeplex.com/">
    <title>datajs - JavaScript Library for data-centric web applications</title>
    <dc:date>2011-04-14T12:50:22+00:00</dc:date>
    <link>http://datajs.codeplex.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[datajs is a new cross-browser JavaScript library that enables data-centric web applications by leveraging modern protocols such as JSON and OData and HTML5-enabled browser features. It's designed to be small, fast and easy to use.]]></description>
<dc:subject>javascript json storage odata api data html</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e0a795593cfe/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:json"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:storage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:odata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.nodejitsu.com/rest-easy-test-any-api-in-nodejs">
    <title>RESTeasy: Test any API in node.js - blog.nodejitsu.com - scaling node.js applications one callback at a time.</title>
    <dc:date>2011-04-14T03:54:10+00:00</dc:date>
    <link>http://blog.nodejitsu.com/rest-easy-test-any-api-in-nodejs</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A simple tool for writing behavior-driven tests for any REST API.]]></description>
<dc:subject>rest api testing nodejs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d98ec8f968fb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nodejs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/cloudhead/cradle">
    <title>cloudhead/cradle - GitHub</title>
    <dc:date>2011-02-20T19:16:31+00:00</dc:date>
    <link>https://github.com/cloudhead/cradle</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Cradle is an asynchronous javascript client for CouchDB. It is somewhat higher-level than most other CouchDB clients, requiring a little less knowledge of CouchDB's REST API. Cradle also has built-in write-through caching, giving you an extra level of speed, and making document updates and deletion easier.]]></description>
<dc:subject>couchdb nodejs database api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f4192553dc81/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:couchdb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nodejs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://disqus.com/api/docs/">
    <title>API - DISQUS</title>
    <dc:date>2011-01-03T14:06:08+00:00</dc:date>
    <link>http://disqus.com/api/docs/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[These docs describe version 3.0 of the Disqus API.]]></description>
<dc:subject>disqus api reference</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8c645babf09d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:disqus"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.oembed.com/">
    <title>oEmbed</title>
    <dc:date>2010-09-17T19:39:05+00:00</dc:date>
    <link>http://www.oembed.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[oEmbed is a format for allowing an embedded representation of a URL on third party sites. The simple API allows a website to display embedded content (such as photos or videos) when a user posts a link to that resource, without having to parse the resource directly.]]></description>
<dc:subject>transclusion web architecture standards api widget</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ed798e19f996/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:transclusion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:widget"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://text-processing.com/">
    <title>Text Processing APIs and Python NLTK Demos | Text Mining | Stemming | Tagging | Python NLTK Demo</title>
    <dc:date>2010-08-23T18:20:13+00:00</dc:date>
    <link>http://text-processing.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Text Processing API supports the following functionality:

Stemming & Lemmatization
Sentiment Analysis
Tagging and Chunk Extraction]]></description>
<dc:subject>nlp api webservices python</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c27f93bd9c0b/</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:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://swift.ushahidi.com/extend/silcc/">
    <title>Extend Swift | SiLCC</title>
    <dc:date>2010-08-01T20:30:22+00:00</dc:date>
    <link>http://swift.ushahidi.com/extend/silcc/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[SiLCC is a cloud based service for parsing text and extracting relevant keywords.]]></description>
<dc:subject>nlp tools tagging metadata api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5afb694bb807/</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:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tagging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/apis/ajax/playground/">
    <title>Google Code Playground</title>
    <dc:date>2010-08-01T20:26:32+00:00</dc:date>
    <link>http://code.google.com/apis/ajax/playground/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Experiment with Google APIs.]]></description>
<dc:subject>google ajax api javascript tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5db114bc73d7/</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:ajax"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://hookbox.org/">
    <title>Hookbox</title>
    <dc:date>2010-07-29T21:25:23+00:00</dc:date>
    <link>http://hookbox.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Hookbox is a Comet server and message queue that tightly integrates with your existing web application via web hooks and a REST interface.]]></description>
<dc:subject>comet messaging python queue ajax REST api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0db162e545ee/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:comet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:messaging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:queue"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ajax"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:REST"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/apis/predict/">
    <title>Google Prediction API - Google Code</title>
    <dc:date>2010-07-08T19:52:54+00:00</dc:date>
    <link>http://code.google.com/apis/predict/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Prediction API enables access to Google's machine learning algorithms to analyze your historic data and predict likely future outcomes.]]></description>
<dc:subject>machinelearning api classification</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ea433b3e9dd2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:machinelearning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:classification"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/apis/storage/">
    <title>Google Storage for Developers - Google Code</title>
    <dc:date>2010-07-08T19:51:24+00:00</dc:date>
    <link>http://code.google.com/apis/storage/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Google Storage for Developers is a RESTful service for storing and accessing your data on Google's infrastructure. The service combines the performance and scalability of Google's cloud with advanced security and sharing capabilities. ]]></description>
<dc:subject>api cloud google storage</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6d5c3df1a5f3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:storage"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/TR/rdfa-api/">
    <title>RDFa API</title>
    <dc:date>2010-06-08T21:03:17+00:00</dc:date>
    <link>http://www.w3.org/TR/rdfa-api/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[It must be simple for Web developers to extract and utilize structured information from a Web document. This document details such a mechanism; an RDFa Document Object Model Application Programming Interface (RDFa DOM API) that allows simple extraction and usage of structured information from a Web document.]]></description>
<dc:subject>rdfa linkeddata web metadata api standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:dfb1eeba9076/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdfa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://developers.facebook.com/docs/api">
    <title>Graph API - Facebook Developers</title>
    <dc:date>2010-04-25T20:13:51+00:00</dc:date>
    <link>http://developers.facebook.com/docs/api</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The new Graph API attempts to drastically simplify the way developers read and write data to Facebook. It presents a simple, consistent view of the Facebook social graph, uniformly representing objects in the graph (e.g., people, photos, events, and fan pages) and the connections between them (e.g., friend relationships, shared content, and photo tags).]]></description>
<dc:subject>social data api rest webservices facebook metadata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2c518f07f896/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:social"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://incubator.apache.org/libcloud/">
    <title>libcloud python library - a unified interface to cloud server providers</title>
    <dc:date>2010-02-13T05:07:08+00:00</dc:date>
    <link>http://incubator.apache.org/libcloud/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[libcloud is a pure python client library for interacting with many of the popular cloud server providers. It was created to make it easy for developers to build products that work between any of the services that it supports.]]></description>
<dc:subject>python cloud tools api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:959c8ee54a5b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://platform.beta.mapquest.com/usage/directions/overview.html">
    <title>Mapquest Routing Services</title>
    <dc:date>2009-07-22T17:18:22+00:00</dc:date>
    <link>http://platform.beta.mapquest.com/usage/directions/overview.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Route Service provides a simple interface to get routing, narrative, and shapes.
]]></description>
<dc:subject>maps api locative directions</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:734effa08dd4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:maps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:locative"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:directions"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>