<?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.poetryfoundation.org/poems/91395/snow-582b58513ffae"/>
	<rdf:li rdf:resource="http://www.kanarinka.com/wp-content/uploads/2015/07/IEEE_Feminist_Data_Visualization.pdf"/>
	<rdf:li rdf:resource="http://programminghistorian.org/lessons/json-and-jq"/>
	<rdf:li rdf:resource="http://guild2910.org/Pelopponesian%20War%20June%2013%202007.pdf"/>
	<rdf:li rdf:resource="https://www.artsy.net/categories"/>
	<rdf:li rdf:resource="http://www.oclc.org/content/dam/research/publications/2016/oclcresearch-organizational-identifiers-and-isni-2016.pdf"/>
	<rdf:li rdf:resource="http://plato.stanford.edu/entries/essential-accidental/#EsseClaiArguForNoni"/>
	<rdf:li rdf:resource="https://mapzen.com/blog/geocoding-places"/>
	<rdf:li rdf:resource="https://github.com/Quartz/bad-data-guide"/>
	<rdf:li rdf:resource="http://cocorahs.blogspot.it/2015/11/a-man-with-his-head-in-clouds.html"/>
	<rdf:li rdf:resource="http://www.snee.com/bobdc.blog/2015/04/running-spark-graphx-algorithm.html"/>
	<rdf:li rdf:resource="http://visual.ly/daylight-saving-time-explained"/>
	<rdf:li rdf:resource="https://www.ideals.illinois.edu/handle/2142/1691"/>
	<rdf:li rdf:resource="http://descriptionguy.com/images/WEBSITE/Documenting-archives-a-guide-for-dummies.pdf"/>
	<rdf:li rdf:resource="http://onlinelibrary.wiley.com/book/10.1002/9781118627747"/>
	<rdf:li rdf:resource="http://vimeo.com/36752317"/>
	<rdf:li rdf:resource="http://www.networkedcorpus.com/"/>
	<rdf:li rdf:resource="http://prezi.com/jr61rhjoqotb/high-accuracy-metadata/"/>
	<rdf:li rdf:resource="http://new-savanna.blogspot.com/2013/10/on-describing-painting.html"/>
	<rdf:li rdf:resource="http://www.jstor.org/stable/2799807"/>
	<rdf:li rdf:resource="http://igniteshow.com/videos/polysemous-terms-did-everyone-understand-your-message"/>
	<rdf:li rdf:resource="https://code.google.com/p/word2vec/"/>
	<rdf:li rdf:resource="http://shapeofdata.wordpress.com/2013/08/06/intrinsic-vs-extrinsic-structure/"/>
	<rdf:li rdf:resource="http://media.aau.dk/null_space_pursuits/2013/07/classification-accuracy-is-not-enough.html"/>
	<rdf:li rdf:resource="http://onlinelibrary.wiley.com/doi/10.1002/bult.2013.1720390511/abstract"/>
	<rdf:li rdf:resource="http://onlinelibrary.wiley.com/doi/10.1002/bult.2013.1720390510/abstract"/>
	<rdf:li rdf:resource="http://fordham.bepress.com/dissertations/AAI3466699/"/>
	<rdf:li rdf:resource="http://www.philosophy.ox.ac.uk/__data/assets/pdf_file/0011/16589/Definition_and_Division.pdf"/>
	<rdf:li rdf:resource="http://faculty.washington.edu/smcohen/PlatoDivision.pdf"/>
	<rdf:li rdf:resource="http://www.orm.net/pdf/EncDBS.pdf"/>
	<rdf:li rdf:resource="http://www.dataprotocols.org/en/latest/data-packages.html"/>
	<rdf:li rdf:resource="http://www.bostonglobe.com/news/politics/2013/04/22/lindsey-graham-fbi-didn-know-tsarnaev-was-russia-because-his-name-was-misspelled/hrRI2TUaKXsQMRLooKkymM/story.html"/>
	<rdf:li rdf:resource="http://aims.fao.org/lode/bd"/>
	<rdf:li rdf:resource="http://www.aiai.ed.ac.uk/~jessicac/psfiles/SIG-SEMIS/issue3-tom-gruber.pdf"/>
	<rdf:li rdf:resource="http://counternotions.com/2013/01/26/idownloader/"/>
	<rdf:li rdf:resource="http://searchengineland.com/facebook-search-not-google-search-145124"/>
	<rdf:li rdf:resource="http://www.thetoolbox.cc/"/>
	<rdf:li rdf:resource="http://kunststube.net/encoding/"/>
	<rdf:li rdf:resource="http://sils.unc.edu/sites/default/files/general/programs/orgranizationgrid2009.pdf"/>
	<rdf:li rdf:resource="http://sils.unc.edu/sites/default/files/general/programs/organizationgrid.pdf"/>
	<rdf:li rdf:resource="http://jsonlint.com/"/>
	<rdf:li rdf:resource="http://eikes.github.com/facetedsearch/"/>
	<rdf:li rdf:resource="http://onlinelibrary.wiley.com/doi/10.1002/asi.22731/abstract"/>
	<rdf:li rdf:resource="http://computationalculture.net/article/what_is_in_pagerank"/>
	<rdf:li rdf:resource="http://www.w3.org/2001/sw/Europe/events/foaf-galway/papers/pp/validating_rdf/"/>
	<rdf:li rdf:resource="http://aclweb.org/anthology-new/E/E12/E12-1051.pdf"/>
	<rdf:li rdf:resource="http://www.ischool.berkeley.edu/newsandevents/events/deanslectures/20121003glushko"/>
	<rdf:li rdf:resource="http://blog.orange11.nl/2012/09/25/whats-so-cool-about-elasticsearch/"/>
	<rdf:li rdf:resource="https://www.cdt.org/blogs/0110apple-ios-6-and-privacy-0"/>
	<rdf:li rdf:resource="http://www.qwantz.com/index.php?comic=2292"/>
	<rdf:li rdf:resource="http://www.oclc.org/research/activities/frbralgorithm.html"/>
	<rdf:li rdf:resource="http://www.librarything.com/review/86646140"/>
	<rdf:li rdf:resource="http://docs.datomic.com/tutorial.html"/>
	<rdf:li rdf:resource="http://docs.datomic.com/schema.html"/>
	<rdf:li rdf:resource="http://codeartisan.blogspot.com/2012/08/hypermedia-programming-lists.html"/>
	<rdf:li rdf:resource="http://andrewgelman.com/2012/09/building-a-regression-model-with-only-27-data-points/"/>
	<rdf:li rdf:resource="http://www.cs.cmu.edu/~nasmith/papers/smith.whitepaper12.pdf"/>
	<rdf:li rdf:resource="http://www.springerlink.com/content/p26q17h071439602/fulltext.pdf?MUD=MP"/>
	<rdf:li rdf:resource="http://blog.semantic-web.at/2012/09/12/state-of-the-art-text-mining-poolparty-extractor-2-1-1-released/"/>
	<rdf:li rdf:resource="http://arxiv.org/help/author_identifiers"/>
	<rdf:li rdf:resource="http://viewshare.org/"/>
	<rdf:li rdf:resource="http://people.cs.umass.edu/~abakalov/papers/jcdl12-lpam.pdf"/>
	<rdf:li rdf:resource="http://ceur-ws.org/Vol-874/paper7.pdf"/>
	<rdf:li rdf:resource="http://www.theparisreview.org/blog/2012/08/30/bullet-points/"/>
	<rdf:li rdf:resource="http://www.digitalhumanities.org/dhq/vol/6/2/000124/000124.html"/>
	<rdf:li rdf:resource="http://turtled.net/"/>
	<rdf:li rdf:resource="http://en.wikipedia.org/wiki/Zachman_Framework"/>
	<rdf:li rdf:resource="http://dret.net/netdret/docs/wilde-cacm2008-document-design-matters/"/>
	<rdf:li rdf:resource="http://www.jenitennison.com/blog/node/171"/>
	<rdf:li rdf:resource="http://dublincore.org/documents/abstract-model/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://www.poetryfoundation.org/poems/91395/snow-582b58513ffae">
    <title>Snow by Louis MacNeice</title>
    <dc:date>2023-08-31T20:51:46+00:00</dc:date>
    <link>https://www.poetryfoundation.org/poems/91395/snow-582b58513ffae</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The room was suddenly rich and the great bay-window was
Spawning snow and pink roses against it
Soundlessly collateral and incompatible:
World is suddener than we fancy it.

