<?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="http://www.open-disco.org/#_summary"/>
	<rdf:li rdf:resource="http://open-services.net/"/>
	<rdf:li rdf:resource="https://github.com/hoisie/web"/>
	<rdf:li rdf:resource="http://dret.net/netdret/docs/wilde-cacm2008-document-design-matters/"/>
	<rdf:li rdf:resource="http://www.gbv.de/wikis/cls/DAIA_-_Document_Availability_Information_API"/>
	<rdf:li rdf:resource="http://ws-rest.org/2012/proc/a4-2-lanthaler.pdf"/>
	<rdf:li rdf:resource="https://wiki.digitalmethods.net/Dmi/DmiWinterSchool2012APIecology"/>
	<rdf:li rdf:resource="http://dret.net/netdret/docs/rest-icwe2010/"/>
	<rdf:li rdf:resource="http://ql.io/"/>
	<rdf:li rdf:resource="http://soundadvice.id.au/blog/2011/12/06/#httpEvolvability"/>
	<rdf:li rdf:resource="http://gregor.middell.net/collatex/api/collate"/>
	<rdf:li rdf:resource="https://github.com/interedition/microservices"/>
	<rdf:li rdf:resource="http://www.interedition.eu/wiki/index.php/About_microservices"/>
	<rdf:li rdf:resource="http://www.simpleframework.org/"/>
	<rdf:li rdf:resource="https://github.com/jgorset/facepy"/>
	<rdf:li rdf:resource="http://webintents.org/"/>
	<rdf:li rdf:resource="https://github.com/urschrei/pyzotero"/>
	<rdf:li rdf:resource="http://akara.info/"/>
	<rdf:li rdf:resource="http://wiki.xml3k.org/Akara/Architecture/Pipelines"/>
	<rdf:li rdf:resource="http://wiki.xml3k.org/Akara/Architecture"/>
	<rdf:li rdf:resource="http://cse.unl.edu/~kstolee/icse2011.pdf"/>
	<rdf:li rdf:resource="http://code.google.com/p/linked-data-api/wiki/Specification"/>
	<rdf:li rdf:resource="http://wikipedia-miner.sourceforge.net/index.htm"/>
	<rdf:li rdf:resource="http://accentuate.us/languages"/>
	<rdf:li rdf:resource="http://code.google.com/p/google-refine/wiki/ReconciliationServiceApi"/>
	<rdf:li rdf:resource="http://www.datasciencetoolkit.org/"/>
	<rdf:li rdf:resource="http://www.loggly.com/product/"/>
	<rdf:li rdf:resource="http://www.pusherapp.com/"/>
	<rdf:li rdf:resource="http://text-processing.com/"/>
	<rdf:li rdf:resource="http://developers.facebook.com/docs/api"/>
	<rdf:li rdf:resource="http://www.odata.org/"/>
	<rdf:li rdf:resource="http://hurl.it/"/>
	<rdf:li rdf:resource="http://authority.ddbc.edu.tw/"/>
	<rdf:li rdf:resource="http://bitbucket.org/jespern/django-piston/wiki/Home"/>
	<rdf:li rdf:resource="http://revcanonical.appspot.com/"/>
	<rdf:li rdf:resource="http://code.flickr.com/blog/2009/03/18/building-fast-client-side-searches/"/>
	<rdf:li rdf:resource="http://developer.yahoo.com/yql/"/>
	<rdf:li rdf:resource="http://developer.yahoo.com/geo/"/>
	<rdf:li rdf:resource="http://documentscompass.org/"/>
	<rdf:li rdf:resource="http://www.loc.gov/standards/sru/oasis.html"/>
	<rdf:li rdf:resource="http://www.dlib.org/dlib/january09/denenberg/01denenberg.html"/>
	<rdf:li rdf:resource="http://www.gbv.de/wikis/cls/Getting_started_with_SeeAlso"/>
	<rdf:li rdf:resource="http://code.google.com/apis/spreadsheets/developers_guide_python.html"/>
	<rdf:li rdf:resource="http://openguid.net/services/"/>
	<rdf:li rdf:resource="http://jets3t.s3.amazonaws.com/index.html"/>
	<rdf:li rdf:resource="http://code.google.com/p/argot-hub/wiki/GettingStartedDeployment"/>
	<rdf:li rdf:resource="http://labs.ideeinc.com/multicolr/#colors=666666,999966,663366;"/>
	<rdf:li rdf:resource="http://www.oclc.org/research/projects/termservices/"/>
	<rdf:li rdf:resource="http://atomserver.codehaus.org/"/>
	<rdf:li rdf:resource="http://outgoing.typepad.com/outgoing/2008/06/linking-to-worl.html"/>
	<rdf:li rdf:resource="http://xisbn.worldcat.org/xisbnadmin/xoclcnum/index.htm"/>
	<rdf:li rdf:resource="http://davidkellogg.com/wiki/Main_Page"/>
	<rdf:li rdf:resource="http://code.google.com/p/hkit/"/>
	<rdf:li rdf:resource="http://code.google.com/p/mf-optimus/"/>
	<rdf:li rdf:resource="http://doc.s3.amazonaws.com/proposals/post.html"/>
	<rdf:li rdf:resource="http://code.google.com/p/nose-trestle/"/>
	<rdf:li rdf:resource="http://opencalais.com/documentation/calais-web-service-api"/>
	<rdf:li rdf:resource="http://featureserver.org/"/>
	<rdf:li rdf:resource="http://analyze.echonest.com/AudioAnalysis.html"/>
	<rdf:li rdf:resource="http://code.google.com/apis/gdata/json.html"/>
	<rdf:li rdf:resource="http://www.basiscraft.com/"/>
	<rdf:li rdf:resource="http://www.snee.com/bobdc.blog/2008/01/scraping_and_linked_data.html"/>
	<rdf:li rdf:resource="http://www.couchdbwiki.com/index.php?title=HTTP_Doc_API#Modify_Multiple_Documents_with_a_Single_Request"/>
	<rdf:li rdf:resource="http://code.google.com/p/httplib2/"/>
	<rdf:li rdf:resource="http://mozy.com/"/>
	<rdf:li rdf:resource="http://www.dil.ie/about.asp"/>
	<rdf:li rdf:resource="http://www.amazon.com/gp/browse.html?node=342335011"/>
	<rdf:li rdf:resource="http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.html"/>
	<rdf:li rdf:resource="http://pipes.deri.org/"/>
	<rdf:li rdf:resource="http://developer.amazonwebservices.com/connect/kbcategory.jspa?categoryID=87"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://www.open-disco.org/#_summary">
    <title>Discovering Interoperative Services for Continuous Operation (DISCO)</title>
    <dc:date>2019-10-10T00:00:57+00:00</dc:date>
    <link>http://www.open-disco.org/#_summary</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document details an adhoc specification called DISCO (Discovering Interoperative Services for Continuous Operation). DISCO is a simple language for managing the adding/removing of services as well as the ability to search ("find") and make connections with ("bind") registered services.

