<?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://github.com/WebOrigami/japan-hike-ebook?tab=readme-ov-file"/>
	<rdf:li rdf:resource="https://manifoldapp.org/"/>
	<rdf:li rdf:resource="https://simonwillison.net/2021/Jul/28/baked-data/"/>
	<rdf:li rdf:resource="http://theroadchoseme.com/how-i-self-published-a-professional-paperback-and-ebook-using-latex-and-pandoc?1"/>
	<rdf:li rdf:resource="http://linked-research.270a.info/#conceptual-design"/>
	<rdf:li rdf:resource="https://www.gitbook.io/"/>
	<rdf:li rdf:resource="http://git.macropus.org/vege-table/"/>
	<rdf:li rdf:resource="https://hackage.haskell.org/package/hakyll"/>
	<rdf:li rdf:resource="http://www.metalsmith.io/"/>
	<rdf:li rdf:resource="https://github.com/LinkedDataFragments/Client"/>
	<rdf:li rdf:resource="http://www.against-the-grain.com/2014/02/an-atg-original-university-presses-facing-enormous-tectonic-shift-in-publishing/"/>
	<rdf:li rdf:resource="http://sleepycoders.blogspot.hu/2013/03/sharing-travis-ci-generated-files.html"/>
	<rdf:li rdf:resource="http://www.openbookpublishers.com/"/>
	<rdf:li rdf:resource="http://theappendix.net/"/>
	<rdf:li rdf:resource="http://www.w3.org/TR/publishing-linking/"/>
	<rdf:li rdf:resource="http://www.acm.org/publications/acm-author-izer-service"/>
	<rdf:li rdf:resource="http://pkp.sfu.ca/omp"/>
	<rdf:li rdf:resource="http://interior.substance.io/"/>
	<rdf:li rdf:resource="http://autotelicum.github.com/Smooth-CoffeeScript/literate/histogram.html"/>
	<rdf:li rdf:resource="http://sourceforge.net/projects/dita4publishers/"/>
	<rdf:li rdf:resource="http://www.arl.org/sparc/author/addendum.shtml"/>
	<rdf:li rdf:resource="http://autotelicum.github.com/Smooth-CoffeeScript/interactive/interactive-coffeescript.html"/>
	<rdf:li rdf:resource="http://www.tapasproject.org/"/>
	<rdf:li rdf:resource="https://github.com/johnsensible/django-sendfile"/>
	<rdf:li rdf:resource="https://github.com/schacon/git-scribe"/>
	<rdf:li rdf:resource="http://groups.google.com/group/lod-lam/browse_thread/thread/2f10b9f7b5bf0784"/>
	<rdf:li rdf:resource="http://jaspervdj.be/hakyll/"/>
	<rdf:li rdf:resource="http://figshare.com/"/>
	<rdf:li rdf:resource="https://sites.google.com/site/beyondthepdf/"/>
	<rdf:li rdf:resource="http://www.w3.org/TR/Pointers-in-RDF/"/>
	<rdf:li rdf:resource="http://ai.stanford.edu/~paskin/tiab/index.html"/>
	<rdf:li rdf:resource="http://www.movesinstitute.org/~kolsch/ucthesis/ucthesis.html"/>
	<rdf:li rdf:resource="http://atomserver.codehaus.org/"/>
	<rdf:li rdf:resource="http://www.w3.org/TR/swbp-vocab-pub/"/>
	<rdf:li rdf:resource="http://www.purselipsquarejaw.org/2008/02/boycott-i-think-not.php"/>
	<rdf:li rdf:resource="http://opentextmining.org/wiki/Main_Page"/>
	<rdf:li rdf:resource="http://www.amuniversal.com/index/"/>
	<rdf:li rdf:resource="http://commongroundpublishing.com/about.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://github.com/WebOrigami/japan-hike-ebook?tab=readme-ov-file">
    <title>WebOrigami/japan-hike-ebook</title>
    <dc:date>2024-03-02T14:06:22+00:00</dc:date>
    <link>https://github.com/WebOrigami/japan-hike-ebook?tab=readme-ov-file</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This project explores using the Origami language to create an ebook in the EPUB format.

]]></description>
<dc:subject>publishing book workflow</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:99fdaa22d85e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:book"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:workflow"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://manifoldapp.org/">
    <title>Manifold | Manifold Possibilities</title>
    <dc:date>2023-09-06T01:25:58+00:00</dc:date>
    <link>https://manifoldapp.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Manifold is the friendly, scalable, sustainable way to add the web to your publishing workflow.]]></description>