World is crazier and more of it than we think,
Incorrigibly plural. I peel and portion
A tangerine and spit the pips and feel
The drunkenness of things being various.

And the fire flames with a bubbling sound for world
Is more spiteful and gay than one supposes— 
On the tongue on the eyes on the ears in the palms of one's hands—
There is more than glass between the snow and the huge roses.

Louis MacNeice, “Snow” from The Collected Poems of Louis MacNeice.  Copyright © 1967 by Louis MacNeice.  Reprinted by permission of David Higham Associates, Ltd.]]></description>
<dc:subject>poetry ontology inls201 inls520 inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f1de3f18e4f5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:poetry"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls201"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.kanarinka.com/wp-content/uploads/2015/07/IEEE_Feminist_Data_Visualization.pdf">
    <title>Feminist Data Visualization</title>
    <dc:date>2017-01-26T17:53:12+00:00</dc:date>
    <link>http://www.kanarinka.com/wp-content/uploads/2015/07/IEEE_Feminist_Data_Visualization.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In this paper, we begin to outline how feminist theory may be productively applied to information visualization research and practice. Other technology- and design-oriented fields such as Science and Technology Studies, Human-Computer Interaction, Digital Humanities, and Geography/GIS have begun to incorporate feminist principles into their research. Feminism is not (just) about women, but rather draws our attention to questions of epistemology – who is included in dominant ways of producing and communicating knowledge and whose perspectives are marginalized. We describe potential applications of feminist theory to influence the information design process as well as to shape the outputs from that process.]]></description>
<dc:subject>visualization feminism sts categories inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e5c1493a0000/</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:feminism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:categories"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://programminghistorian.org/lessons/json-and-jq">
    <title>Reshaping JSON with jq | Programming Historian</title>
    <dc:date>2016-09-06T19:25:19+00:00</dc:date>
    <link>http://programminghistorian.org/lessons/json-and-jq</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Working with data from an art museum API and from the Twitter API, this lesson teaches how to use the command-line utility jq to filter and parse complex JSON files into flat CSV files. This lesson will begin with an overview of the basic operators of the jq query syntax. Next, you will learn progressively more complex ways of connecting these operators together. By the end of the lesson, you will understand how to combine basic operators to create queries that can reshape many types of JSON data.]]></description>
<dc:subject>json tutorial inls520 inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:32eb0cadf9d8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:json"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://guild2910.org/Pelopponesian%20War%20June%2013%202007.pdf">
    <title>The Peloponnesian War and the Future of Reference, Cataloging, and Scholarship in Research Libraries</title>
    <dc:date>2016-09-01T17:11:39+00:00</dc:date>
    <link>http://guild2910.org/Pelopponesian%20War%20June%2013%202007.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The paper is an examination of the overall principles and practices of both reference service and cataloging operations in the promotion of scholarly research, pointing out important differences not just in content available onsite and offsite, but also among necessary search techniques. It specifies the differences between scholarship and quick information seeking, and examines the implications of those differences for the future of cataloging. It examines various proposals that the profession should concentrate its efforts on alternatives to cataloging: relevance ranking, tagging, under-the-hood programming, etc. The paper considers the need for, and requirements of, education of researchers; and it examines in detail many of the glaring disconnects between theory and practice in the library profession today. Finally, it provides an overview of the whole “shape of the elephant” of library services, within which cataloging is only one component.]]></description>
<dc:subject>libraries cataloging reference inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6149ac135902/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cataloging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.artsy.net/categories">
    <title>Categories | Artsy</title>
    <dc:date>2016-05-31T16:36:35+00:00</dc:date>
    <link>https://www.artsy.net/categories</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Art Genome Project is the classification system and technological framework that powers Artsy. It maps the characteristics (we call them “genes”) that connect artists, artworks, architecture, and design objects across history. There are currently over 1,000 characteristics in The Art Genome Project, including art historical movements, subject matter, and formal qualities.]]></description>
<dc:subject>art categorization classification inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5eab8ce60ace/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:art"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:categorization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:classification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.oclc.org/content/dam/research/publications/2016/oclcresearch-organizational-identifiers-and-isni-2016.pdf">
    <title>Addressing the Challenges with Organizational Identifiers and ISNI</title>
    <dc:date>2016-05-04T16:45:53+00:00</dc:date>
    <link>http://www.oclc.org/content/dam/research/publications/2016/oclcresearch-organizational-identifiers-and-isni-2016.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This report focuses on organizational identifiers from the perspective of academic institutions. Their ranks and reputation often determine their success in obtaining funding and attracting or retaining faculty. Identifiers provide the “glue”1 for institutions and funder systems to support comparing and ranking the outputs of the research process; assessing the impact of grants between institutions and their funders; and tracking and collating publications between researchers and their publishers. The report outlines a number of scenarios where the International Standard Name Identifier (ISNI) can be used to disambiguate organizations, including real-world examples.]]></description>
<dc:subject>identifiers identity inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:23785c10195d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://plato.stanford.edu/entries/essential-accidental/#EsseClaiArguForNoni">
    <title>Essential vs. Accidental Properties (Stanford Encyclopedia of Philosophy)</title>
    <dc:date>2016-04-19T01:45:07+00:00</dc:date>
    <link>http://plato.stanford.edu/entries/essential-accidental/#EsseClaiArguForNoni</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The distinction between essential versus accidental properties has been characterized in various ways, but it is currently most commonly understood in modal terms: an essential property of an object is a property that it must have, while an accidental property of an object is one that it happens to have but that it could lack.]]></description>
<dc:subject>properties description inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3423a376e80e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:properties"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://mapzen.com/blog/geocoding-places">
    <title>Meaningful Geocoding - Geocoding Places · Mapzen</title>
    <dc:date>2016-03-02T14:30:26+00:00</dc:date>
    <link>https://mapzen.com/blog/geocoding-places</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In the first post of our series, Meaningful Geocoding, we covered geocoding for addresses. In this post we’ll discuss scenarios that cover users who aren’t looking for something exact. That is, how do we handle users that are just looking for a neighborhood, city, region, country, or a postal code.]]></description>
<dc:subject>inls520 naming geo</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:199558eca7ce/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:geo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/Quartz/bad-data-guide">
    <title>Quartz/bad-data-guide</title>
    <dc:date>2015-12-10T17:39:04+00:00</dc:date>
    <link>https://github.com/Quartz/bad-data-guide</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[An exhaustive reference to problems seen in real-world data along with suggestions on how to resolve them.

As a reporter your world is full of data. And those data are full of problems. This guide presents thorough descriptions and possible solutions to many of the kinds of problems that you will encounter when working with data.

Most of these problems can be solved. Some of them can't be solved and that means you should not use the data. Others can't be solved, but with precautions you can continue using the data. In order to allow for these ambiguities, this guide is organized by who is best equipped to solve the problem: you, your source, an expert, etc. In the description of each problem you may also find suggestions for what to do if that person can't help you.

You can not possibly review every dataset you encounter with for all of these problems. If you try to do that you will never get anything published. However, by familiarizing yourself with the kinds of issues you are likely to encounter you will have a better chance of identifying an issue before it causes you to make a mistake.]]></description>
<dc:subject>data journalism inls520 cleaning</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:82dc98ffe5d5/</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:journalism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cleaning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://cocorahs.blogspot.it/2015/11/a-man-with-his-head-in-clouds.html">
    <title>Community Collaborative Rain, Hail &amp; Snow Network: A Man with His Head In the Clouds</title>
    <dc:date>2015-12-02T21:03:04+00:00</dc:date>
    <link>http://cocorahs.blogspot.it/2015/11/a-man-with-his-head-in-clouds.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Most of us learned about the basic types of clouds some time in school. Clouds fall into general classifications as high, middle, low, or accessory clouds. You may be familiar with some of the specific names, such as cirrus, stratus, and cumulonimbus. What you may not be familiar with is how clouds got their names.]]></description>
<dc:subject>classification naming inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ef43ea891225/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:classification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.snee.com/bobdc.blog/2015/04/running-spark-graphx-algorithm.html">
    <title>Running Spark GraphX algorithms on Library of Congress subject heading SKOS - bobdc.blog</title>
    <dc:date>2015-04-15T02:43:13+00:00</dc:date>
    <link>http://www.snee.com/bobdc.blog/2015/04/running-spark-graphx-algorithm.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Today I'm demonstrating the latter by reading in a well-known RDF dataset and executing GraphX's Connected Components algorithm on it. This algorithm collects nodes into groupings that connect to each other but not to any other nodes. In classic Big Data scenarios, this helps applications perform tasks such as the identification of subnetworks of people within larger networks, giving clues about which products or cat videos to suggest to those people based on what their friends liked.