DISCO was designed to be easy, open, lightweight, and extensible. For this reason, readers/implementers may find things "missing" or "underspecified." This is intentional. Getting started is meant to be easy. And local customization is supported as needed. This allows the DISCO spec to safely grow and improve over time without breaking exsting implementations.

The DISCO "language" supports the following features:

register : add a service to the shared registry

find : query the registry for services (dependents) to consume

bind : notify the registry the intention to connect with and use another service

renew : renew a service’s registry lease to prove is is still up and running

unregister : remove a service from the registry

Optionally, services can expose a health-check URL to allow registries to periodically check the status of a registered service.

Implementing a DISCO server is a simple as exposing URLs that support each of the above actions and supporting the defined input and output arguments in one or more identified media types.

Implementing support for DISCO in a service (or service proxy) can be accomplished by adding method to an individual service that handle the register, unregister, and renew or health-check actions. Optionally, services can add support for the find and bind actions if they wish to use the registry to locate other dependent services they consume.]]></description>
<dc:subject>webservices catalogs metadata standard</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3d5327a4e9ef/</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:catalogs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standard"/>
</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="https://github.com/hoisie/web">
    <title>hoisie/web</title>
    <dc:date>2012-07-24T17:01:36+00:00</dc:date>
    <link>https://github.com/hoisie/web</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[web.go is the simplest way to write web applications in the Go programming language. It's ideal for writing simple, performant backend web services.]]></description>
<dc:subject>go web framework webservices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:525e0b16ebb6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:go"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dret.net/netdret/docs/wilde-cacm2008-document-design-matters/">
    <title>Document Design Matters (Erik Wilde and Robert J. Glushko)</title>
    <dc:date>2012-07-01T12:43:09+00:00</dc:date>
    <link>http://dret.net/netdret/docs/wilde-cacm2008-document-design-matters/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The classical approach to the data aspect of system design distinguishes conceptual, logical, and physical models. Models of each type or level are governed by metamodels that specify the kinds of concepts and constraints that can be used by each model; in most cases metamodels are accompanied by languages for describing models. For example, in database design, conceptual models usually conform to the Entity-Relationship (ER) metamodel (or some extension of it), the logical model maps ER models to relational tables and introduces normalization, and the physical model handles implementation issues such as possible denormalizations in the context of a particular database schema language. In this modeling methodology, there is a single hierarchy of models that rests on the assumption that one data model spans all modeling levels and applies to all the applications in some domain. The one true model approach assumes homogeneity, but this does not work very well for the Web. The Web as a constantly growing ecosystem of heterogeneous data and services has challenged a number of practices and theories about the design of IT landscapes. Instead of being governed by one true model used by everyone, the underlying assumption of top-down design, Web data and services evolve in an uncoordinated fashion. As a result, a fundamental challenge with Web data and services is matching and mapping local and often partial models that not only are different models of the same application domain, but also differ, implicitly or explicitly, in their associated metamodels.]]></description>
