<?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://www.spinellis.gr/sw/dgsh/"/>
	<rdf:li rdf:resource="https://coko.foundation/technology/"/>
	<rdf:li rdf:resource="https://github.com/mangalam-research/wed"/>
	<rdf:li rdf:resource="http://symogih.org/?q=type-of-knowledge-unit-classes-tree"/>
	<rdf:li rdf:resource="http://company-mode.github.io/"/>
	<rdf:li rdf:resource="http://www.ligatus.org.uk/node/762"/>
	<rdf:li rdf:resource="https://github.com/sebastian-meier/d3.sketchy"/>
	<rdf:li rdf:resource="http://cwmemory.com/2015/06/08/open-notes-open-book/"/>
	<rdf:li rdf:resource="http://scholarlymarkdown.com/"/>
	<rdf:li rdf:resource="http://whitneyannetrettien.com/whiki/index.php?title=Main_Page"/>
	<rdf:li rdf:resource="http://bl.ocks.org/mbostock/e2a20d86124693ef0f93"/>
	<rdf:li rdf:resource="http://huni.net.au/"/>
	<rdf:li rdf:resource="https://gforge.inria.fr/projects/cendari-vre/"/>
	<rdf:li rdf:resource="http://www.aviz.fr/Research/CENDARI"/>
	<rdf:li rdf:resource="http://simperium.com/"/>
	<rdf:li rdf:resource="https://openscienceframework.org/project/4znZP/wiki/home/"/>
	<rdf:li rdf:resource="http://orgmode.org/"/>
	<rdf:li rdf:resource="http://threads2.scripting.com/2013/april/introducingFargo"/>
	<rdf:li rdf:resource="http://notational.net/"/>
	<rdf:li rdf:resource="http://www.cendari.eu/"/>
	<rdf:li rdf:resource="http://hangingtogether.org/?p=2621"/>
	<rdf:li rdf:resource="https://github.com/cooperhewitt/solr-whosonfirst"/>
	<rdf:li rdf:resource="http://pkp.sfu.ca/omp"/>
	<rdf:li rdf:resource="http://www.garshol.priv.no/blog/231.html"/>
	<rdf:li rdf:resource="http://prose.io/about.html"/>
	<rdf:li rdf:resource="http://interior.substance.io/"/>
	<rdf:li rdf:resource="http://createjs.org/"/>
	<rdf:li rdf:resource="http://www.alex-reid.net/2012/07/what-about-massive-open-online-scholarship.html"/>
	<rdf:li rdf:resource="http://drupal.forhumanists.org/book/when-not-use-drupal"/>
	<rdf:li rdf:resource="http://www.loc.gov/standards/datetime/pre-submission.html"/>
	<rdf:li rdf:resource="http://rbm.acrl.org/content/10/2/95.full.pdf"/>
	<rdf:li rdf:resource="http://www.rbms.info/conferences/preconfdocs/2011/SeminarCAll.pdf#page=18"/>
	<rdf:li rdf:resource="http://archivists.metapress.com/content/l3h27j5x8716586q/?p=7b722a6cc0c045b39d693d95a77c159b&amp;pi=4"/>
	<rdf:li rdf:resource="http://hangingtogether.org/?p=1690"/>
	<rdf:li rdf:resource="http://viejs.org/"/>
	<rdf:li rdf:resource="http://www.iks-project.eu/"/>
	<rdf:li rdf:resource="http://incubator.apache.org/stanbol/"/>
	<rdf:li rdf:resource="http://www.papyri.info/"/>
	<rdf:li rdf:resource="http://en.wikisource.org/wiki/Thoms,_William_John_(DNB00)"/>
	<rdf:li rdf:resource="http://nq.oxfordjournals.org/"/>
	<rdf:li rdf:resource="http://www.gutenberg.org/wiki/Notes_and_Queries_(Bookshelf)"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://www.spinellis.gr/sw/dgsh/">
    <title>dgsh — directed graph shell</title>
    <dc:date>2017-09-03T20:48:15+00:00</dc:date>
    <link>https://www.spinellis.gr/sw/dgsh/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The directed graph shell, dgsh (pronounced /dæɡʃ/ — dagsh), provides an expressive way to construct sophisticated and efficient big data set and stream processing pipelines using existing Unix tools as well as custom-built components. It is a Unix-style shell (based on bash) allowing the specification of pipelines with non-linear non-uniform operations.]]></description>