The US Library of Congress has been working on their Subject Headings metadata since 1898, and it's available in SKOS RDF. Many of the subjects include "related" values; for example, you can see that the subject Cocktails has related values of Cocktail parties and Happy hours, and that Happy hours has related values of Bars (Drinking establishments), Restaurants, and Cocktails. So, while it includes skos:related triples that indirectly link Cocktails to Restaurants, it has none that link these to the subject of Space stations, so the Space stations subject is not part of the same Connected Components subgraph as the Cocktails subject.]]></description>
<dc:subject>graph algorithms inls520 KOS inls201</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a7aa17a10ddf/</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:algorithms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:KOS"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls201"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://visual.ly/daylight-saving-time-explained">
    <title>Daylight saving time explained | Visual.ly</title>
    <dc:date>2014-12-20T22:26:07+00:00</dc:date>
    <link>http://visual.ly/daylight-saving-time-explained</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[I wanted to see the effect of daylight saving time change on sunrise and sunset times. The data was taken from http://www.timeanddate.com and is for Chicago. The figure shows that daylight saving timechange (marked by the DLS lines) keeps the sunrise time pretty much constant throughout the whole year, while making the sunset time change a lot. The spread of sunrise times for the whole year as measured by the standard deviation is 42 minutes, while for sunset times is 1:30 hours. ]]></description>
<dc:subject>time visualization standards inls520 inls201</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4710359d0e32/</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:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls201"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.ideals.illinois.edu/handle/2142/1691">
    <title>IDEALS @ Illinois: The Epistemological Foundations of Knowledge Representations</title>
    <dc:date>2014-09-29T17:57:54+00:00</dc:date>
    <link>https://www.ideals.illinois.edu/handle/2142/1691</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This paper looks at the epistemological foundations of knowledge
 representations embodied in retrieval languages. It considers questions
 such as the validity of knowledge representations and their effectiveness
 for the purposes of retrieval and automation. The knowledge
 representations it considers are derived from three theories of meaning that
 have dominated twentieth-century philosophy.]]></description>
<dc:subject>inls520 definition epistemology KR</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3d391e872e01/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:definition"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:epistemology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:KR"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://descriptionguy.com/images/WEBSITE/Documenting-archives-a-guide-for-dummies.pdf">
    <title>DOCUMENTING ARCHIVES AND OTHER RECORDS - A GUIDE FOR DUMMIES</title>
    <dc:date>2014-04-28T19:32:47+00:00</dc:date>
    <link>http://descriptionguy.com/images/WEBSITE/Documenting-archives-a-guide-for-dummies.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[We can describe only what we understand. There are many ways to understand records. This is one of them.]]></description>
<dc:subject>documentation description archives inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b42bf6562ae3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://onlinelibrary.wiley.com/book/10.1002/9781118627747">
    <title>Classifying Reality - Wiley Online Library</title>
    <dc:date>2014-03-29T11:28:50+00:00</dc:date>
    <link>http://onlinelibrary.wiley.com/book/10.1002/9781118627747</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Distinguished metaphysicians examine issues central to the high-profile debate between philosophers over how to classify the natural world, and discuss issues in applied ontology such as the classification of diseases.

Leading metaphysicians explore fundamental questions related to the classification and structure of the natural world

An essential commentary on issues at the heart of the contemporary debate between philosophy and science

Interweaves discussion of overarching themes with detailed material on applied ontology]]></description>
<dc:subject>classification metaphysics ontology organization inls520 philosophy science</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7d15d5ff1554/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:classification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metaphysics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:organization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:philosophy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:science"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://vimeo.com/36752317">
    <title>Linked Open Data - What is it? on Vimeo</title>
    <dc:date>2014-02-21T19:03:16+00:00</dc:date>
    <link>http://vimeo.com/36752317</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Simple animation to explain what Linked Open Data is and why it's a good thing, both for users and for data providers.
]]></description>
<dc:subject>linkeddata inls520 * inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:567af0e1d61b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:*"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.networkedcorpus.com/">
    <title>Networked Corpus | Bridging the indexical knowledge of the 18th and 21st centuries</title>
    <dc:date>2014-01-08T15:47:45+00:00</dc:date>
    <link>http://www.networkedcorpus.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Networked Corpus provides a new way to navigate large collections of texts. Using a statistical method called topic modeling, it creates links between passages that share common vocabularies, while also showing in detail the way in which the topic modeling program has “read” the texts. We are using the Networked Corpus to analyze earlier genres and concepts of topical knowledge from the development of commonplacing, anthologizing, and indexing in the early modern period through the nineteenth century.]]></description>
<dc:subject>topicmodels visualization inls520 indexing pubberlin</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:955716211b84/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:topicmodels"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:indexing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pubberlin"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://prezi.com/jr61rhjoqotb/high-accuracy-metadata/">
    <title>High Accuracy Metadata by Ashleigh Faith on Prezi</title>
    <dc:date>2013-11-26T13:31:01+00:00</dc:date>
    <link>http://prezi.com/jr61rhjoqotb/high-accuracy-metadata/</link>
    <dc:creator>rybesh</dc:creator><dc:subject>inls520 taxonomy automation machinelearning</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:36c5b9491d00/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:taxonomy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:automation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:machinelearning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://new-savanna.blogspot.com/2013/10/on-describing-painting.html">
    <title>NEW SAVANNA: On Describing a Painting</title>
    <dc:date>2013-10-21T15:47:03+00:00</dc:date>
    <link>http://new-savanna.blogspot.com/2013/10/on-describing-painting.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Paintings, like literary texts or movies, are very complex objects, with many properties. It is through description that some among those properties enter into the intellectual record for further notice and discussion. ]]></description>
<dc:subject>description art inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ce46bd1354ec/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:art"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.jstor.org/stable/2799807">
    <title>Polythetic Classification: Convergence and Consequences</title>
    <dc:date>2013-10-01T19:59:43+00:00</dc:date>
    <link>http://www.jstor.org/stable/2799807</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The conventional definition of a conceptual class is that its members must possess certain properties in common. Vygotsky and Wittgenstein have shown that this definition is unrealistic and logically unnecessary. The resultant recognition of classificatory concepts formed by family resemblances has recently led to a revision of anthropological analyses of kinship and of belief statements. The present article reports the discovery that, by a remarkable convergence of ideas in the past decade, family resemblance predicates had already been adduced in certain natural sciences under the term 'polythetic classification'. The methodological and experimental results of this approach are set out, and a variety of consequences for social anthropology are drawn from them. A main conclusion is that comparative studies carried out in the stock classificatory terms of anthropology are subverted by the realisation that they refer not to common features but to polythetic classes of social facts. It is suggested that effective comparison may nevertheless be practicable by reliance on a purely formal terminology of analytical concepts, and it is envisaged that these may permit the determination of basic predicates in the study of human affairs.]]></description>
<dc:subject>classification inls520 categories</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ab84b9178e6e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:classification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:categories"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://igniteshow.com/videos/polysemous-terms-did-everyone-understand-your-message">
    <title>Polysemous Terms: Did Everyone Understand Your Message? by Joe Hourcle | Ignite Talk Videos</title>
    <dc:date>2013-09-30T20:52:24+00:00</dc:date>
    <link>http://igniteshow.com/videos/polysemous-terms-did-everyone-understand-your-message</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[ Joe discusses the concept of polysemous with an example of a pancake and then applies it to science data (briefly) providing an example of dataset and the domain issues related with that term. ]]></description>
<dc:subject>inls520 meaning language inls201</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7ff873f4169e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:meaning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls201"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://code.google.com/p/word2vec/">
    <title>word2vec - Tool for computing continuous distributed representations of words. - Google Project Hosting</title>
    <dc:date>2013-08-16T04:10:02+00:00</dc:date>
    <link>https://code.google.com/p/word2vec/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The word2vec tool takes a text corpus as input and produces the word vectors as output. It first constructs a vocabulary from the training text data and then learns vector representation of words. The resulting word vector file can be used as features in many natural language processing and machine learning applications.