<dc:subject>models xml webservices inls520 documents design inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ba8fca0a8044/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documents"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</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://ws-rest.org/2012/proc/a4-2-lanthaler.pdf">
    <title>On Using JSON-LD to Create Evolvable RESTful Services</title>
    <dc:date>2012-05-11T16:26:08+00:00</dc:date>
    <link>http://ws-rest.org/2012/proc/a4-2-lanthaler.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[As the amount of data and devices on the Web experiences exponential growth issues on how to integrate such hugely heterogeneous components into a scalable system become increasingly important. REST has proven to be a viable solution for such large-scale information systems. It provides a set of architectural constraints that, when applied as a whole, result in benefits in terms of loose coupling, maintainability, evolvability, and scalability. Unfortunately, some of REST’s constraints such as the ones that demand self-descriptive messages or require the use of hypermedia as the engine of application state are rarely implemented correctly. This results in tightly coupled and thus brittle systems. To solve these and other issues, we present JSON-LD, a community effort to standardize a media type targeted to machine-to-machine communication with inherent hypermedia support and rich semantics. Since JSON-LD is 100% compatible with traditional JSON, developers can continue to use their existing tools and libraries. As we show in the paper, JSON-LD can be used to build truly RESTful services that, at the same time, integrate the exposed data into the Semantic Web. The required additional design costs are significantly outweighed by the achievable benefits in terms of loose coupling, evolvability, scalability, self-descriptiveness, and maintainability.]]></description>
<dc:subject>rest json webservices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7725d008d8a0/</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:json"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</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://dret.net/netdret/docs/rest-icwe2010/">
    <title>Design Principles, Patterns and Emerging Technologies for RESTful Web Services (ICWE 2010 Tutorial)</title>
    <dc:date>2011-12-30T19:07:49+00:00</dc:date>
    <link>http://dret.net/netdret/docs/rest-icwe2010/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The primary goal of this tutorial to close the gap between the high-level concept of Service-Oriented Architecture (SOA), and the question of how to implement such an architecture once services have been identified. Colloquially, it is often assumed that services in a Web-oriented are implemented as Web services, and these are often exclusively perceived as using the SOAP stack of protocols. Our goal is to describe that Web services can also use other technologies, such as RESTful implementations on top of HTTP. Furthermore, we will explain how a disciplined process can lead from the business level, which is mainly about identifying services on an abstract level, to an IT architecture, and that it is important to not impose architectural constraints (such as defining service in a function-oriented way rather than in a resource-oriented way) too early in the process.]]></description>
<dc:subject>rest webservices inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e182b3a023b4/</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:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</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="http://gregor.middell.net/collatex/api/collate">
    <title>REST service :: CollateX</title>
    <dc:date>2011-11-29T12:05:15+00:00</dc:date>
    <link>http://gregor.middell.net/collatex/api/collate</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is the REST service of CollateX. To call it, you can post witness data as specified below and get the collation result back in a number of formats.]]></description>
<dc:subject>collation editing digitalhumanities tools webservices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6f0263329c24/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/interedition/microservices">
    <title>interedition/microservices - GitHub</title>
    <dc:date>2011-11-29T11:52:24+00:00</dc:date>
    <link>https://github.com/interedition/microservices</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Microservices developed by a European-funded development collective whose aim it is to promote the interoperability of the tools and methodology we use in the field of digital scholarly editing and research.]]></description>
<dc:subject>rest webservices architecture digitalhumanities dh</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0295c2fc6a06/</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:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:dh"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.interedition.eu/wiki/index.php/About_microservices">
    <title>About microservices - IntereditionWiki</title>
    <dc:date>2011-11-29T11:50:05+00:00</dc:date>
    <link>http://www.interedition.eu/wiki/index.php/About_microservices</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Micro services are small cloud deployed web services supporting specific tasks in (any) digital work flow pertaining to larger scholarly tasks. They are the small reusable web published building blocks of digital scholarly tools. They provide the basic solution to interoperability and sustainability for digital scholarly tools Interedition is striving for.]]></description>
<dc:subject>webservices rest architecture digitalhumanities dh</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5bab34826c01/</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:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:dh"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.simpleframework.org/">
    <title>Simple 4.1.21</title>
    <dc:date>2011-09-22T19:08:05+00:00</dc:date>
    <link>http://www.simpleframework.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The goal of Simple is to bring the power of simplicity to the world of server side Java. The primary focus of the project is to provide a truly embeddable Java based HTTP engine capable of handling enormous loads. Simple provides a truly asynchronous service model, request completion is driven using an internal, transparent, monitoring system. This allows Simple to vastly outperform most popular Java based servers in a multi-tier environment, as it requires only a very limited number of threads to handle very high quantities of concurrent clients. Simple has consistently out performed both commercial and open source Java Servlet engines and has a fully comprehensive API that is as usable for experienced Java developers as it is for beginners. Best of all, Simple is completely free, and is released under the terms of the Apache License, which ensures its availability for use by open source and proprietary developers alike.]]></description>
<dc:subject>java http webservices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:eac27ca3ea4a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:java"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</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="https://github.com/urschrei/pyzotero">
    <title>urschrei/pyzotero - GitHub</title>
    <dc:date>2011-06-28T15:32:36+00:00</dc:date>
    <link>https://github.com/urschrei/pyzotero</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is a first pass at implementing a Python wrapper for the Zotero API.]]></description>