<dc:subject>graph programming tools editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:37cc191f1f2c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:graph"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://coko.foundation/technology/">
    <title>CKF Technology – Collaborative Knowledge Foundation</title>
    <dc:date>2017-01-10T19:23:36+00:00</dc:date>
    <link>https://coko.foundation/technology/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Reimagining publishing means shifting to a collaborative webspace with a digital-first process that posits an HTML document at the center of a flexible set of tasks and action. The Coko community is building many tools including a sophisticated web editor and a flexible workflow engine that can be configured for many different content workflows and adjusted easily to fit changing process needs.]]></description>
<dc:subject>scholarlycommunication authoring tools editing editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:653d272eb910/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarlycommunication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authoring"/>
	<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:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/mangalam-research/wed">
    <title>mangalam-research/wed: Wed is a web-based editor that assists users in editing XML documents according to a schema.</title>
    <dc:date>2016-03-10T17:47:09+00:00</dc:date>
    <link>https://github.com/mangalam-research/wed</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Wed is a schema-aware editor for XML documents. It runs in a web browser. The software is at the beta stage. It is being used in a project for editing scholarly articles.]]></description>
<dc:subject>xml tools editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ef48377c4c4b/</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:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://symogih.org/?q=type-of-knowledge-unit-classes-tree">
    <title>Classes de types d'unités de connaissance | SYMOGIH</title>
    <dc:date>2015-12-17T18:20:12+00:00</dc:date>
    <link>http://symogih.org/?q=type-of-knowledge-unit-classes-tree</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The SYMOGIH platform's dictionary of types of knowledge units, allowing "the gradual and evolutionary modeling of historical information."]]></description>
<dc:subject>editorsnotes historical research tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e408f2fee5f7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:historical"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://company-mode.github.io/">
    <title>company-mode for Emacs</title>
    <dc:date>2015-09-08T01:28:08+00:00</dc:date>
    <link>http://company-mode.github.io/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Company is a text completion framework for Emacs. The name stands for "complete anything". It uses pluggable back-ends and front-ends to retrieve and display completion candidates.]]></description>
<dc:subject>emacs programming interface tools editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b1f1911d3ab8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:emacs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.ligatus.org.uk/node/762">
    <title>Export formats | Ligatus</title>
    <dc:date>2015-09-01T18:22:42+00:00</dc:date>
    <link>http://www.ligatus.org.uk/node/762</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[I did a short bibliographical review (attached at the bottom of the post) and it confirms that the idea of the semantic desktop was particularly popular around the middle of the 00's but it never really took off although the open source community embraced it (especially KDE and GNOME projects).]]></description>
<dc:subject>semweb research bibliography editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5cc039e146e3/</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:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bibliography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/sebastian-meier/d3.sketchy">
    <title>sebastian-meier/d3.sketchy</title>
    <dc:date>2015-07-29T12:49:22+00:00</dc:date>
    <link>https://github.com/sebastian-meier/d3.sketchy</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A tool to create sketchy backgrounds, shapes and lines]]></description>
<dc:subject>visualization editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:87b489f49302/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://cwmemory.com/2015/06/08/open-notes-open-book/">
    <title>Open Notes, Open Book | CIVIL WAR MEMORY</title>
    <dc:date>2015-06-08T13:53:34+00:00</dc:date>
    <link>http://cwmemory.com/2015/06/08/open-notes-open-book/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Once I picked up this project after setting it aside for a time I started to think about ways to share the research process with the public. The subject of black Confederates is fraught with misunderstanding not only about the history, but about how to approach the rich repository of relevant primary sources that are accessible online.