<dc:subject>academia publishing tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0b046132b842/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:academia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://simonwillison.net/2021/Jul/28/baked-data/">
    <title>The Baked Data architectural pattern</title>
    <dc:date>2022-11-15T19:21:54+00:00</dc:date>
    <link>https://simonwillison.net/2021/Jul/28/baked-data/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Baked Data: bundling a read-only copy of your data alongside the code for your application, as part of the same deployment.]]></description>
<dc:subject>data publishing architecture patterns</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a311d5e1da16/</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:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:patterns"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://theroadchoseme.com/how-i-self-published-a-professional-paperback-and-ebook-using-latex-and-pandoc?1">
    <title>How I self-published a professional paperback and eBook using LaTeX and Pandoc | The Road Chose Me</title>
    <dc:date>2022-03-31T16:10:33+00:00</dc:date>
    <link>http://theroadchoseme.com/how-i-self-published-a-professional-paperback-and-ebook-using-latex-and-pandoc?1</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In this post I’ll run through all the details from the whys to the hows to a final recap with my thoughts about how my decisions worked out.
Given I used to sling code, I’ll include a lot of code samples used to achieve my goals which you can use too.
This post is not intended to teach you the nitty-gritty details of LaTeX, but rather to give a high(ish) level overview of what can be achieved with the tech-stack I settled on.]]></description>
<dc:subject>diy latex publishing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a4dbd8194a2a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:diy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:latex"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://linked-research.270a.info/#conceptual-design">
    <title>Enabling Accessible Knowledge</title>
    <dc:date>2015-03-16T23:22:26+00:00</dc:date>
    <link>http://linked-research.270a.info/#conceptual-design</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Linked Research [15] is a proposal for Web researchers to use the technologies in the native Web stack to access, share and discover knowledge. The Call for Linked Research [16] aims to encourage the “do it yourself” behaviour for sharing and reusing research knowledge. The workflow template for Linked Research is intended to enable better discovery of research objects, and improved user experience and access to research knowledge.]]></description>
<dc:subject>html publishing web scholarlycommunication</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:75b119a2678e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarlycommunication"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.gitbook.io/">
    <title>GitBook</title>
    <dc:date>2014-06-03T22:04:39+00:00</dc:date>
    <link>https://www.gitbook.io/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[GitBook is a tool for using Markdown to write books, which are converted to dynamic websites or exported to static formats like PDF. GitBook also integrates with Git and GitHub, adding a social element to the book creation process.

If you are exporting your book into an HTML page, interactive aspects are also embedable. At the time of this writing, the system provides support for quizzes and JavaScript exercises. However, the tool is fully open source and written using Node.js, so you are free to extend the functionality to meet your needs.]]></description>
<dc:subject>git markdown publishing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f430ec21048f/</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:markdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://git.macropus.org/vege-table/">
    <title>vege-table: the data table that grows</title>
    <dc:date>2014-05-18T01:19:37+00:00</dc:date>
    <link>http://git.macropus.org/vege-table/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The easiest, most resourceful way to harvest, explore and publish a collection of data.

]]></description>
<dc:subject>javascript data sharing publishing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c3f2f5c13138/</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:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sharing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hackage.haskell.org/package/hakyll">
    <title>Hackage: hakyll: A static website compiler library</title>
    <dc:date>2014-04-17T04:44:33+00:00</dc:date>
    <link>https://hackage.haskell.org/package/hakyll</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Hakyll is a static website compiler library. It provides you with the tools to create a simple or advanced static website using a Haskell DSL and formats such as markdown or RST. ]]></description>