<dc:subject>python zotero webservices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c738c8c4da8c/</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:zotero"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://akara.info/">
    <title>Akara</title>
    <dc:date>2011-06-23T17:00:28+00:00</dc:date>
    <link>http://akara.info/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Akara is a platform for developing data services available on the Web, using REST architecture. Akara is open source software written in Python and C.]]></description>
<dc:subject>python rest webservices pipeline composition</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5764330a7e6f/</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:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pipeline"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:composition"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://wiki.xml3k.org/Akara/Architecture/Pipelines">
    <title>Akara/Architecture/Pipelines - xml3k Wiki</title>
    <dc:date>2011-06-23T16:59:42+00:00</dc:date>
    <link>http://wiki.xml3k.org/Akara/Architecture/Pipelines</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Akara is specialized for delivering data services, and to a particular set of architectural best practices for doing so. Two of the key points are:

RESTful principles (to maximize the utility, reuseability and integration of resources)
Service composition, and its corollary, divide-and-conquer.
In "the akara way", complex services are combinations of simpler services, which might in turn be combinations of even simpler services, all the way down to the unit transform, which is a simple, independent (i.e. not coupled to other services), highly cohesive conversion from a simple data input to a simple data output.

These combinations of simpler services in Akara are called "Pipelines".]]></description>
<dc:subject>rest webservices pipeline composition</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d11c6e9fabe4/</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:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pipeline"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:composition"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://wiki.xml3k.org/Akara/Architecture">
    <title>Akara/Architecture - xml3k Wiki</title>
    <dc:date>2011-06-23T16:58:49+00:00</dc:date>
    <link>http://wiki.xml3k.org/Akara/Architecture</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Akara provides a pipeline-based services model, implemented for invocation using REST methods. Services are identified by ID (URI), and are made available at one or more mount points (URLs). Services are abstracted through the REST model so that, for example, if you make a request of an AKara instance, it might be that specific Akara instance that executes the service, or it might be acting as some form of intermediary to other capability, whether in the form of another Akara instance or a completely different technology.

This basic service abstraction system supports complicated service choreography, including round-robin, load-balancing, a race of parallel invocations (e.g. to satisfy emergency processing requests), or even through some sort of scoring system (i.e. I prefer Akara to FooTransformer for XSLT, if available). Improtantly, this flexibility comes without the excess baggage of many "SOA" service models.]]></description>
<dc:subject>rest webservices pipeline</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:48241e33a064/</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:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pipeline"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://cse.unl.edu/~kstolee/icse2011.pdf">
    <title>Refactoring Pipe-like Mashups for End-User Programmers</title>
    <dc:date>2011-06-17T20:35:50+00:00</dc:date>
    <link>http://cse.unl.edu/~kstolee/icse2011.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Mashups are becoming increasingly popular as end users are able to easily access, manipulate, and compose data from many web sources. We have observed, however, that mashups tend to suffer from deficiencies that propagate as mashups are reused. To address these deficiencies, we would like to bring some of the benefits of software engineering techniques to the end users creating these pro- grams. In this work, we focus on identifying code smells indicative of the deficiencies we observed in web mashups programmed in the popular Yahoo! Pipes environment. Through an empirical study, we explore the impact of those smells on end-user programmers and observe that users generally prefer mashups without smells. We then introduce refactorings targeting those smells, reducing the complexity of the mashup programs, increasing their abstraction, updating broken data sources and dated components, and standard- izing their structures to fit the community development patterns. Our assessment of a large sample of mashups shows that smells are present in 81% of them and that the proposed refactorings can re- duce the number of smelly mashups to 16%, illustrating the poten- tial of refactoring to support the thousands of end users program- ming mashups.]]></description>
<dc:subject>webservices composition design interface rest</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:72345a242e1a/</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:composition"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
</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/index.htm">
    <title>Wikipedia Miner - Home</title>
    <dc:date>2011-05-17T19:28:03+00:00</dc:date>
    <link>http://wikipedia-miner.sourceforge.net/index.htm</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 textmining nlp webservices tools datamining</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:992947faf4a5/</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:textmining"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nlp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:datamining"/>
</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://code.google.com/p/google-refine/wiki/ReconciliationServiceApi">
    <title>ReconciliationServiceApi - google-refine - Specification for a standard reconciliation service API. - Google Refine, a power tool for working with messy data (formerly Freebase Gridworks) - Google Project Hosting</title>
    <dc:date>2011-03-27T17:43:15+00:00</dc:date>
    <link>http://code.google.com/p/google-refine/wiki/ReconciliationServiceApi</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A reconciliation service is a web service that, given some text which is a name or label for something, and optionally some additional details, returns a ranked list of potential entities matching the criteria.]]></description>
<dc:subject>naming authority webservices reconciliation dataprocessing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:97af484410a7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authority"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reconciliation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:dataprocessing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.datasciencetoolkit.org/">
    <title>Data Science Toolkit</title>
    <dc:date>2011-03-24T20:11:10+00:00</dc:date>
    <link>http://www.datasciencetoolkit.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A collection of the best open data sets and open-source tools for data science, wrapped in an easy-to-use REST/JSON API with command line, Python and Javascript interfaces. Available as a self-contained VM or EC2 AMI that you can deploy yourself.]]></description>