I want to be able to track every aspect of the research process, including the slightest revisions in factual and interpretive understanding. Readers would be able to track the secondary sources utilized that broadly frame my understanding of a specific subject right down to the interpretation of individual primary sources.

The best example of this Open Sourcing approach can be found at Caleb McDaniel’s wiki site for his new book project on slave refugees in Texas. I recommend reading about what McDaniel calls “Open Source Notebook History.” It’s a natural extension of much of what I hoped to achieve through my blog posts about the Crater.

It’s worth noting that the goal is not to have people agree with my own conclusions; in fact, my conclusions may be the least important aspect of such a project. Again, it is the process of doing history that I believe would be valuable for many people involved in this debate to see.

The question that I am struggling with is what kind of platform to utilize. I played around with Github, but the interface is a bit too unwieldy for interested readers. Other possibilities include Google pages or some other free wiki software.]]></description>
<dc:subject>editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cf46a3caeb7d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://scholarlymarkdown.com/">
    <title>ScholarlyMarkdown</title>
    <dc:date>2015-03-16T23:19:45+00:00</dc:date>
    <link>http://scholarlymarkdown.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[ScholarlyMarkdown is a syntax/standard/best-practice of scholarly and academic communication that is web-first, semantic XML-second, and LaTeX/Word a close third. Its main goal is to produce a semantically model of a scholarly article based on Markdown input, and translate it to a variety of formats that is suitable for both online scholarly communication, archiving, and publication.]]></description>
<dc:subject>markdown scholarlycommunication editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7321f7f7982e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:markdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarlycommunication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://whitneyannetrettien.com/whiki/index.php?title=Main_Page">
    <title>Whiki</title>
    <dc:date>2014-10-27T17:55:16+00:00</dc:date>
    <link>http://whitneyannetrettien.com/whiki/index.php?title=Main_Page</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is an online commonplace book for Whitney Trettien. You're welcome to use these notes and reading lists to guide you in your own studies. If you have any questions about your rights as a user, please review the Noncommercial-Share Alike 3.0 Unported Creative Commons license which covers any original work produced herein.]]></description>
<dc:subject>editorsnotes notetaking</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6c30094c78c6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:notetaking"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bl.ocks.org/mbostock/e2a20d86124693ef0f93">
    <title>Pencil Sketch</title>
    <dc:date>2014-09-21T15:18:57+00:00</dc:date>
    <link>http://bl.ocks.org/mbostock/e2a20d86124693ef0f93</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This stylized globe uses D3’s in-development geometry pipeline to jitter points before rendering. Points are sampled along great arcs, jittered, and then smoothed using basis-spline interpolation to achieve a hand-drawn effect. The resulting spherical geometry is computed once, allowing faster rendering with arbitrary rotation!]]></description>
<dc:subject>maps notetaking visualization editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:bfdf805e899f/</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:notetaking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://huni.net.au/">
    <title>HuNI | Humanities Networked Infrastructure</title>
    <dc:date>2014-09-12T13:03:30+00:00</dc:date>
    <link>http://huni.net.au/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[HuNI unlocks and combines data from Australia’s most important humanities and creative arts datasets, linking together, for the first time, information about the people, places, events and works that make up the country’s rich cultural heritage.The new HuNI virtual laboratory provides global access to this large-scale aggregate of networked data. The ability for researchers to work independently or collaboratively with the data through discovery, analysis and sharing functions enables researchers from different humanities disciplines to yield new scholarly outcomes and deepen the world’s understanding of Australian culture across space and time.Researcher tools developed elsewhere by others will be able to access the combined HuNI aggregate data service, affording researchers the opportunity to use specialised tools to analyse the data further.]]></description>