<dc:subject>haskell ssg publishing hakyll</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d7bc45b02e36/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:haskell"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ssg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hakyll"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.metalsmith.io/">
    <title>Metalsmith</title>
    <dc:date>2014-04-15T17:44:53+00:00</dc:date>
    <link>http://www.metalsmith.io/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[An extremely simple, pluggable static site generator.]]></description>
<dc:subject>javascript ssg publishing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e840b188c8e1/</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:ssg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/LinkedDataFragments/Client">
    <title>LinkedDataFragments/Client</title>
    <dc:date>2014-02-28T19:10:35+00:00</dc:date>
    <link>https://github.com/LinkedDataFragments/Client</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The issue with the current Linked Data Fragments is that they are either so powerful that their servers suffer from low availability rates (as is the case with SPARQL), or either don't allow efficient querying.

Instead, this client solves queries by accessing basic Linked Data Fragments. 
Each basic Linked Data Fragment offers:

data that corresponds to a basic triple pattern (example).
metadata that consists of the (approximate) total triple count (example).
controls that lead to all other fragments of the same dataset (example).]]></description>
<dc:subject>linkeddata publishing inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c1e1272f2861/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.against-the-grain.com/2014/02/an-atg-original-university-presses-facing-enormous-tectonic-shift-in-publishing/">
    <title>University Presses Facing ‘Enormous Tectonic Shift’ in Publishing | Against-the-Grain.com</title>
    <dc:date>2014-02-19T19:19:43+00:00</dc:date>
    <link>http://www.against-the-grain.com/2014/02/an-atg-original-university-presses-facing-enormous-tectonic-shift-in-publishing/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[University presses have worked hard to establish their reputation for high quality scholarly monographic and journal publication. In 2011, these presses were poised at the forefront of the transition to ebooks in the research sector. Even then, press directors were quick to point to “enormous tectonic shifts” yet to come in the transition to 21st century scholarly publishing.

The past three years have seen major changes and challenges to these presses, with potentially competing publishing initiatives from campus libraries and efforts by many universities to re-evaluate the role and organizational structure of their university presses.

]]></description>
<dc:subject>openaccess libraries scholarlycommunication publishing pubberlin</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:403f828f05e8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:openaccess"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarlycommunication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pubberlin"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sleepycoders.blogspot.hu/2013/03/sharing-travis-ci-generated-files.html">
    <title>Sharing Travis-CI generated files</title>
    <dc:date>2014-01-20T19:51:03+00:00</dc:date>
    <link>http://sleepycoders.blogspot.hu/2013/03/sharing-travis-ci-generated-files.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[There are some things that are generated by your project and it will be nice to make available to the broad audience with each successful update. For example code coverage statistics, pdf of your LaTeX publication, maybe some documentation for your library, or even binary of the application itself.]]></description>
<dc:subject>github publishing documentation howto</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0b4ec1b5e081/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.openbookpublishers.com/">
    <title>Open Book Publishers</title>
    <dc:date>2014-01-17T18:46:34+00:00</dc:date>
    <link>http://www.openbookpublishers.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[At Open Book Publishers we are changing the nature of the traditional academic book. Our books are published in hardback, paperback, pdf and ebook editions, but they also include a free online edition that can be read via our website, or embedded anywhere. We are proud to say that our online editions are currently being accessed by thousands of readers each month in over 125 countries. In addition, our digital publishing model allows us to extend our books well beyond the printed page. On our website, we produce online supplementary material, including extra chapters, reviews, links, image galleries and other digital resources — these can be found on the individual product page for each book.]]></description>
<dc:subject>ebooks publishing openaccess pubberlin</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b97023fb4a76/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ebooks"/>
	<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:pubberlin"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://theappendix.net/">
    <title>The Appendix</title>
    <dc:date>2014-01-17T18:43:45+00:00</dc:date>
    <link>http://theappendix.net/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Appendix is a quarterly journal of experimental and narrative history; though at times outlandish, everything in its pages is as true as the sources allow. The Appendix solicits articles from historians, writers, and artists committed to good storytelling, with an eye for the strange and a suspicion of both jargon and traditional narratives. A creature of the web, its format takes advantage of the flexibility of hypertext and modern web presentation techniques to experiment with and explore the process and method of writing history.]]></description>