<dc:subject>data tools nlp ec2 webservices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ae52f8f6b8a3/</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:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nlp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ec2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.loggly.com/product/">
    <title>Product | Loggly</title>
    <dc:date>2011-02-20T18:23:40+00:00</dc:date>
    <link>http://www.loggly.com/product/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Loggly helps you collect, index, and store all your log data and then makes it accessible through search for analysis and reporting. All this is done without having to download or install anything on your servers.]]></description>
<dc:subject>logging webservices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7cc5bdb3ab14/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:logging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.pusherapp.com/">
    <title>Pusher - Realtime client push powered by HTML5 websockets, beyond AJAX</title>
    <dc:date>2010-10-14T18:35:09+00:00</dc:date>
    <link>http://www.pusherapp.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Allow your users to collaborate in realtime
Add live status updates and messages
broadcast events to everyone viewing a page]]></description>
<dc:subject>realtime collaboration javascript webservices websockets html</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:299f7063d1cc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:websockets"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
</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://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://www.odata.org/">
    <title>Open Data Protocol (OData)</title>
    <dc:date>2010-04-14T17:02:19+00:00</dc:date>
    <link>http://www.odata.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today. OData does this by applying and building upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores.]]></description>
<dc:subject>atom data webservices standards linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:53230612ea68/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:atom"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<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:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://hurl.it/">
    <title>hurl</title>
    <dc:date>2009-10-22T17:14:15+00:00</dc:date>
    <link>http://hurl.it/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Hurl makes HTTP requests.]]></description>