<dc:subject>digitalhumanities lod infrastructure editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b300ac081ab9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:lod"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:infrastructure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://gforge.inria.fr/projects/cendari-vre/">
    <title>INRIAGForge: EditorsNotes: Cendari: Project Home</title>
    <dc:date>2014-04-18T17:43:14+00:00</dc:date>
    <link>https://gforge.inria.fr/projects/cendari-vre/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[CENDARI (Virtual Research Environment for historians based on note taking) project source code repos.]]></description>
<dc:subject>history research editorsnotes archives visualization semweb digitalhumanities libraries hci</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2e6dadb85e9a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hci"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.aviz.fr/Research/CENDARI">
    <title>CENDARI</title>
    <dc:date>2014-04-18T17:42:13+00:00</dc:date>
    <link>http://www.aviz.fr/Research/CENDARI</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Collaborative EuropeaN Digital Archive Infrastructure (CENDARI) will provide and facilitate access to existing archives and resources in Europe for the study of medieval and modern European history (specifically the First World War period) through the development of an ‘enquiry environment’.
This environment will increase access to records of historic importance across the European Research Area, creating a powerful new platform for accessing and investigating historical data in a transnational fashion overcoming the national and institutional data silos that now exist. It will leverage the power of the European infrastructure for Digital Humanities (DARIAH) bringing these technical experts together with leading historians and existing research infrastructures (archives, libraries and individual digital projects) within a programme of technical research informed by cutting edge reflection on the impact of the digital age on scholarly practice.]]></description>
<dc:subject>history research editorsnotes archives visualization semweb digitalhumanities libraries hci</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0dad248f6dcc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hci"/>
</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="https://openscienceframework.org/project/4znZP/wiki/home/">
    <title>Open Science Framework | Wiki</title>
    <dc:date>2013-11-19T02:10:10+00:00</dc:date>
    <link>https://openscienceframework.org/project/4znZP/wiki/home/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Open Science Framework (OSF) is part network of research materials, part version control system, and part collaboration software. The purpose of the software is to support the scientist's workflow and help increase the alignment between scientific values and scientific practices.]]></description>
<dc:subject>research collaboration workflow versioning data tools editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:546c573c5016/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:workflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:versioning"/>
	<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:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://orgmode.org/">
    <title>Org mode for Emacs – Your Life in Plain Text</title>
    <dc:date>2013-07-29T18:00:21+00:00</dc:date>
    <link>http://orgmode.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Org mode is for keeping notes, maintaining TODO lists, planning projects, and authoring documents with a fast and effective plain-text system.]]></description>
<dc:subject>emacs notetaking editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:50678f46cde0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:emacs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:notetaking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://threads2.scripting.com/2013/april/introducingFargo">
    <title>Thread: Introducing Fargo!</title>
    <dc:date>2013-07-23T17:03:07+00:00</dc:date>
    <link>http://threads2.scripting.com/2013/april/introducingFargo</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[1. Fargo is a rich, networked text outliner.
2. You can use it as a notepad, todo list, to organize projects, narrate your work, for presentations, brainstorming, design, programming, specs. Investors use Fargo to organize deals, lawyers for cases, educators for course outlines, project leaders to organize the work of team members.
3. Fargo is deceptively simple. You edit documents within documents, nesting them and organizing to as many levels as you need. Reorganize structures with a single gesture. Expand to see the detail or zoom out to see the big picture.
4. Dropbox is brilliant and transformative. Coupled with the deep power of Fargo, you get a profoundly powerful work environment that goes everywhere.
5. You can share outlines with friends and co-workers, or publicly.]]></description>
<dc:subject>notetaking editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:97efad64eab0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:notetaking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://notational.net/">
    <title>Notational Velocity</title>
    <dc:date>2013-07-23T17:01:27+00:00</dc:date>
    <link>http://notational.net/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[NOTATIONAL VELOCITY is an application that stores and retrieves notes. 