A simple way to investigate the learned representations is to find the closest words for a user-specified word. The distance tool serves that purpose. For example, if you enter 'france', distance will display the most similar words and their distances to 'france'.]]></description>
<dc:subject>nlp similarity textanalysis semantics inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:766699a08a09/</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:similarity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:textanalysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semantics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://shapeofdata.wordpress.com/2013/08/06/intrinsic-vs-extrinsic-structure/">
    <title>Intrinsic vs. Extrinsic Structure | The Shape of Data</title>
    <dc:date>2013-08-15T01:36:28+00:00</dc:date>
    <link>http://shapeofdata.wordpress.com/2013/08/06/intrinsic-vs-extrinsic-structure/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The distinction between intrinsic and extrinsic structure is closely related to the difference between local and global structure: The local structure of something is the structure that you see when you zoom in very close, while the global structure is what you see when you look at it from far away. For example, the local structure of your shirt is a tangle of crisscrossing threads. Its global structure is a two-dimensional shape with four holes (one for your head, two for your arms and a big hole at the bottom for your waist.) The extrinsic structure of an object is essentially the same as its global structure. However, an object’s intrinsic structure isn’t the same as its local structure. Instead, it’s more or less what you get by combining all the local structures and fitting them together. ]]></description>
<dc:subject>inls520 structure relationships</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c5e84660bde1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:structure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:relationships"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://media.aau.dk/null_space_pursuits/2013/07/classification-accuracy-is-not-enough.html">
    <title>Classification accuracy is not enough - Pursuits in the Null Space</title>
    <dc:date>2013-07-26T11:19:20+00:00</dc:date>
    <link>http://media.aau.dk/null_space_pursuits/2013/07/classification-accuracy-is-not-enough.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[I perform three different experiments to determine how well two state-of-the-art systems for music genre recognition are recognizing genre. In the first experiment, I find the two systems are consistently making extremely bad misclassifications. In the second experiment, I find the two systems can be fooled by such simple transformations that they cannot possibly be listening to the music. In the third experiment, I find their internal models of the genres do not match how humans think the genres sound. Hence, it appears that the systems are not recognizing genre in the least. However, this seems to contradict the fact that they achieve extremely good classification accuracies, and have been touted as superior solutions in the literature. Turns out, Classification accuracy is not enough!]]></description>
<dc:subject>classification inls520 music IR genre measurement experimental methods</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3c2bda35c4a9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:classification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:music"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:IR"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:genre"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:measurement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:experimental"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:methods"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://onlinelibrary.wiley.com/doi/10.1002/bult.2013.1720390511/abstract">
    <title>Using a taxonomy for your database or website: A look behind the scenes - Hlava - 2013 - Bulletin of the American Society for Information Science and Technology - Wiley Online Library</title>
    <dc:date>2013-06-24T16:57:06+00:00</dc:date>
    <link>http://onlinelibrary.wiley.com/doi/10.1002/bult.2013.1720390511/abstract</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Peering behind the screen of a database or website reveals the methods and benefits of incorporating a taxonomy. A digital taxonomy file contains terms, term records with details of relationships and a hierarchical structure. The terms are used to categorize content and apply as metanames describing website content items. Digging deeper, the taxonomy terms are stored and associated with a relational database management system, object-oriented database or XML-based database system. Taxonomy terms can be presented to the end user in a browsable format along with term record details for additional guidance. Captured in the inverted index of search software, the terms promote findability and search success. Documents with taxonomy terms attached can be accurately retrieved regardless of where they are held, and terms can be repurposed as site labels and points of association between internal content items.]]></description>
<dc:subject>inls520 taxonomy</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:178c4c2c4a27/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:taxonomy"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://onlinelibrary.wiley.com/doi/10.1002/bult.2013.1720390510/abstract">
    <title>Transforming our conversation of information architecture with structure - Davis - 2013 - Bulletin of the American Society for Information Science and Technology - Wiley Online Library</title>
    <dc:date>2013-06-24T16:56:45+00:00</dc:date>
    <link>http://onlinelibrary.wiley.com/doi/10.1002/bult.2013.1720390510/abstract</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Since the origin of the concept, information architecture has been viewed as an art and a science, rooted in library science but borrowing from multiple disciplines. Though there are recognized elements, some say it lacks a foundation of consistent internal theory. The central concept of information architecture is structure. Though invisible and often taken for granted, effective structure is the quality that makes websites functional. It rests on navigation, information organization and information relationships and can extend to user experience and spatial representation. Information architecture reflects elements from a number of disciplines but, by aggregating them, is greater than the parts. Advancing information architecture from art to science depends on shared strategies and solutions for website structure.]]></description>
<dc:subject>inls520 structure information architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9cc14b38e28b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:structure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://fordham.bepress.com/dissertations/AAI3466699/">
    <title>&quot;'Carving nature at its joint': The Platonic method of division in Plat&quot; by Gary Thomas Gabor</title>
    <dc:date>2013-06-03T20:55:21+00:00</dc:date>
    <link>http://fordham.bepress.com/dissertations/AAI3466699/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The method of division was a philosophically influential logical procedure first introduced by Plato in the Phaedrus which served as something close to a full-fledged theory of definition in his later dialogues. Aristotle later picked up, critiqued, and refined the method, first by codifying its terminology and by the introduction of a number of rules meant to ensure that the classes identified by the method were natural ones.^ The Neoplatonists, in their commentaries and other works, sought to incorporate the contributions provided by Plato and Aristotle. By and large, they accepted the mechanisms and terminology introduced by Aristotle, especially as they applied to the entities of the natural sensible world, while also accepting Plato's precept that division, as a dialectical method, applies primary to transcendent Forms.^ This attempt to reconcile and integrate Plato's and Aristotle's accounts of division into one single method gave rise to several contributions by the Neoplatonists not found in the works of either Plato or Aristotle. First, they sought to exactly identify the scope and nature of the method, including which entities it did and did not apply to. This led to heavy debate among them. It also led them to a consideration of several topics treated by neither Plato nor Aristotle, including the possibility of single-member classes, and the division of a higher genus into a single, subordinate sub-species. Finally, they articulated a few refinements of Plato's and Aristotle's own mechanisms for ensuring the naturalness of proposed kinds, and attempted to incorporate their various rules into a single, unified method.]]></description>
<dc:subject>definition philosophy methods taxonomy inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:251b488ed141/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:definition"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:philosophy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:methods"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:taxonomy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.philosophy.ox.ac.uk/__data/assets/pdf_file/0011/16589/Definition_and_Division.pdf">
    <title>Deﬁnition and Division in Plato’s Sophist</title>
    <dc:date>2013-06-03T20:54:03+00:00</dc:date>
    <link>http://www.philosophy.ox.ac.uk/__data/assets/pdf_file/0011/16589/Definition_and_Division.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[I investigate below some of the many scholarly responses to this bewildering display of the much-vaunted method of division. I divide scholars into a ‘no-faction’, those who hold that we should not try to discern, in any or all of the dialogue’s deﬁnitions, a positive outcome to the investigation into what sophistry is (Ryle, Cherniss), and a ‘yes-faction’: those who think an outcome is to be found (Moravcsik, Cornford, and others). ]]></description>
<dc:subject>definition methods philosophy taxonomy inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d778d16c5ab2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:definition"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:methods"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:philosophy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:taxonomy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://faculty.washington.edu/smcohen/PlatoDivision.pdf">
    <title>Plato's Method of Division</title>
    <dc:date>2013-06-03T20:51:04+00:00</dc:date>
    <link>http://faculty.washington.edu/smcohen/PlatoDivision.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Our main difficulty with Plato's method of division is that we don,t know what is being divided or what it is being divided into. And until we know these things, we don't know very much about the method of division]]></description>
<dc:subject>plato philosophy methods taxonomy inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:be51b8bcf9e2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:plato"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:philosophy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:methods"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:taxonomy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.orm.net/pdf/EncDBS.pdf">
    <title>Object-Role Modeling</title>
    <dc:date>2013-05-24T14:47:03+00:00</dc:date>
    <link>http://www.orm.net/pdf/EncDBS.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Unlike Entity-Relationship (ER) modeling and Unified Modeling Language (UML) class diagrams, ORM treats all facts as relationships (unary, binary, ternary etc.). How facts are grouped into structures (e.g. attribute-based entity types, classes, relation schemes, XML schemas) is considered a design level, implementation issue that is irrelevant to the capturing of essential business semantics.]]></description>