<dc:subject>history literature publishing pubberlin</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d63a3d13000a/</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:literature"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pubberlin"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/TR/publishing-linking/">
    <title>Publishing and Linking on the Web</title>
    <dc:date>2013-04-30T16:26:49+00:00</dc:date>
    <link>http://www.w3.org/TR/publishing-linking/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document is intended to inform future social and legal discussions about the architecture of the Web: the ways in which the Web's technical facilities operate to store, publish and retrieve information, and by providing definitions for terminology as used within the Web's technical community. Specifically, this document has the following goals:

Clarify that linking - providing the location of some content - is different in intention from including - embedding content developed elsewhere within your own - and should be treated differently by the law.
Intermediaries, such as proxies and caches, and more controversially, search engines and agggregators that merely refer to or collect content developed elsewhere, should be treated differently than websites that create orginal content.
In many cases, websites put legal restrictions on how the material they make available may be linked or reused. Such restrictions can be better enforced by using mechanisms provided by the web rather than by legal terms of use.]]></description>
<dc:subject>web linking policy publishing law * inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:92faa0ca9f99/</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:linking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:policy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:law"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:*"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.acm.org/publications/acm-author-izer-service">
    <title>ACM AUTHOR-IZER SERVICE — Association for Computing Machinery</title>
    <dc:date>2013-03-29T17:21:17+00:00</dc:date>
    <link>http://www.acm.org/publications/acm-author-izer-service</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[ACM Author-Izer is a unique service that enables ACM authors to generate and post links on either their home page or institutional repository for visitors to download the definitive version of their articles from the ACM Digital Library at no charge.]]></description>
<dc:subject>acm publishing openaccess</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d3a091ee7da5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:acm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:openaccess"/>
</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://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://autotelicum.github.com/Smooth-CoffeeScript/literate/histogram.html">
    <title>Photo histogram in CoffeeKup — Smooth CoffeeScript</title>
    <dc:date>2012-04-06T21:13:49+00:00</dc:date>
    <link>http://autotelicum.github.com/Smooth-CoffeeScript/literate/histogram.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This literate program is interactive in its HTML5 form. Edit a CoffeeScript segment to try it. You can see the generated JavaScript as you modify a CoffeeScript function by typing ‘show name’ after its definition.]]></description>
<dc:subject>coffeescript education publishing interactive</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a5f901a07ad7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:coffeescript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:education"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interactive"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sourceforge.net/projects/dita4publishers/">
    <title>DITA For Publishers | Free software downloads at SourceForge.net</title>
    <dc:date>2012-04-06T16:56:13+00:00</dc:date>
    <link>http://sourceforge.net/projects/dita4publishers/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Provides general-purpose DITA map, topic, and domain specializations for the Publishing industry, as well as supporting processors (e.g., DITA Open Toolkit plugins).]]></description>
<dc:subject>publishing xml tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:545e183b4665/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.arl.org/sparc/author/addendum.shtml">
    <title>Author Rights: Using the SPARC Author Addendum to secure your rights as the author of a journal article (SPARC)</title>
    <dc:date>2012-03-15T21:05:07+00:00</dc:date>
    <link>http://www.arl.org/sparc/author/addendum.shtml</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The SPARC Author Addendum is a legal instrument that modifies the publisher’s agreement and allows you to keep key rights to your articles. The Author Addendum is a free resource developed by SPARC in partnership with Creative Commons <http://www.creativecommons.org> and Science Commons <http://science.creativecommons.org>, established non-profit organizations that offer a range of copyright options for many different creative endeavors.]]></description>