It is an attempt to loosen the mental blockages to recording information and to scrape away the tartar of convention that handicaps its retrieval. The solution is by nature nonconformist.]]></description>
<dc:subject>mac osx notetaking editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a7db26f50184/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:mac"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:osx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:notetaking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.cendari.eu/">
    <title>Cendari | Collaborative European Digital Archive Infrastructure</title>
    <dc:date>2013-05-28T16:56:25+00:00</dc:date>
    <link>http://www.cendari.eu/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[CENDARI IS A RESEARCH INFRASTRUCTURE PROJECT AIMED AT INTEGRATING DIGITAL ARCHIVES FOR MEDIEVAL AND MODERN EUROPEAN HISTORY.]]></description>
<dc:subject>digitalhumanities archives infrastructure editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a2ec7f452863/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:infrastructure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://hangingtogether.org/?p=2621">
    <title>hangingtogether.org » Blog Archive » Irreconcilable differences? Name authority control &amp; humanities scholarship</title>
    <dc:date>2013-03-27T15:34:23+00:00</dc:date>
    <link>http://hangingtogether.org/?p=2621</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[We discovered two key issues important to scholars that just don’t mesh well with the library practices represented in name authority files, which VIAF aggregates, due to differences in intended audiences, disciplinary norms, and metadata needs.]]></description>
<dc:subject>authority scholarship naming editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:30b1bf591f40/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authority"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarship"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/cooperhewitt/solr-whosonfirst">
    <title>cooperhewitt/solr-whosonfirst · GitHub</title>
    <dc:date>2013-01-18T13:56:10+00:00</dc:date>
    <link>https://github.com/cooperhewitt/solr-whosonfirst</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[solr-whosonfirst is an experimental Solr 4 core for mapping person names between institutions using a number of tokenizers and analyzers.

]]></description>
<dc:subject>names reconciliation linkeddata editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a030cabdf74b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:names"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reconciliation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://pkp.sfu.ca/omp">
    <title>Open Monograph Press | Public Knowledge Project</title>
    <dc:date>2012-09-22T03:43:24+00:00</dc:date>
    <link>http://pkp.sfu.ca/omp</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[OMP is an open source software platform for managing the editorial workflow required to see monographs, edited volumes and, scholarly editions through internal and external review, editing, cataloguing, production, and publication. OMP will operate, as well, as a press website with catalog, distribution, and sales capacities.]]></description>
<dc:subject>digitalhumanities opensource publishing openaccess editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:212f94b6ec79/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:openaccess"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.garshol.priv.no/blog/231.html">
    <title>RDF triple stores — an overview | Larsblog</title>
    <dc:date>2012-09-22T02:36:24+00:00</dc:date>
    <link>http://www.garshol.priv.no/blog/231.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[There's a huge range of triple stores out there, and it's not trivial to find the one most suited for your exact needs. I reviewed all those I could find earlier this year for a project, and here is the result. I've evaluated the stores against the requirements that mattered for that particular project. I haven't summarized the scores, as everyone's weights for these requirements will be different.

I've deliberately left out rows for whether these tools support things like R2RML, query federation, data binding, SDshare, and so on, even though many of them do. The rationale is that if you pick a triple store that doesn't support these things you can get support anyway through separate components.

I've also deliberately left out cloud-only offerings, as I feel these are a different type of product from the databases you can install and maintain locally.]]></description>
<dc:subject>rdf database comparison editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:920c0602557e/</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:comparison"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://prose.io/about.html">
    <title>Prose · A Content Editor for GitHub</title>
    <dc:date>2012-08-06T00:13:59+00:00</dc:date>
    <link>http://prose.io/about.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Prose is a web-based interface for managing text-based content in your GitHub repositories. Use it to create, edit, and delete files, and save your changes directly to GitHub.]]></description>
<dc:subject>git github blogging tools editing editorsnotes CMS versioning</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c065cfa15c84/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:blogging"/>
	<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:editorsnotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:CMS"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:versioning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://interior.substance.io/">
    <title>Substance · Towards open digital publishing</title>
    <dc:date>2012-08-05T21:26:35+00:00</dc:date>
    <link>http://interior.substance.io/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Substance is an open platform for collaborative composition and sharing of digital documents.]]></description>