<dc:subject>data modeling relationships inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:fe5cb08802d7/</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:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:relationships"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.dataprotocols.org/en/latest/data-packages.html">
    <title>Data Packages — Open Data Protocols - Simple Open Standards for Open Data</title>
    <dc:date>2013-05-23T21:00:31+00:00</dc:date>
    <link>http://www.dataprotocols.org/en/latest/data-packages.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A Data Package (or DataPackage) is a coherent collection of data and possibly other assets into a single form. It provides the basis for convenient delivery, installation and management of datasets.]]></description>
<dc:subject>opendata data standards description metadata inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:70819106a314/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opendata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.bostonglobe.com/news/politics/2013/04/22/lindsey-graham-fbi-didn-know-tsarnaev-was-russia-because-his-name-was-misspelled/hrRI2TUaKXsQMRLooKkymM/story.html">
    <title>Lindsey Graham: FBI didn’t know Tsarnaev was in Russia because his name was misspelled - Politics - The Boston Globe</title>
    <dc:date>2013-04-24T15:40:40+00:00</dc:date>
    <link>http://www.bostonglobe.com/news/politics/2013/04/22/lindsey-graham-fbi-didn-know-tsarnaev-was-russia-because-his-name-was-misspelled/hrRI2TUaKXsQMRLooKkymM/story.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Senator Lindsey Graham said Monday the FBI told him it was initially unaware Tamerlan Tsarnaev had traveled to Russia early last year because of a clerical error: His name was misspelled.

“He went over to Russia, but apparently, when he got on the Aeroflot plane, they misspelled his name,” Graham, a South Carolina Republican, said on Fox television. “So it never went into the system that he actually went to Russia.”

Federal officials did not respond to requests to independently confirm Graham’s account, and his office did not respond to several follow-up requests for fuller context.]]></description>
<dc:subject>naming authority inls520 inls201</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c222c818a7b1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authority"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls201"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://aims.fao.org/lode/bd">
    <title>LODE-BD Recommendations 2.0 | Agricultural Information Management Standards (AIMS)</title>
    <dc:date>2013-04-16T01:22:53+00:00</dc:date>
    <link>http://aims.fao.org/lode/bd</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[LODE-BD aims to support the selection of appropriate encoding strategies for producing meaningful Linked Open Data (LOD)-enabled bibliographical data (directly or indirectly). The LODE-BD recommendations are applicable for structured data describing bibliographic resources such as articles, monographs, theses, conference papers, presentation materials, research reports, learning objects, etc. – in print or electronic format.

The core component of LODE-BD contains a set of recommended decision trees for common properties used in describing a bibliographic resource instance. Each decision tree is delivered with various acting points and the matching encoding suggestions. The full range of options presented by LODE-BD will enable data providers to make their choices according to their development stages, internal data structures, and the reality of their practices.]]></description>
<dc:subject>linkeddata cataloging inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:edd4457a0347/</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:cataloging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.aiai.ed.ac.uk/~jessicac/psfiles/SIG-SEMIS/issue3-tom-gruber.pdf">
    <title>Tom Gruber in AIS SIGSEMIS Bulletin</title>
    <dc:date>2013-02-06T15:27:20+00:00</dc:date>
    <link>http://www.aiai.ed.ac.uk/~jessicac/psfiles/SIG-SEMIS/issue3-tom-gruber.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA["every ontology is a treaty – a social agreement – among people with some common motive in sharing"]]></description>
<dc:subject>ontology definition inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:dad591d98156/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:definition"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://counternotions.com/2013/01/26/idownloader/">
    <title>How many iDownloaders does it take to screw an App Store? « counternotions</title>
    <dc:date>2013-01-27T14:34:46+00:00</dc:date>
    <link>http://counternotions.com/2013/01/26/idownloader/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Apple’s inability or unwillingness to fundamentally improve categorization, discovery, navigation, display, promotion, fraud, pricing and reviews at the App Store has been most glaring.]]></description>
<dc:subject>cataloging inls520 examples description inls201</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:61e6742116cc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cataloging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:examples"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls201"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://searchengineland.com/facebook-search-not-google-search-145124">
    <title>How The New Facebook Search Is Different &amp; Unique From Google Search</title>
    <dc:date>2013-01-16T17:04:21+00:00</dc:date>
    <link>http://searchengineland.com/facebook-search-not-google-search-145124</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[With a typical Google search, the objects we search for are web pages, with the connections (or graph) that help determine the pages that rise to the top primarily being links from across the web. Links, simple form, are like votes, helping Google decide which are the most popular pages to show for a particular topic.

With Facebook Graph Search, the objects we search for aren’t web pages but instead virtual representations of real world objects: people, places and things. The connections are primarily Facebook Likes. Did such-and-such a person like a particular photo? A particular doctor? A particular restaurant? Those likes are the ties that bind the information in Facebook together.]]></description>
<dc:subject>graph search inls520 inls201</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9c683399f73f/</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:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls201"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.thetoolbox.cc/">
    <title>The Toolbox: a directory of useful single-page sites and apps</title>
    <dc:date>2012-11-30T16:54:04+00:00</dc:date>
    <link>http://www.thetoolbox.cc/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A collection of the best time-saving apps, tools, and widgets from around the web.]]></description>
<dc:subject>web development tools inls520 inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f87e5b7c70f9/</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:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kunststube.net/encoding/">
    <title>What Every Programmer Absolutely, Positively Needs to Know About Encodings and Character Sets to Work With Text</title>
    <dc:date>2012-11-18T19:39:56+00:00</dc:date>
    <link>http://kunststube.net/encoding/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[If you are dealing with text in a computer, you need to know about encodings. Period. Yes, even if you are just sending emails. Even if you are just receiving emails. You don't need to understand every last detail, but you must at least know what this whole "encoding" thing is about. And the good news first: while the topic can get messy and confusing, the basic idea is really, really simple.

This article is about encodings and character sets. An article by Joel Spolsky entitled The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!) is a nice introduction to the topic and I greatly enjoy reading it every once in a while. I hesitate to refer people to it who have trouble understanding encoding problems though since, while entertaining, it is pretty light on actual technical details. I hope this article can shed some more light on what exactly an encoding is and just why all your text screws up when you least need it. This article is aimed at developers (with a focus on PHP), but any computer user should be able to benefit from it.]]></description>
<dc:subject>unicode text encoding inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b5cdac3d5eb1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:unicode"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:text"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:encoding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sils.unc.edu/sites/default/files/general/programs/orgranizationgrid2009.pdf">
    <title>Specialization in Organization of Information &amp; Materials (MSIS)</title>
    <dc:date>2012-11-12T21:10:07+00:00</dc:date>
    <link>http://sils.unc.edu/sites/default/files/general/programs/orgranizationgrid2009.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Advising grid for Specialization in Organization of Information & Materials (MSIS), circa 1/5/2009.]]></description>
<dc:subject>sils organization curriculum inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2f64263a14aa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sils"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:organization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:curriculum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sils.unc.edu/sites/default/files/general/programs/organizationgrid.pdf">
    <title>Specialization in Organization of Information &amp; Materials (MSLS)</title>
    <dc:date>2012-11-12T21:09:15+00:00</dc:date>
    <link>http://sils.unc.edu/sites/default/files/general/programs/organizationgrid.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Advising grid for Specialization in Organization of Information & Materials (MSLS), circa 1/5/2009.]]></description>
<dc:subject>sils organization curriculum inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cc1131d2e5f5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sils"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:organization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:curriculum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://jsonlint.com/">
    <title>JSONLint - The JSON Validator.</title>
    <dc:date>2012-10-11T14:14:05+00:00</dc:date>
    <link>http://jsonlint.com/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[JSON linter.]]></description>
<dc:subject>json validation inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:670c94f8b56c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:json"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:validation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://eikes.github.com/facetedsearch/">
    <title>Faceted Search JavaScript Library</title>
    <dc:date>2012-10-11T14:01:13+00:00</dc:date>
    <link>http://eikes.github.com/facetedsearch/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This JS lib lets you filter, sort and display large datasets in the browser.]]></description>