<dc:subject>authors copyright publishing academia authoring authorship openaccess</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:393a591e60ee/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authors"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:academia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authorship"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:openaccess"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://autotelicum.github.com/Smooth-CoffeeScript/interactive/interactive-coffeescript.html">
    <title>Interactive Smooth CoffeeScript</title>
    <dc:date>2012-02-24T02:56:26+00:00</dc:date>
    <link>http://autotelicum.github.com/Smooth-CoffeeScript/interactive/interactive-coffeescript.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Discover the beauty of functional programming in Coffeescript. The source of this book is a literate markdown program/document which produces this code: CoffeeScript, that translates into JavaScript and produces this output.]]></description>
<dc:subject>coffeescript programming tutorial publishing authoring markdown functional</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0b9038cf9e7c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:coffeescript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:markdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:functional"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.tapasproject.org/">
    <title>A New Part of Your Digital Humanities Toolkit | Tapas Project</title>
    <dc:date>2012-01-25T14:30:18+00:00</dc:date>
    <link>http://www.tapasproject.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Tapas is the TEI Archival Publishing and Access Service for scholars and other creators of TEI data who need a place to publish their materials in different forms and ensure it remains accessible over time. Tapas is also for anyone interested in reading and exploring TEI data, and communicating with those that share that interest.]]></description>
<dc:subject>tei publishing digitalhumanities</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:48ac61327ebe/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tei"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/johnsensible/django-sendfile">
    <title>johnsensible/django-sendfile - GitHub</title>
    <dc:date>2011-11-04T12:54:50+00:00</dc:date>
    <link>https://github.com/johnsensible/django-sendfile</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is a wrapper around web-server specific methods for sending files to web clients. This is useful when Django needs to check permissions associated files, but does not want to serve the actual bytes of the file itself. i.e. as serving large files is not what Django is made for.]]></description>
<dc:subject>django publishing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b70736db0314/</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:publishing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/schacon/git-scribe">
    <title>schacon/git-scribe - GitHub</title>
    <dc:date>2011-11-04T11:51:46+00:00</dc:date>
    <link>https://github.com/schacon/git-scribe</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The git-scribe tool is a simple command line toolset to help you use Git, GitHub and Asciidoc to write e-books. This provides tools for setting up the structure, collaborating with co-authors, doing technical and copy-editing, handling translations, taking errata, as well as publishing online, pdf, mobi (Kindle) and epub (iBooks, Nook) versions.]]></description>
<dc:subject>books git publishing writing authoring collaboration</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a66c543e50ae/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:writing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://groups.google.com/group/lod-lam/browse_thread/thread/2f10b9f7b5bf0784">
    <title>Frameworks for publishing vocabularies online - Linked Open Data in Libraries, Archives, &amp; Museums | Google Groups</title>
    <dc:date>2011-10-20T21:10:50+00:00</dc:date>
    <link>http://groups.google.com/group/lod-lam/browse_thread/thread/2f10b9f7b5bf0784</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Survey of frameworks for publishing RDF vocabularies/ontologies online.]]></description>
<dc:subject>semweb linkeddata vocabulary documentation publishing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9aaad2b13274/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:vocabulary"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://jaspervdj.be/hakyll/">
    <title>Hakyll - Home</title>
    <dc:date>2011-04-16T01:56:18+00:00</dc:date>
    <link>http://jaspervdj.be/hakyll/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Hakyll is a Haskell library for generating static sites, mostly aimed at small-to-medium sites and personal blogs. It is written in a very configurable way and uses an xmonad-like DSL for configuration.]]></description>
<dc:subject>haskell publishing ssg</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3316ae015d31/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:haskell"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ssg"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://figshare.com/">
    <title>FigShare</title>
    <dc:date>2011-04-06T14:15:03+00:00</dc:date>
    <link>http://figshare.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Scientific publishing as it stands is an inefficient way to do science on a global scale. A lot of time and money is being wasted by groups around the world duplicating research that has already been carried out. FigShare allows you to share all of your data, negative results and unpublished figures. In doing this, other researchers will not duplicate the work, but instead may publish with your previously wasted figures, or offer collaboration opportunities and feedback on preprint figures.]]></description>