<dc:subject>opensource publishing editing authoring editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ebe6d979cd1f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://createjs.org/">
    <title>Create.js - A new kind of web editing interface</title>
    <dc:date>2012-07-31T18:03:43+00:00</dc:date>
    <link>http://createjs.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Create.js is a comprehensive web editing interface for Content Management Systems. It is designed to provide a modern, fully browser-based HTML5 environment for managing content. Create can be adapted to work on almost any content management backend.
The user interface philosophy behind Create is simple: all content that you are allowed to change becomes editable, right there on the page you’re reading. Any modifications you make are retained in your browser and can be sent back to the CMS with a push of a button.]]></description>
<dc:subject>javascript jquery editing interface editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:683477b3d4a1/</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:jquery"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.alex-reid.net/2012/07/what-about-massive-open-online-scholarship.html">
    <title>digital digs: What about massive open online scholarship?</title>
    <dc:date>2012-07-30T15:11:22+00:00</dc:date>
    <link>http://www.alex-reid.net/2012/07/what-about-massive-open-online-scholarship.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[So what would humanities research look like if it were a networked practice integrated with the always-on, real time interactivity of social media?]]></description>
<dc:subject>editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c1abc63c4e11/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://drupal.forhumanists.org/book/when-not-use-drupal">
    <title>When Not to Use Drupal | Drupal for Humanists</title>
    <dc:date>2012-07-11T17:13:22+00:00</dc:date>
    <link>http://drupal.forhumanists.org/book/when-not-use-drupal</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Once you try to move beyond the blog form to integrate the kind of collaborative workspaces and community-oriented functionality typically needed for a moderately collaborative digital project, WordPress is lacking. And if you want to deal with data within that site, and taxonomies and data models and visual representation of such data, then you’re better off in Drupal, which can provide you with all the functionality necessary to present long narratives with embedded images but also provide you the capability to integrate datasets and sophisticated collaborative tools.

For any digital humanities project where the aim is to present time and space-enabled data, you should try out Omeka with the Neatline extensions. If you're just getting started in creating a collection of objects, places, and so on, you should also first take a look at Omeka. The value of Drupal over Omeka comes when your use case becomes too specific or complex and you need to create specific data models, views into the data, and services to connect to your work.

If your project uses detailed markup that covers more than just structural elements of the text, chances are that TEI is the right choice. For simpler text encoding projects, it’s important to weigh the pros and cons of TEI and Drupal as they relate to your goals for your data, amount of technical support available, and workflow. Drupal might be a better choice, but it may also require that you explain to colleagues why you did not use TEI; be thorough in your exploration of both options and clear about the rationale behind your decision if you choose the Drupal path.

Typically, you would not think of using a CMS to deal with rich data visualization and interactivity, but that’s beginning to change, especially with geographic data in Drupal, as will be explained in the Spatial Drupal chapter. Integration of data as content types into Drupal comes with significant overhead and typically provides less functionality and slower performance than hand-crafted scripts. If all one wants to do is show a flat dataset in a well-known visualization pattern, then the costs of building it in Drupal far outweigh any benefit. But, if a project is utilizing some form of visual representation directly in their research, such as geographic representation of the research matter, then Drupal allows that scholar or project to represent a timeline or map-based view of the ongoing, collaborative research.]]></description>
<dc:subject>cms editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4a5f175bdecb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.loc.gov/standards/datetime/pre-submission.html">
    <title>Extended Date/Time Format (EDTF) 1.0 Submission</title>
    <dc:date>2012-05-18T02:22:11+00:00</dc:date>
    <link>http://www.loc.gov/standards/datetime/pre-submission.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This specification defines features to be supported in a date/time string, features considered useful for a wide variety of applications. It takes the form of a profile of / extension to ISO 8601, the International Standard for the representation of dates and times. ISO 8601 describes a large number of date/time formats. On one hand some of these formats are redundant and/or not very useful; to reduce the scope for error and the complexity of software, it seems worthwhile to restrict the supported formats to a smaller set. On the other hand, there are a number of date and time format conventions in common use that are not included in ISO 8601; it seems worthwhile to normalize these.]]></description>