<dc:subject>webservices debugging documentation</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:554b8a7f0281/</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:debugging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://authority.ddbc.edu.tw/">
    <title>佛學名相規範資料庫 / Buddhist Authority Database Project</title>
    <dc:date>2009-05-30T17:49:17+00:00</dc:date>
    <link>http://authority.ddbc.edu.tw/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[These databases integrate information from various projects at the Library and Information Center at Dharma Drum Buddhist College. By providing information on Chinese calendar dates, as well as an onomasticon of person and place names from Buddhist sources they help with disambiguation and geo-spatial referencing of names and dates. The data is openly available through various web-services.
]]></description>
<dc:subject>china authority database research history names buddhism opendata webservices digitalhumanities</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:920372782cd0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:china"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authority"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:names"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:buddhism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opendata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bitbucket.org/jespern/django-piston/wiki/Home">
    <title>jespern / django-piston / wiki / Home — bitbucket.org</title>
    <dc:date>2009-04-30T19:28:56+00:00</dc:date>
    <link>http://bitbucket.org/jespern/django-piston/wiki/Home</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A mini-framework for Django for creating RESTful APIs.
]]></description>
<dc:subject>django rest api code framework webservices</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:76a7f4268a97/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:django"/>
	<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:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://revcanonical.appspot.com/">
    <title>rev=canonical: url shortening that doesn't hurt the internet</title>
    <dc:date>2009-04-11T18:11:55+00:00</dc:date>
    <link>http://revcanonical.appspot.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[RevCanonical is url shortening with a twist. Instead of creating its own super short versions of links, it checks to see if the link owner has published a shortened version of the given page using HTML link element. If not, we just return the original URL. And you should bug the link owner about providing a better alternative.
]]></description>
<dc:subject>web architecture webservices linking hypertext html standards</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:006478b9f7b6/</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:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypertext"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.flickr.com/blog/2009/03/18/building-fast-client-side-searches/">
    <title>Code: Flickr Developer Blog » Building Fast Client-side Searches</title>
    <dc:date>2009-03-25T18:14:49+00:00</dc:date>
    <link>http://code.flickr.com/blog/2009/03/18/building-fast-client-side-searches/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Fetching the data using a dynamically generated script tag... the difference in performance was shocking.
]]></description>
<dc:subject>search javascript performance webservices ajax ui json</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:9ad9a6719dfc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ajax"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:json"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://developer.yahoo.com/yql/">
    <title>Yahoo! Query Language - YDN</title>
    <dc:date>2009-03-25T18:09:15+00:00</dc:date>
    <link>http://developer.yahoo.com/yql/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The YQL platform provides a single endpoint service that enables developers to query, filter and combine data across Yahoo! and beyond. YQL exposes a SQL-like SELECT syntax that that is both familiar to developers and expressive enough for getting the right data.
]]></description>
<dc:subject>semweb api webservices yahoo</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:c835b8d3c283/</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:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:yahoo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://developer.yahoo.com/geo/">
    <title>Yahoo! GeoPlanet - YDN</title>
    <dc:date>2009-03-25T18:08:24+00:00</dc:date>
    <link>http://developer.yahoo.com/geo/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Yahoo! GeoPlanet is a resource for managing all geo-permanent named places on Earth. It provides the geographic developer community with the vocabulary and grammar to describe the world's geography in an unequivocal, permanent, and language-neutral manner.
]]></description>
<dc:subject>maps gis api place gazetteer webservices identity yahoo</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:45d5bf000358/</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:gis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:place"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:gazetteer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:yahoo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://documentscompass.org/">
    <title>Digital documentry editions assistance for scholars and publishers</title>
    <dc:date>2009-01-26T20:04:20+00:00</dc:date>
    <link>http://documentscompass.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Documents Compass provides non-profit assistance to those who are engaged in or planning documentary editing projects in the electronic age.
]]></description>
<dc:subject>metadata tools editing webservices digitalhumanities documentary</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:432dd54e6df4/</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:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentary"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.loc.gov/standards/sru/oasis.html">
    <title>SRU/CQL Standardization in OASIS</title>
    <dc:date>2009-01-15T16:54:50+00:00</dc:date>
    <link>http://www.loc.gov/standards/sru/oasis.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The premise behind dynamic bindings is that any search engine, even one that existed prior to development of the standard, need only to provide a dynamic binding -  a self-description. It need make no other changes in order to be accessible. A client will be able to access any search engine that provides a description, if only it implements the capability to read and interpret the description and use it to formulate a request (including a query) and interpret the response.
]]></description>
<dc:subject>metadata search standards webservices IR</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:199acae26fb8/</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:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:IR"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.dlib.org/dlib/january09/denenberg/01denenberg.html">
    <title>Search Web Services - The OASIS SWS Technical Committee Work: The Abstract Protocol Definition, OpenSearch Binding, and SRU/CQL 2.0</title>
    <dc:date>2009-01-15T16:53:34+00:00</dc:date>
    <link>http://www.dlib.org/dlib/january09/denenberg/01denenberg.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The OASIS Search Web Services Technical Committee is developing search and retrieval web services, integrating various approaches under a unifying model, an Abstract Protocol Definition.
]]></description>
<dc:subject>metadata search standards webservices IR</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:7d253455e424/</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:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:IR"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.gbv.de/wikis/cls/Getting_started_with_SeeAlso">
    <title>Getting started with SeeAlso</title>
    <dc:date>2008-11-18T00:39:48+00:00</dc:date>
    <link>http://www.gbv.de/wikis/cls/Getting_started_with_SeeAlso</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The SeeAlso Linkserver API documentation is intended for web developers that want to write dynamic web pages that include additional links, or to developers that want to provide links and other information to specific resources that people can include in their web pages.
]]></description>
<dc:subject>library webservices api documentation hypermedia</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:a9ce3b6f2c04/</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:webservices"/>
	<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:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/apis/spreadsheets/developers_guide_python.html">
    <title>Developer's Guide: Python - Google Spreadsheets APIs and Tools - Google Code</title>
    <dc:date>2008-09-30T21:39:21+00:00</dc:date>
    <link>http://code.google.com/apis/spreadsheets/developers_guide_python.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Google Spreadsheets Data API allows client applications to view and update Spreadsheets content in the form of Google Data API feeds. Your client application can request a list of a user's spreadsheets, edit or delete content in an existing Spreadsheets worksheet, and query the content in an existing Spreadsheets worksheet.
]]></description>
<dc:subject>python google api spreadsheet database webservices</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:6639766259e2/</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:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:spreadsheet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://openguid.net/services/">
    <title>Services</title>
    <dc:date>2008-09-26T13:45:46+00:00</dc:date>
    <link>http://openguid.net/services/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Open GUID consists of the following services to manage web identity: Finding existing unique web identifiers. Establishing new unique web identifiers. Associating legacy identifiers with an open one. Registering identical classes and instances in web ontologies.
]]></description>
<dc:subject>semweb identity registry search tools webservices</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:2d35a6caf84b/</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:identity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:registry"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://jets3t.s3.amazonaws.com/index.html">
    <title>JetS3t</title>
    <dc:date>2008-09-08T18:23:02+00:00</dc:date>
    <link>http://jets3t.s3.amazonaws.com/index.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[JetS3t is a free, open-source Java toolkit and application suite for the Amazon Simple Storage Service (Amazon S3).
]]></description>
<dc:subject>java webservices tools code storage</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:299565854a6d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:java"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:storage"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/p/argot-hub/wiki/GettingStartedDeployment">
    <title>GettingStartedDeployment - argot-hub - Google Code - How to deploy your metadata.</title>
    <dc:date>2008-08-15T03:24:39+00:00</dc:date>
    <link>http://code.google.com/p/argot-hub/wiki/GettingStartedDeployment</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Whilst there are many ways to publish metadata, we're going to focus on the use of RDFa, and how to either embed the information in web-pages, or provide a separate XML feed.
]]></description>
<dc:subject>rdfa datarss howto webservices metadata</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:7d95d6d725d4/</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:datarss"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://labs.ideeinc.com/multicolr/#colors=666666,999966,663366;">
    <title>Multicolr Search Lab - Idée Inc.</title>
    <dc:date>2008-07-10T14:15:53+00:00</dc:date>
    <link>http://labs.ideeinc.com/multicolr/#colors=666666,999966,663366;</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[We extracted the colours from 3 million “interesting” Flickr images. Using our visual similarity technology you can navigate the collection by colour.
]]></description>
<dc:subject>color image search webservices visualweb</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:6ea5b1568c41/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:color"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:image"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualweb"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.oclc.org/research/projects/termservices/">
    <title>Terminology Services [OCLC - Projects]</title>
    <dc:date>2008-07-08T10:48:53+00:00</dc:date>
    <link>http://www.oclc.org/research/projects/termservices/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This project provides Web-based services for controlled vocabularies.
]]></description>
<dc:subject>webservices vocabularies semweb ontology thesaurus</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:229595ba2739/</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:vocabularies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:thesaurus"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://atomserver.codehaus.org/">
    <title>AtomServer</title>
    <dc:date>2008-07-08T10:48:53+00:00</dc:date>
    <link>http://atomserver.codehaus.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[AtomServer is a generic data store implemented as a REST-ful web service. It is designed as a GData-style Atom Store.
]]></description>
<dc:subject>atom java database webservices publishing platform</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:f9e059bac8c1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:atom"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:java"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:platform"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://outgoing.typepad.com/outgoing/2008/06/linking-to-worl.html">
    <title>Outgoing: Linking to WorldCat Identities</title>
    <dc:date>2008-06-26T15:56:01+00:00</dc:date>
    <link>http://outgoing.typepad.com/outgoing/2008/06/linking-to-worl.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A summary of the current API, as of June 2008.
]]></description>
<dc:subject>library identity authority api webservices</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:8612f7a97fb3/</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:identity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authority"/>
	<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://xisbn.worldcat.org/xisbnadmin/xoclcnum/index.htm">
    <title>WorldCat Web service: xISBN [OCLC - WorldCat Affiliate tools]: xOCLCNUM</title>
    <dc:date>2008-05-26T08:37:22+00:00</dc:date>
    <link>http://xisbn.worldcat.org/xisbnadmin/xoclcnum/index.htm</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Submit an OCLC number to this service, and it returns a list of related OCLC numbers and selected metadata.
]]></description>
<dc:subject>library cataloging metadata bibliography webservices identity</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:bb90379f014a/</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:cataloging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bibliography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identity"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://davidkellogg.com/wiki/Main_Page">
    <title>PlainOldWebserver</title>
    <dc:date>2008-03-28T06:24:17+00:00</dc:date>
    <link>http://davidkellogg.com/wiki/Main_Page</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[POW is a fully-functional open source (GPL) webserver that works inside your browser.
]]></description>
<dc:subject>javascript web tools webservices interface local firefox</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:411e03425096/</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:web"/>
	<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:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:local"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:firefox"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/p/hkit/">
    <title>hkit - Google Code</title>
    <dc:date>2008-03-27T16:06:01+00:00</dc:date>
    <link>http://code.google.com/p/hkit/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[hkit is a simple PHP5 tool for extracting common microformats from a page.
]]></description>
<dc:subject>microformats metadata webservices xml json php</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:a41b48630ab2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:microformats"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:json"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:php"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/p/mf-optimus/">
    <title>mf-optimus - Google Code</title>
    <dc:date>2008-03-27T16:04:55+00:00</dc:date>
    <link>http://code.google.com/p/mf-optimus/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Easily transform your microformatted content to nice, clean, easily digestible, XML, JSON or JSON-P. You can also easily set ﬁlters to only receive particular formats.
]]></description>
<dc:subject>microformats metadata webservices xml json code</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:7dd96159ecab/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:microformats"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:json"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://doc.s3.amazonaws.com/proposals/post.html">
    <title>Amazon S3: Browser-Based Uploads using POST</title>
    <dc:date>2008-03-26T04:42:05+00:00</dc:date>
    <link>http://doc.s3.amazonaws.com/proposals/post.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Your webserver can now serve a standard HTML form that will allow your users to upload their content directly into Amazon S3 on your behalf.
]]></description>
<dc:subject>rest webservices database storage</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:13f17be1f680/</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:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:storage"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/p/nose-trestle/">
    <title>nose-trestle - Google Code</title>
    <dc:date>2008-03-19T15:51:52+00:00</dc:date>
    <link>http://code.google.com/p/nose-trestle/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Trestle is a nose plugin that enables you to write testable documentation for web apps.
]]></description>
<dc:subject>python rest webservices testing tools code</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:21a0afbe0e15/</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:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://opencalais.com/documentation/calais-web-service-api">
    <title>OpenCalais</title>
    <dc:date>2008-03-11T16:45:58+00:00</dc:date>
    <link>http://opencalais.com/documentation/calais-web-service-api</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Calais web service allows you to automatically annotate your content with rich semantic metadata, including Entities like People and Companies and Events & Facts like Acquisitions and Management Changes.
]]></description>
<dc:subject>nlp webservices entitydetection categorization</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:9a2c0e15fd45/</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:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:entitydetection"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:categorization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://featureserver.org/">
    <title>FeatureServer</title>
    <dc:date>2008-02-14T04:24:52+00:00</dc:date>
    <link>http://featureserver.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Using standard HTTP methods, you can fetch a representation of a feature or a collection of features, add new data to the service, or delete data from the service.
]]></description>
<dc:subject>maps GIS rest webservices annotation</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:0fbea68c80ac/</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:GIS"/>
	<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:annotation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://analyze.echonest.com/AudioAnalysis.html">
    <title>The Echo Nest API</title>
    <dc:date>2008-01-29T19:39:52+00:00</dc:date>
    <link>http://analyze.echonest.com/AudioAnalysis.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The music analyzer API can help power music visualization, music games, artistic installations, and DJ applications with a much deeper level of music structure understanding.
]]></description>
<dc:subject>audio analysis api music metadata tools webservices</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:01fc8c36a9a0/</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:analysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:music"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/apis/gdata/json.html">
    <title>Using JSON with Google Data APIs - Google Data APIs - Google Code</title>
    <dc:date>2008-01-18T05:35:08+00:00</dc:date>
    <link>http://code.google.com/apis/gdata/json.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Google's mapping of Atom to JSON.
]]></description>
<dc:subject>atom json webservices reference</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:ab51953bd22b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:atom"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:json"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.basiscraft.com/">
    <title>Flower</title>
    <dc:date>2008-01-14T19:55:33+00:00</dc:date>
    <link>http://www.basiscraft.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Flower is a new kind of user programmable web service, especially well suited for applications which process, store, and query XML data sets.
]]></description>
<dc:subject>xml webservices tools opensource xquery xslt framework rest</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:81f6285d532a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xquery"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xslt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rest"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.snee.com/bobdc.blog/2008/01/scraping_and_linked_data.html">
    <title>bobdc.blog: Scraping and linked data</title>
    <dc:date>2008-01-11T18:33:21+00:00</dc:date>
    <link>http://www.snee.com/bobdc.blog/2008/01/scraping_and_linked_data.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Somehow, code monkeys surrounded by earth-toned cubicle fabric think that it makes them resemble DJs surrounded by crates of vinyl if they use musical buzzwords to refer to the act of combining multiple things into a new one.
]]></description>
<dc:subject>remix webservices humor</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:93f3f63aa0be/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:remix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:humor"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.couchdbwiki.com/index.php?title=HTTP_Doc_API#Modify_Multiple_Documents_with_a_Single_Request">
    <title>HTTP Doc API - CouchDb</title>
    <dc:date>2008-01-10T23:19:15+00:00</dc:date>
    <link>http://www.couchdbwiki.com/index.php?title=HTTP_Doc_API#Modify_Multiple_Documents_with_a_Single_Request</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[CouchDB provides a bulk insert/update feature.
]]></description>
<dc:subject>webservices database reference</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:473b2dbcd140/</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:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/p/httplib2/">
    <title>httplib2</title>
    <dc:date>2008-01-10T22:52:31+00:00</dc:date>
    <link>http://code.google.com/p/httplib2/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A comprehensive HTTP client library that supports many features left out of other HTTP libraries.
]]></description>
<dc:subject>python webservices library tools</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:a3a4fa22a1eb/</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:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mozy.com/">
    <title>Mozy Online Backup: Simple, Automatic, Secure</title>
    <dc:date>2008-01-09T19:25:46+00:00</dc:date>
    <link>http://mozy.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Back up all of your photos, music and documents on your home computer for only $4.95 per month.
]]></description>
<dc:subject>backup webservices</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:7a4b465703d1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:backup"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.dil.ie/about.asp">
    <title>eDIL Electronic Dictionary of the Irish Language</title>
    <dc:date>2008-01-07T20:42:14+00:00</dc:date>
    <link>http://www.dil.ie/about.asp</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A digital edition of the complete contents of the Royal Irish Academy’s Dictionary of the Irish Language based mainly on Old and Middle Irish materials.
]]></description>
<dc:subject>ireland neh2007 language reference digitization webservices</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:1ce370e97e5d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ireland"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:neh2007"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.amazon.com/gp/browse.html?node=342335011">
    <title>Amazon Simple DB</title>
    <dc:date>2007-12-14T18:02:24+00:00</dc:date>
    <link>http://www.amazon.com/gp/browse.html?node=342335011</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Amazon SimpleDB is a web service for running queries on structured data in real time.
]]></description>
<dc:subject>distributed database webservices</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:19c8c1f6a154/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.html">
    <title>OASIS Specification Template: Search Web Services</title>
    <dc:date>2007-11-09T15:56:03+00:00</dc:date>
    <link>http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Search web service is a means of opening a database to external enquiry in a standardized manner that facilitates discovery of query and response possibilities and makes it possible for heterogeneous databases to be queried simultaneously with the sam
]]></description>
<dc:subject>search webservices standards</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:58862a6200bd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://pipes.deri.org/">
    <title>Semantic Web Pipes</title>
    <dc:date>2007-11-03T15:44:36+00:00</dc:date>
    <link>http://pipes.deri.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Using Semantic Web Pipes you can fetch, mix and process RDF files published on the Web.
]]></description>
<dc:subject>semweb tools webservices metadata</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:e1886cac749c/</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:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://developer.amazonwebservices.com/connect/kbcategory.jspa?categoryID=87">
    <title>Amazon EC2 Technical Documentation</title>
    <dc:date>2007-11-02T19:51:15+00:00</dc:date>
    <link>http://developer.amazonwebservices.com/connect/kbcategory.jspa?categoryID=87</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Docs for Amazon's Elastic Computing Cloud.
]]></description>
<dc:subject>distributed computers reference documentation webservices</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:ab9c267cda44/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:computers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>