<dc:subject>javascript faceted classification inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:17aafa6be52b/</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:faceted"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:classification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://onlinelibrary.wiley.com/doi/10.1002/asi.22731/abstract">
    <title>The weakening relationship between the impact factor and papers' citations in the digital age - Lozano - 2012 - Journal of the American Society for Information Science and Technology - Wiley Online Library</title>
    <dc:date>2012-10-10T14:19:24+00:00</dc:date>
    <link>http://onlinelibrary.wiley.com/doi/10.1002/asi.22731/abstract</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Historically, papers have been physically bound to the journal in which they were published; but in the digital age papers are available individually, no longer tied to their respective journals. Hence, papers now can be read and cited based on their own merits, independently of the journal's physical availability, reputation, or impact factor (IF). We compare the strength of the relationship between journals' IFs and the actual citations received by their respective papers from 1902 to 2009. Throughout most of the 20th century, papers' citation rates were increasingly linked to their respective journals' IFs. However, since 1990, the advent of the digital age, the relation between IFs and paper citations has been weakening. This began first in physics, a field that was quick to make the transition into the electronic domain. Furthermore, since 1990 the overall proportion of highly cited papers coming from highly cited journals has been decreasing and, of these highly cited papers, the proportion not coming from highly cited journals has been increasing. Should this pattern continue, it might bring an end to the use of the IF as a way to evaluate the quality of journals, papers, and researchers.]]></description>
<dc:subject>inls520 citation networks bibliometrics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:70feb4f1c961/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:citation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:networks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bibliometrics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://computationalculture.net/article/what_is_in_pagerank">
    <title>What is in PageRank? A Historical and Conceptual Investigation of a Recursive Status Index. : Computational Culture</title>
    <dc:date>2012-10-08T16:00:18+00:00</dc:date>
    <link>http://computationalculture.net/article/what_is_in_pagerank</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This paper proposes an analysis, based in a software studies mindset, of Google’s PageRank algorithm. It develops two lines of investigation: first, it situates this ‘evaluative metric’ in a larger genealogy of ideas, concepts, theories, and methods that developed, from the 1930s onwards, around the fields of sociometry, citation analysis, social exchange theory, and hypertext navigation. This backdrop is presented as a conceptual a priori, in the Foucauldian sense, from where PageRank becomes ‘sayable’. Second, by comparing the algorithm to a close cousin, Jon Kleinberg’s HITS, and by examining a particular parameter in the PageRank model, the paper shows that the concrete model does not follow teleologically from this historical a priori. Behind the particular empirical case lurks the larger epistemological and methodological question of how to study software. The paper advocates a multilayered approach that combines different types of methodological and conceptual resources.]]></description>
<dc:subject>digitalhumanities inls520 concepts history evaluation metrics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:da7da6d9909a/</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:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:concepts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:evaluation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metrics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/2001/sw/Europe/events/foaf-galway/papers/pp/validating_rdf/">
    <title>Validating RDF with TreeHugger and Schematron - Position Paper for FOAF-Galway, 2004</title>
    <dc:date>2012-10-08T14:27:24+00:00</dc:date>
    <link>http://www.w3.org/2001/sw/Europe/events/foaf-galway/papers/pp/validating_rdf/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Document-level validation is very useful for RDF but has often been ignored. We set out a usecase and a possible approach using Schematron, an XPath-based validation mechanism, combined with TreeHugger, a way of using XML tools such as XSLT over the RDF model.]]></description>
<dc:subject>schematron owl rdf xml validation inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e5233e990754/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:schematron"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:owl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:validation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://aclweb.org/anthology-new/E/E12/E12-1051.pdf">
    <title>Instance-Driven Attachment of Semantic Annotations over Conceptual Hierarchies</title>
    <dc:date>2012-10-06T23:45:29+00:00</dc:date>
    <link>http://aclweb.org/anthology-new/E/E12/E12-1051.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Whether automatically extracted or human generated, open-domain factual knowledge is often available in the form of semantic annotations (e.g., composed-by ) that take one or more specific instances (e.g., rhapsody in blue , george gershwin ) as their arguments. This paper introduces a method for converting flat sets of instance-level annotations into hierarchically organized, concept-level annotations, which capture not only the broad semantics of the desired arguments (e.g., `People' rather than `Locations'), but also the correct level of generality (e.g., `Composers' rather than `People', or `Jazz Composers'). The method refrains from encoding features specific to a particular domain or annotation, to ensure immediate applicability to new, previously unseen annotations. Over a gold standard of semantic annotations and concepts that best capture their arguments, the method substantially outperforms three baselines, on average, computing concepts that are less than one step in the hierarchy away from the corresponding gold standard concepts.]]></description>
<dc:subject>concepts taxonomy semantics machinelearning inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9d31bb3a5d2c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:concepts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:taxonomy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semantics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:machinelearning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.ischool.berkeley.edu/newsandevents/events/deanslectures/20121003glushko">
    <title>The Discipline of Organizing: The Intellectual Intersection of the Information Schools | School of Information</title>
    <dc:date>2012-10-06T02:01:09+00:00</dc:date>
    <link>http://www.ischool.berkeley.edu/newsandevents/events/deanslectures/20121003glushko</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Information School community suffers from a splintered identity, because the schools differ greatly in the problem domains emphasized, the degrees offered, the courses required, and the types of jobs found by graduates. But despite the obvious differences among them, we believe there is an intellectual intersection among the I Schools in the study of “Organizing Systems” — intentionally arranged collections of resources and the interactions they support. All organizing systems share common activities: identifying resources to be organized; organizing resources by describing and classifying them; designing resource-based interactions; and maintaining resources and organization over time. This framework exposes design concepts and patterns that apply to libraries, museums, business information systems, personal information management, and social computing contexts.

In this talk I will present the key ideas of the Organizing System perspective, discuss how it is being collaboratively taught this semester at several I Schools, and describe how its transdisciplinary character has inspired new concepts for customized e-books as its delivery platform.]]></description>
<dc:subject>inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:09fbc7a887de/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.orange11.nl/2012/09/25/whats-so-cool-about-elasticsearch/">
    <title>What’s so cool about elasticsearch? « Orange11 Blog / Orange11: Enterprise Java, Open Source, software solutions, Amsterdam</title>
    <dc:date>2012-10-05T23:52:36+00:00</dc:date>
    <link>http://blog.orange11.nl/2012/09/25/whats-so-cool-about-elasticsearch/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[You usually end up needing to search on different fields with different weights, by applying some filters or conditions to boost document rating based on the value of some pre-defined fields, facebook likes, recent documents, facets,highlighting and so on. All of this can be done through a single query and there is a need to express this complexity: the elasticsearch query DSL is the answer.]]></description>
<dc:subject>elasticsearch search IR inls520 faceted facets analysis classification</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f02522710f57/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:elasticsearch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:IR"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:faceted"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:facets"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:analysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:classification"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.cdt.org/blogs/0110apple-ios-6-and-privacy-0">
    <title>Apple iOS 6 and Privacy | Center for Democracy &amp; Technology</title>
    <dc:date>2012-10-01T19:07:36+00:00</dc:date>
    <link>https://www.cdt.org/blogs/0110apple-ios-6-and-privacy-0</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Apple has incorporated three new identifiers to take the place of the much-maligned and unchangeable UDID: iOS 6 now makes available a vendor-specific identifier, identifierForVendor, that can be used by app developers to recognize a device across their apps; a second identifier for advertising purposes, advertisingIdentifier, that can be used by third-party ad networks to identify a device for advertising purposes; and a third application identifier, UUID, that is a more accessible way for applications to create identifiers specific to that application. These three IDs may sound similar but the details are quite different: The vendor identifier is cleared when the user uninstalls the last app on their phone by a given vendor; the advertising identifier persists until the device is completely reset; the application identifier persists only if the application saves it, and then only until that application is uninstalled. Each of these new identifiers is preferable to the UDID, which cannot be modified.]]></description>
<dc:subject>identifiers identity inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ab4fbe402f4e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.qwantz.com/index.php?comic=2292">
    <title>Dinosaur Comics - September 27th, 2012 - awesome fun times!</title>
    <dc:date>2012-09-27T20:59:54+00:00</dc:date>
    <link>http://www.qwantz.com/index.php?comic=2292</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA["You may not know what I cared about, who I loved, or the things I believed to be true, but by God, you'll know my ad click behavior patterns and what my IP address was searching for."]]></description>
<dc:subject>inls520 modeling bigdata information</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0bd8fa0306ec/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bigdata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:information"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.oclc.org/research/activities/frbralgorithm.html">
    <title>FRBR Work-Set Algorithm</title>
    <dc:date>2012-09-24T18:07:59+00:00</dc:date>
    <link>http://www.oclc.org/research/activities/frbralgorithm.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[OCLC Research is pleased to provide you with an algorithm for converting MARC21 bibliographic databases to the "FRBR" model.