<dc:subject>time standards history bibliography editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:89c47efed903/</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:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bibliography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://rbm.acrl.org/content/10/2/95.full.pdf">
    <title>Progressing Toward Bibliography; or: Organic Growth in the Bibliographic Record</title>
    <dc:date>2012-05-18T01:59:21+00:00</dc:date>
    <link>http://rbm.acrl.org/content/10/2/95.full.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This paper discusses the idea of “progressive bibliography,” or proceeding from minimal to fuller descriptions, as an intellectually valid and pragmatically essential methodology. It examines some already existing approaches and discusses a few of the challenges and further areas of research. While the idea of positive accumulation of knowledge is old, computerized tools and modern information theories enables us to streamline this process to the benefit of patrons and scholars, and so managers of these collections have new tools to tackle ever-increasing backlogs of underprocessed materials.]]></description>
<dc:subject>editorsnotes description bibliography archives</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1875e15a682a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bibliography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.rbms.info/conferences/preconfdocs/2011/SeminarCAll.pdf#page=18">
    <title>Organic Description, Teaching About Stuﬀ, and Computers</title>
    <dc:date>2012-05-18T01:57:23+00:00</dc:date>
    <link>http://www.rbms.info/conferences/preconfdocs/2011/SeminarCAll.pdf#page=18</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Let’s re-imagine how we can  better build digital systems to support narratives that can be used to teach, instruct, and begin discussions.]]></description>
<dc:subject>editorsnotes contours narrative catalogs organization</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2830ae532b21/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:contours"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:narrative"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:catalogs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:organization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://archivists.metapress.com/content/l3h27j5x8716586q/?p=7b722a6cc0c045b39d693d95a77c159b&amp;pi=4">
    <title>Colophons and Annotations: New Directions for the Finding Aid</title>
    <dc:date>2012-05-18T01:54:03+00:00</dc:date>
    <link>http://archivists.metapress.com/content/l3h27j5x8716586q/?p=7b722a6cc0c045b39d693d95a77c159b&amp;pi=4</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The authors argue that finding aids present only singular perspectives of the collections they describe and fail to represent the impact of archivists' work on records and subsequentreinterpretations of collections by archivists and researchers. The authors place these criticisms within the burgeoning postmodern discourse in archival studies and make two concrete suggestions for finding aids that would allow practicing archivists to acknowledge the inherent subjectivity of archival work and to incorporate multiple perspectives into the description of records.]]></description>
<dc:subject>editorsnotes archives</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3496d69320a0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://hangingtogether.org/?p=1690">
    <title>hangingtogether.org » Blog Archive » Thick Description: Fingerprints, Sonnets, and Aboutness in Special Collections</title>
    <dc:date>2012-05-17T20:43:55+00:00</dc:date>
    <link>http://hangingtogether.org/?p=1690</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Archivists and librarians contribute to discovery when they discard illusions of neutrality and express their excitement for the materials and their opinions about their significance.]]></description>
<dc:subject>archives libraries description editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5db8d068efcd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://viejs.org/">
    <title>VIE — Vienna IKS Editables</title>
    <dc:date>2012-04-03T18:52:22+00:00</dc:date>
    <link>http://viejs.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[VIE is a JavaScript library for implementing decoupled Content Management Systems and semantic interaction in web applications.]]></description>
<dc:subject>semweb editorsnotes cms</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8c0c175c1094/</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:editorsnotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cms"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.iks-project.eu/">
    <title>Interactive Knowledge Stack - Semantic CMS - Open Source | IKS - The Semantic CMS Community - Open Source</title>
    <dc:date>2012-04-03T18:51:47+00:00</dc:date>
    <link>http://www.iks-project.eu/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Interactive Knowledge Stack (IKS) is an open source community, whose projects are focused on building an open and flexible technology platform for semantically enhanced Content Management Systems (CMS). If you have a CMS and want to start using semantic technologies in combination with your content then IKS is the project for you. To make integration as easy and painless as possible all features are accessible via RESTful web services.]]></description>