<dc:subject>datasharing research publishing science opendata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:19ce3d0ddda4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:datasharing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:science"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opendata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://sites.google.com/site/beyondthepdf/">
    <title>Beyond the PDF</title>
    <dc:date>2011-01-30T00:26:13+00:00</dc:date>
    <link>https://sites.google.com/site/beyondthepdf/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The goal of the workshop was not to produce a white paper! Rather it was to identify a set of requirements, and a group of willing participants to develop a mandate, open source code and a set of deliverables to be used by scholars to accelerate data and knowledge sharing and discovery . Our starting point, and the only prerequisite to participating, was the belief that we need to move Beyond the PDF (meant to capture a common philosophy, not necessarily to be taken literally).

In a heady moment we might also describe our efforts as the desire to contribute to the development of a free and open digital printing press for the 21st century. A platform, when utilized, moves us beyond a static and disparate data and knowledge representation to a rich integrated content which grows and changes the more we learn. A system (content plus platform) from which a scholar can interact and once evaluated shows improved understanding and interest.]]></description>
<dc:subject>publishing data scholarship tools KR</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0cb3354dd6ca/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarship"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:KR"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/TR/Pointers-in-RDF/">
    <title>Pointer Methods in RDF</title>
    <dc:date>2009-04-09T17:39:49+00:00</dc:date>
    <link>http://www.w3.org/TR/Pointers-in-RDF/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This specification contains a framework for representing pointers - entities that permit identifying a portion or segment of a piece of content - making use of the Resource Description Framework (RDF). It will also describe a number of specific types of pointers that permit portions of a document to be referred to in different ways.
]]></description>
<dc:subject>rdf annotation publishing vocabulary media web standards semweb</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:5e1a45b98344/</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:annotation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:vocabulary"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:media"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ai.stanford.edu/~paskin/tiab/index.html">
    <title>Thesis in a Box</title>
    <dc:date>2008-11-19T22:07:26+00:00</dc:date>
    <link>http://ai.stanford.edu/~paskin/tiab/index.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Thesis in a Box is a LaTeX/PDF framework for easily formatting a doctoral dissertation that obeys the formatting requirements of the University of California, Berkeley.
]]></description>
<dc:subject>latex publishing tools berkeley dissertation</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:441505d2e060/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:latex"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:berkeley"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:dissertation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.movesinstitute.org/~kolsch/ucthesis/ucthesis.html">
    <title>ucthesis latex style</title>
    <dc:date>2008-11-19T21:23:59+00:00</dc:date>
    <link>http://www.movesinstitute.org/~kolsch/ucthesis/ucthesis.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This is a "very quick start guide" for writing dissertations with the ucthesis.cls LaTeX style file.
]]></description>
<dc:subject>latex publishing berkeley dissertation</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:b7a6ee63d690/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:latex"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:berkeley"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:dissertation"/>
</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://www.w3.org/TR/swbp-vocab-pub/">
    <title>Best Practice Recipes for Publishing RDF Vocabularies</title>
    <dc:date>2008-05-20T09:44:59+00:00</dc:date>
    <link>http://www.w3.org/TR/swbp-vocab-pub/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document describes best practice recipes for publishing vocabularies or ontologies on the Web (in RDF Schema or OWL).
]]></description>
<dc:subject>semweb rdf ontology publishing howto</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:de94ec5dcf52/</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:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.purselipsquarejaw.org/2008/02/boycott-i-think-not.php">
    <title>Boycott? I think not.</title>
    <dc:date>2008-02-07T13:33:00+00:00</dc:date>
    <link>http://www.purselipsquarejaw.org/2008/02/boycott-i-think-not.php</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[I fully support open-access scholarship, but find danah boyd's recent post on boycotting "locked-down" journals naive at best, and offensive at worst.First of all, I think she overstates the "lock-down." I've published articles with Sage and Taylor&Francis, and was able to publish almost identical draft versions here. All I did was hand-write that provision onto my contract before I signed it, and no one ever objected.  And while I agree that there is some sort of "black market" economy for exchanging articles, I'm willing to accept this as a viable tactic against an over-arching publication for profit strategy. In my experience, one of the quickest ways to alienate people from your cause is to invalidate existing acts of resistance because they don't fit your model. That's just scientific positivism applied to personal politics, and I don't like playing the "my politics are better than your politics" game.This brings me to my main objection: danah's overall tone is so patronising to academics that I can't help but feel insulted. I mean, really, how do unsupported claims like this one - "If scholars are publishing for audiences of zero, no wonder no one respects them" - help our shared cause of reforming academic publishing?Danah's position disrespects years of scholarship and community, and it dismisses outright the possibility that an academic might find genuine pride, or satisfaction, or joy in such work. Surely good ethnographers would want to ask a scholar what she gets out of a given practice before they tell her, or speak for her? And as an early career academic, I was most unimpressed by being given the option of becoming a "punk" or "conservative" scholar:"Young punk scholars: Publish only in open-access journals in protest, especially if you're in a new field.  This may cost you advancement or tenure, but you know it's the right thing to do...More conservative young scholars: publish what you need to get tenure and then stop publishing in closed venues immediately upon acquiring tenure. I understand why you feel the need to follow the rules. This is fine, but make a point by stopping this practice the moment you don't need it."What is this, high school? I honestly fail to see how this "open" model gives me any more space to manoeuvre as a scholar, or as a human being.In any case, Mel Gregg also takes issue with danah's "capacity to diagnose the pitfalls of an entire industry and the motivations of all of us who choose to work in it" and I appreciated Jason Wilson's comments on how journal publishing actually works. But since I also really like constructive criticism, and I haven't provided any alternatives here, I'll second Alex Halavais' suggestion:"If you want to find the Achilles heal, the catalyst that would get things moving much faster, it's easy enough: follow the money. Pressure NSF, MacArthur, etc., to require open publication for all funded research. Get state legislatures to do the same for state schools: if you get a summer grant or fellowship, your work needs to be published in public, so that the public who paid for it can access it."I encourage Canadian citizens and researchers to contact the following organisations to voice your opinions on these matters:SSHRC  |  NSERC  |  Killam TrustsResearchers can also apply for funding from the Government of Canada's Intellectual Property Mobilization Program (IPM).Canadian Intellectual Property Office  |  HRSDC Learning and Post-Secondary Education | Provincial Ministries of EducationAssociation of Universities and Colleges of Canada  |  Canadian Federation of Students]]></description>