FRBR (Functional Requirements for Bibliographic Records) is a 1998 recommendation of the International Federation of Library Associations and Institutions (IFLA) to restructure catalog databases to reflect the conceptual structure of information resources. This project is one of several FRBR-related OCLC Research projects, which examine issues associated with converting a set of bibliographic records to conform to FRBR requirements (a process referred to as "FRBRization").]]></description>
<dc:subject>FRBR inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ef8445131f32/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:FRBR"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.librarything.com/review/86646140">
    <title>Paper Machines: About Cards &amp; Catalogs, 1548-1929 (History and Foundations of Information Science) by Markus Krajewski | LibraryThing</title>
    <dc:date>2012-09-22T04:32:57+00:00</dc:date>
    <link>http://www.librarything.com/review/86646140</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Timothy Burke's review of Krajewski, Markus. Paper Machines?: About Cards & Catalogs, 1548-1929. MIT Press,, 2011. Print. History and Foundations of Information Science.

Intellectual, material and technological history of the "file card" and its incorporation into the structure and conception of digital file storage and access. Central object of focus is the card catalog. 

Starts with the question: why was there a moment where the designers of card catalogs promised they would be in some sense "universal information devices" capable of almost anything?]]></description>
<dc:subject>information management history inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ff2eb3d95a48/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://docs.datomic.com/tutorial.html">
    <title>Datomic Development Resources</title>
    <dc:date>2012-09-22T04:20:51+00:00</dc:date>
    <link>http://docs.datomic.com/tutorial.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Datomic is designed to be directly programmable using data. Transactions, queries and query results are all represented as simple list and map data structures. We'll be using these data structures as examples throughout this tutorial.]]></description>
<dc:subject>inls520 datomic tutorial data structure</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:30f8d346619e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:datomic"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:structure"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://docs.datomic.com/schema.html">
    <title>Datomic Development Resources</title>
    <dc:date>2012-09-22T04:19:00+00:00</dc:date>
    <link>http://docs.datomic.com/schema.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Duck typing for data?

Each Datomic database has a schema that describes the set of attributes that can be associated with entities. A schema only defines the characteristics of the attributes themselves. It does not define which attributes can be associated with which entities. Decisions about which attributes apply to which entities are made by an application.

This gives applications a great degree of freedom to evolve over time. For example, an application that wants to model a person as an entity does not have to decide up front whether the person is an employee or a customer. It can associate a combination of attributes describing customers and attributes describing employees with the same entity. An application can determine whether an entity represents a particular abstraction, customer or employee, simply be looking for the presence of the appropriate attributes.]]></description>
<dc:subject>database description inls520 datomic</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e95a8869d2c2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:datomic"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://codeartisan.blogspot.com/2012/08/hypermedia-programming-lists.html">
    <title>codeartisan: Hypermedia Programming: Lists</title>
    <dc:date>2012-09-22T04:05:13+00:00</dc:date>
    <link>http://codeartisan.blogspot.com/2012/08/hypermedia-programming-lists.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The humble list is one of our simplest and yet most powerful data structures--so much so that we will even routinely write them out by hand. We put them on sticky notes to help us remember things we need to do or things we need to buy from the grocery store. We even use them for entertainment. In this post I'll explain how to represent and manipulate lists using hypermedia techniques.

The most straightforward list representation actually doesn't look that different than a handwritten to-do list; the text/uri-list media type just consists of one URI per line. This makes the format incredibly concise, since there is very little syntactic structure (just interleaved line breaks!), while making it completely general through the use of globally unambiguous identifiers.

Now let's talk about manipulating this list with HTTP.]]></description>
<dc:subject>web hypermedia data structure inls520 REST api inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:00d4acc10234/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypermedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:structure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:REST"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://andrewgelman.com/2012/09/building-a-regression-model-with-only-27-data-points/">
    <title>Building a regression model . . . with only 27 data points « Statistical Modeling, Causal Inference, and Social Science</title>
    <dc:date>2012-09-22T03:23:09+00:00</dc:date>
    <link>http://andrewgelman.com/2012/09/building-a-regression-model-with-only-27-data-points/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Get more data. Not by getting information on more years (I assume you can’t do that) but by breaking up the data you do have, for example by geography, or class of business, or size of business, or some other factor. Or could each business be a data point? What I’m getting at is, it seems that you must have a lot more than 27 pieces of information you could analyze.]]></description>
<dc:subject>statistics modeling regression metadata description inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:74e37ba89fb3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:statistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:regression"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.cs.cmu.edu/~nasmith/papers/smith.whitepaper12.pdf">
    <title>Noah Smith/Adversarial Evaluation for Models of Natural Language</title>
    <dc:date>2012-09-22T02:08:39+00:00</dc:date>
    <link>http://www.cs.cmu.edu/~nasmith/papers/smith.whitepaper12.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In this paper, we discuss some of the weaknesses of our current methodology. We present a new abstract framework for evaluating natural language processing (NLP) models in general and unsupervised NLP models in particular. The central idea is to make explicit certain adversarial roles among researchers, so that the different roles in an evaluation are more clearly defined and performers of all roles are offered ways to make measurable contributions to the larger goal.]]></description>
<dc:subject>nlp models evaluation cogsci inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:075700234519/</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:models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:evaluation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cogsci"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.springerlink.com/content/p26q17h071439602/fulltext.pdf?MUD=MP">
    <title>The removal of pluto from the class of planets and homosexuality from the class of psychiatric disorders: a comparison</title>
    <dc:date>2012-09-17T01:58:01+00:00</dc:date>
    <link>http://www.springerlink.com/content/p26q17h071439602/fulltext.pdf?MUD=MP</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[We compare astronomers’ removal of Pluto from the listing of planets and psychiatrists’ removal of homosexuality from the listing of mental disorders. Although the political maneuverings that emerged in both controversies are less than scientifically ideal, we argue that competition for “scientific authority” among competing groups is a normal part of scientific progress. In both cases, a complicated relationship between abstract constructs and evidence made the classification problem thorny.]]></description>
<dc:subject>classification inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:33ede82caba7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:classification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.semantic-web.at/2012/09/12/state-of-the-art-text-mining-poolparty-extractor-2-1-1-released/">
    <title>State-of-the-art Text Mining: PoolParty Extractor 2.1.1 released |The Semantic Puzzle</title>
    <dc:date>2012-09-15T20:18:57+00:00</dc:date>
    <link>http://blog.semantic-web.at/2012/09/12/state-of-the-art-text-mining-poolparty-extractor-2-1-1-released/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The idea behind PPX is to underpin automatic text mining algorithms with domain-specific knowledge from thesauri and linked data sources. This is the precondition to extract meaning from unstructured information more precisely and with higher performance. PoolParty Extractor supports the following application scenarios:

automatic document categorisation
named entity extraction based on concepts from thesauri or other knowledge models
text analysis to improve semantic indexing
automatic transformation of unstructured text to an RDF based linked data source
linking and enrichment of text with structured data from databases or XML-documents
extended indexing by using inflected forms of words and by splitting of compound words
generation and continuous improvement of thesauri by text corpus analysis
PoolParty Extractor can be integrated smoothly with third-party systems like CMS, DMS, communication platforms, wikis etc.]]></description>
<dc:subject>entitydetection extraction textmining linkeddata thesaurus inls520 semweb</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9cf2a648382d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:entitydetection"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:extraction"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:textmining"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:thesaurus"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://arxiv.org/help/author_identifiers">
    <title>arXiv.org help - Author Identifiers</title>
    <dc:date>2012-09-13T21:57:38+00:00</dc:date>
    <link>http://arxiv.org/help/author_identifiers</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[It is a long-term goal of arXiv to accurately identify and disambiguate all authors of all articles in arXiv. Such identification would provide accurate results for queries such as "show me all the other papers by the particular John Smith that wrote this paper", something that can be done only approximately with text-based searches. It would also permit construction of an author-article graph which is useful for relevance assessment and bibliometric analysis.

Since 2005 arXiv has used authority records that associate user accounts with articles authored by that user. These records support the endorsement system. The use of public author identifiers as a way to build services upon this data is new in 2009. Initially, users must opt-in to have a public author identifier and to expose the record of their articles on arXiv for use in other services. At some later date we hope to be able to improve our authority records to the point where we can create public author identifiers for all authors of arXiv articles without needing to enlist the help of each author to check their record before opting in.]]></description>
<dc:subject>authorship identifiers inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:47641c9dc1ca/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authorship"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://viewshare.org/">
    <title>Welcome to Viewshare</title>
    <dc:date>2012-09-10T19:49:16+00:00</dc:date>
    <link>http://viewshare.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Viewshare is a free platform for generating and customizing views (interactive maps, timelines, facets, tag clouds) that allow users to experience your digital collections.]]></description>