<dc:subject>semweb cms editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:deb9008f9bf9/</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:cms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://incubator.apache.org/stanbol/">
    <title>Apache Stanbol - Welcome to Apache Stanbol (incubating)</title>
    <dc:date>2012-04-03T18:34:27+00:00</dc:date>
    <link>http://incubator.apache.org/stanbol/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Apache Stanbol (currently in incubation) is an open source modular software stack and reusable set of components for semantic content management.

Apache Stanbol components are meant to be accessed over RESTful interfaces to provide semantic services for content management. Thus, one application is to extend traditional content management systems with (internal or external) semantic services.]]></description>
<dc:subject>nlp semweb CMS tools editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8930af197d9a/</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:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:CMS"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.papyri.info/">
    <title>Papyri.info</title>
    <dc:date>2012-02-23T23:53:24+00:00</dc:date>
    <link>http://www.papyri.info/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Papyri.info is dedicated to the study of ancient papyrological documents.  It offers links to papyrological resources, a customized search engine (called the Papyrological Navigator) capable of retrieving information from multiple related collections, and an editing application, the Papyrological Editor, which contributors can use to suggest emendations to PN texts.

The Papyrological Navigator aggregates and displays information from the Advanced Papyrological Information System (APIS), the Duke Databank of Documentary Papyri (DDbDP), the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV), and Bibliographie Papyrologique (BP), as well as links to Trismegistos.]]></description>
<dc:subject>digitalhumanities collaboration editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:55a611eacea1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://en.wikisource.org/wiki/Thoms,_William_John_(DNB00)">
    <title>Thoms, William John (DNB00) - Wikisource</title>
    <dc:date>2012-01-27T22:30:02+00:00</dc:date>
    <link>http://en.wikisource.org/wiki/Thoms,_William_John_(DNB00)</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In 1849 he resumed his project of providing a paper ‘in which literary men could answer one another's questions.’ Dilke encouraged him, with the result that the first number of ‘Notes and Queries’ appeared on 3 Nov. 1849. The name was chosen by Thoms, and he selected for a motto Captain Cuttle's phrase, ‘When found, make a note of.’ In form the journal was modelled on the ‘Somerset House Gazette.’]]></description>
<dc:subject>scholarlycommunication scholarship history editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:227f9f4342d9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarlycommunication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarship"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nq.oxfordjournals.org/">
    <title>Oxford Journals | Humanities | Notes and Queries</title>
    <dc:date>2012-01-27T18:06:56+00:00</dc:date>
    <link>http://nq.oxfordjournals.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Founded under the editorship of the antiquary W J Thoms, the primary intention of Notes and Queries was, and still remains, the asking and answering of readers' questions. It is devoted principally to English language and literature, lexicography, history, and scholarly antiquarianism.]]></description>
<dc:subject>history language literature editorsnotes scholarlycommunication scholarship</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:068db1afd013/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:literature"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarlycommunication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarship"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.gutenberg.org/wiki/Notes_and_Queries_(Bookshelf)">
    <title>Notes and Queries (Bookshelf) - Gutenberg</title>
    <dc:date>2012-01-27T18:04:53+00:00</dc:date>
    <link>http://www.gutenberg.org/wiki/Notes_and_Queries_(Bookshelf)</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Notes and Queries (originally subtitled "a medium of inter-communication for literary men, artists, antiquaries, genealogists, etc") is a London-based, quarterly publication, part academic journal, part correspondence magazine, in which scholars and interested amateurs can exchange knowledge on literature and history.]]></description>
<dc:subject>editorsnotes scholarship scholarlycommunication history literature</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:fe0bb53dc96d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarship"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarlycommunication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:literature"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>