<dc:subject>academia publishing</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:52fd4c6560f5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:academia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://opentextmining.org/wiki/Main_Page">
    <title>OpenTextMining</title>
    <dc:date>2007-11-14T19:55:42+00:00</dc:date>
    <link>http://opentextmining.org/wiki/Main_Page</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Open Text Mining Interface (OTMI) is an initiative from Nature Publishing Group (NPG). It aims to enable scholarly publishers, among others, to disclose their full text for indexing and text-mining purposes but without giving it away in a form that is rea
]]></description>
<dc:subject>academia publishing copyright data nlp standards datamining</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:84c48194fd91/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:academia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nlp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:datamining"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.amuniversal.com/index/">
    <title>Andrews McMeel Universal</title>
    <dc:date>2007-03-27T22:07:00+00:00</dc:date>
    <link>http://www.amuniversal.com/index/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[For more than a quarter of a century, Andrews McMeel Universal and its divisions, Universal Press Syndicate, Andrews McMeel Publishing, LLC, uclick, and AMUSE, have helped define American popular culture.
]]></description>
<dc:subject>pop culture syndication business publishing cartoons humor news newspaper</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:b0f68d44946e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:syndication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cartoons"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:humor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:news"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:newspaper"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://commongroundpublishing.com/about.html">
    <title>Common Ground - About</title>
    <dc:date>2007-03-07T02:41:27+00:00</dc:date>
    <link>http://commongroundpublishing.com/about.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Common Ground has also become extensively involved in software development, built upon the Common Ground Markup Language (CGML).
]]></description>
<dc:subject>publishing authoring code tools xml language p2p collaboration</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:80dde13ea1cc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:p2p"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:collaboration"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>