<dc:subject>archive culture history tools loc digitalhumanities infoviz inls520 facets</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2feb2612afc4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archive"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:loc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:infoviz"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:facets"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://people.cs.umass.edu/~abakalov/papers/jcdl12-lpam.pdf">
    <title>Topic Models for Taxonomies</title>
    <dc:date>2012-09-08T12:50:39+00:00</dc:date>
    <link>http://people.cs.umass.edu/~abakalov/papers/jcdl12-lpam.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Concept taxonomies such as MeSH, the ACM Computing Classification System, and the NY Times Subject Headings are frequently used to help organize data. They typically consist of a set of concept names organized in a hierarchy. However, these names and structure are often not sufficient to fully capture the intended meaning of a taxonomy node, and particularly non-experts may have difficulty navigating and placing data into the taxonomy. This paper introduces two semi-supervised topic models that automatically augment a given taxonomy with many additional keywords by leveraging a corpus of multi-labeled documents. Our experiments show that users find the topics beneficial for taxonomy interpretation, substantially increasing their cataloging accuracy. Furthermore, the models provide a better information rate compared to Labeled LDA [7].]]></description>
<dc:subject>topicmodels taxonomy organization inls520 classification</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:27ca73f91f00/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:topicmodels"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:taxonomy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:organization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:classification"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ceur-ws.org/Vol-874/paper7.pdf">
    <title>Legal Rules, Text and Ontologies Over Time</title>
    <dc:date>2012-09-03T22:13:22+00:00</dc:date>
    <link>http://ceur-ws.org/Vol-874/paper7.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The current paper presents the “Fill the gap” project that aims to design a set of XML standards for modelling legal documents in the Semantic Web over time. The goal of the project is to design an information system using XML standards able to store in an XML-native database legal resources and legal rules in an integrated way for supporting legal knowledge engineers and end-users (e.g., public administrative officers, judges, citizens).]]></description>
<dc:subject>law ontology documentation time temporality modeling inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:80b5aa7ba3ea/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:law"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:temporality"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.theparisreview.org/blog/2012/08/30/bullet-points/">
    <title>Paris Review – Bullet Points, Joseph Bernstein</title>
    <dc:date>2012-08-30T16:52:18+00:00</dc:date>
    <link>http://www.theparisreview.org/blog/2012/08/30/bullet-points/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[You will likely have noticed by now the writerly fashion of building an essay by numbered sections. These sections can vary from just a single sentence to many pages. Sometimes a section will bear one or more indentations or line breaks and will stretch into a mini-essay. Sometimes there will be as few as three sections and sometimes there will be more than a hundred.

Writers, such as God, have been numbering sections for a very long time indeed, and I do not wish to suggest that this technique is new, rather that it is increasingly used. My proof is a general sense that this is happening, nursed into conviction by a robust confirmation bias.]]></description>
<dc:subject>writing structure organization inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7c6eb172c0d8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:writing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:structure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:organization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.digitalhumanities.org/dhq/vol/6/2/000124/000124.html">
    <title>DHQ: Digital Humanities Quarterly: From the Personal to the Proprietary: Conceptual Writing's Critique of Metadata</title>
    <dc:date>2012-08-16T16:24:31+00:00</dc:date>
    <link>http://www.digitalhumanities.org/dhq/vol/6/2/000124/000124.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The past decade has seen a remarkable proliferation of new works of constrained and appropriated writing that prominently incorporate, and in turn investigate, metadata schemes. I argue that these works ought to be of considerable interest not only to critics of contemporary avant-garde writing — but also to media theorists, librarians and textual scholars. By emphasizing classification protocols, conceptual writing makes an implicit case for the interrelationship of these fields. Each of the four main books under discussion here — Tan Lin’s Seven Controlled Vocabularies, Craig Dworkin’s Perverse Library, M. Nourbese Philip’s Zong! and Simon Morris’ Getting Inside Jack Kerouac’s Head — draws upon pre-existing textual archives. In doing so, these books suggest that processes of data storage, classification and transmission are key to how poetry is created, recognized and disseminated. Conceptual writing’s attention to information classification protocols offers not only a critique of contemporary models of authorship, but also of contemporary frameworks of personal agency and intellectual property.]]></description>
<dc:subject>metadata literature writing inls520 digitalhumanities</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b36c3ac7e955/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:literature"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:writing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://turtled.net/">
    <title>turtled</title>
    <dc:date>2012-07-30T18:41:25+00:00</dc:date>
    <link>http://turtled.net/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A simple online RDF Turtle editor that allows you to render an RDF graph visually, restrict to sub-graphs via SPARQL and to export the visualisation as SVG.]]></description>
<dc:subject>rdf turtle tools inls520 inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f39cc8543ae8/</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:turtle"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://en.wikipedia.org/wiki/Zachman_Framework">
    <title>Zachman Framework - Wikipedia, the free encyclopedia</title>
    <dc:date>2012-07-02T17:15:43+00:00</dc:date>
    <link>http://en.wikipedia.org/wiki/Zachman_Framework</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The basic idea behind the Zachman Framework is that the same complex thing or item can be described for different purposes in different ways using different types of descriptions (e.g., textual, graphical). The Zachman Framework provides the thirty-six necessary categories for completely describing anything; especially complex things like manufactured goods (e.g., appliances), constructed structures (e.g., buildings), and enterprises (e.g., the organization and all of its goals, people, and technologies). The framework provides six different transformations of an abstract idea (not increasing in detail, but transforming) from six different perspectives.]]></description>
<dc:subject>description framework models information architecture inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3aba1dfc4ed0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dret.net/netdret/docs/wilde-cacm2008-document-design-matters/">
    <title>Document Design Matters (Erik Wilde and Robert J. Glushko)</title>
    <dc:date>2012-07-01T12:43:09+00:00</dc:date>
    <link>http://dret.net/netdret/docs/wilde-cacm2008-document-design-matters/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The classical approach to the data aspect of system design distinguishes conceptual, logical, and physical models. Models of each type or level are governed by metamodels that specify the kinds of concepts and constraints that can be used by each model; in most cases metamodels are accompanied by languages for describing models. For example, in database design, conceptual models usually conform to the Entity-Relationship (ER) metamodel (or some extension of it), the logical model maps ER models to relational tables and introduces normalization, and the physical model handles implementation issues such as possible denormalizations in the context of a particular database schema language. In this modeling methodology, there is a single hierarchy of models that rests on the assumption that one data model spans all modeling levels and applies to all the applications in some domain. The one true model approach assumes homogeneity, but this does not work very well for the Web. The Web as a constantly growing ecosystem of heterogeneous data and services has challenged a number of practices and theories about the design of IT landscapes. Instead of being governed by one true model used by everyone, the underlying assumption of top-down design, Web data and services evolve in an uncoordinated fashion. As a result, a fundamental challenge with Web data and services is matching and mapping local and often partial models that not only are different models of the same application domain, but also differ, implicitly or explicitly, in their associated metamodels.]]></description>
<dc:subject>models xml webservices inls520 documents design inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ba8fca0a8044/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documents"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.jenitennison.com/blog/node/171">
    <title>RDF Chimera | Jeni's Musings</title>
    <dc:date>2012-07-01T12:42:08+00:00</dc:date>
    <link>http://www.jenitennison.com/blog/node/171</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The advantages of using chimeras created from two formats with different underlying models are seldom outweighed by the disadvantages.]]></description>
<dc:subject>models rdf xml json inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:19dccd9a958f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:json"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dublincore.org/documents/abstract-model/">
    <title>DCMI Abstract Model</title>
    <dc:date>2012-05-16T20:07:38+00:00</dc:date>
    <link>http://dublincore.org/documents/abstract-model/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document specifies an abstract model for Dublin Core metadata. The primary purpose of this document is to specify the components and constructs used in Dublin Core metadata. It defines the nature of the components used and describes how those components are combined to create information structures. It provides an information model which is independent of any particular encoding syntax. Such an information model allows us to gain a better understanding of the kinds of descriptions that we are encoding and facilitates the development of better mappings and cross-syntax translations.]]></description>
<dc:subject>metadata model inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:52a4fc9a1a99/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:model"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>