<?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://w3c-facade-x.github.io/facade-x-metamodel/"/>
	<rdf:li rdf:resource="https://github.com/DigiClass/LOD-People/tree/main/sample-data"/>
	<rdf:li rdf:resource="https://web.archive.org/web/20241009144707/https://ics.uci.edu/~alspaugh/cls/shr/allen.html"/>
	<rdf:li rdf:resource="https://www.minizinc.org/"/>
	<rdf:li rdf:resource="https://github.com/karpathy/nanoGPT"/>
	<rdf:li rdf:resource="https://jena.apache.org/documentation/notes/rdf-frames.html"/>
	<rdf:li rdf:resource="https://www.wikidata.org/wiki/Help:Dates"/>
	<rdf:li rdf:resource="http://gams.uni-graz.at/archive/objects/o:depcha.bookkeeping/methods/sdef:Ontology/get"/>
	<rdf:li rdf:resource="https://pleiades.stoa.org/vocabularies/"/>
	<rdf:li rdf:resource="https://github.com/isawnyu/pleiades-geographer/blob/1af9d06e53e590df6376c24121e4acb5c1b847e3/pleiades/geographer/geo.py#L555-L629"/>
	<rdf:li rdf:resource="https://www.w3.org/TR/owl-primer/"/>
	<rdf:li rdf:resource="https://martinfowler.com/eaaDev/timeNarrative.html"/>
	<rdf:li rdf:resource="http://nlphist.hypotheses.org/356"/>
	<rdf:li rdf:resource="http://www.betaversion.org/~stefano/linotype/news/91/"/>
	<rdf:li rdf:resource="http://docstore.mik.ua/orelly/xml/schema/ch04_01.htm#xmlschema-CHP-4-SECT-1"/>
	<rdf:li rdf:resource="http://www.w3.org/TR/swbp-xsch-datatypes/"/>
	<rdf:li rdf:resource="http://external.opengeospatial.org/twiki_public/TemporalDWG/TemporalCrsUris"/>
	<rdf:li rdf:resource="http://def.seegrid.csiro.au/isotc211/iso19108/2002/temporal"/>
	<rdf:li rdf:resource="http://www.fig.net/pub/fig_2003/ts_10/ts10_3_sumrada.pdf"/>
	<rdf:li rdf:resource="http://www.galdosinc.com/archives/151"/>
	<rdf:li rdf:resource="http://www.fgdc.gov/standards/news/TSPI"/>
	<rdf:li rdf:resource="https://github.com/spumko/joi"/>
	<rdf:li rdf:resource="http://nlp.stanford.edu/~manning/papers/CICLing2011-manning-tagging.pdf"/>
	<rdf:li rdf:resource="http://alessandrovermeulen.me/2013/07/13/the-difference-between-shallow-and-deep-embedding/"/>
	<rdf:li rdf:resource="http://www.orm.net/pdf/EncDBS.pdf"/>
	<rdf:li rdf:resource="http://www.w3.org/DesignIssues/RDB-RDF.html"/>
	<rdf:li rdf:resource="http://delivery.acm.org/10.1145/1970000/1961297/p30-meijer.pdf?ip=152.2.82.226&amp;acc=OPEN&amp;CFID=167332848&amp;CFTOKEN=68292005&amp;__acm__=1359659924_04872f77bfa393f3abf563a4a75cfa34"/>
	<rdf:li rdf:resource="http://www.loc.gov/marc/marc-functional-analysis/functional-analysis.html"/>
	<rdf:li rdf:resource="http://www.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215/?tag=cc-preschool-20"/>
	<rdf:li rdf:resource="http://plato.stanford.edu/entries/process-philosophy/"/>
	<rdf:li rdf:resource="http://wiki.jvmlangsummit.com/images/a/ab/HickeyJVMSummit2009.pdf"/>
	<rdf:li rdf:resource="http://www.infoq.com/presentations/Are-We-There-Yet-Rich-Hickey"/>
	<rdf:li rdf:resource="http://t-machine.org/index.php/2012/03/16/entity-systems-what-makes-good-components-good-entities/"/>
	<rdf:li rdf:resource="http://www.chris-granger.com/2012/12/11/anatomy-of-a-knockout/"/>
	<rdf:li rdf:resource="http://listserv.loc.gov/cgi-bin/wa?A2=ind1211&amp;L=bibframe&amp;D=0&amp;T=0&amp;P=4506"/>
	<rdf:li rdf:resource="http://wiki.dublincore.org/index.php/Cataloger_Scenarios"/>
	<rdf:li rdf:resource="http://www.recognition.su/wiki/images/8/85/Breiman01stat-ml.pdf"/>
	<rdf:li rdf:resource="http://www.dataversity.net/a-short-history-of-the-er-diagram-and-information-modeling/"/>
	<rdf:li rdf:resource="http://kcoyle.blogspot.com/2012/07/futures-and-options.html"/>
	<rdf:li rdf:resource="http://www.springerlink.com.libproxy.lib.unc.edu/content/d3403g33023l7m3m/fulltext.html"/>
	<rdf:li rdf:resource="http://www.qwantz.com/index.php?comic=2292"/>
	<rdf:li rdf:resource="http://andrewgelman.com/2012/09/building-a-regression-model-with-only-27-data-points/"/>
	<rdf:li rdf:resource="http://ceur-ws.org/Vol-874/paper7.pdf"/>
	<rdf:li rdf:resource="http://vimeo.com/42186274"/>
	<rdf:li rdf:resource="http://kcoyle.blogspot.com/2012/07/authorities-and-entities.html"/>
	<rdf:li rdf:resource="http://datamineruk.com/2012/04/03/data-journalism-and-the-problem-of-narrativity/"/>
	<rdf:li rdf:resource="http://datasymposium.wordpress.com/readings/"/>
	<rdf:li rdf:resource="https://www.seegrid.csiro.au/wiki/CGIModel/GeologicTime"/>
	<rdf:li rdf:resource="http://books.google.com/books?id=YqpZKTp-Wh0C&amp;dq=Hierarchical+Modeling+and+Analysis+for+Spatial+Data&amp;source=gbs_navlinks_s"/>
	<rdf:li rdf:resource="http://listserv.loc.gov/cgi-bin/wa?A2=ind1202&amp;L=id&amp;T=0&amp;P=303"/>
	<rdf:li rdf:resource="http://plato.stanford.edu/entries/model-theory/"/>
	<rdf:li rdf:resource="http://worrydream.com/LadderOfAbstraction/"/>
	<rdf:li rdf:resource="http://worrydream.com/ExplorableExplanations/"/>
	<rdf:li rdf:resource="http://mitpress.mit.edu/books/chapters/0262693143chapm1.pdf"/>
	<rdf:li rdf:resource="http://semanticweb.cs.vu.nl/derive2011/Programme.html"/>
	<rdf:li rdf:resource="http://www.morganclaypool.com/doi/abs/10.2200/S00374ED1V01Y201107DTM019"/>
	<rdf:li rdf:resource="http://narrative.csail.mit.edu/ws12/"/>
	<rdf:li rdf:resource="http://people.csail.mit.edu/regina/6892/index.html"/>
	<rdf:li rdf:resource="http://jis.sagepub.com/content/37/3/332.abstract?etoc"/>
	<rdf:li rdf:resource="http://faculty.poly.edu/~onov/Nov_Living In a Bubble Toward a Unified Bubble Theory_2008_IJGS.pdf"/>
	<rdf:li rdf:resource="http://sourceforge.net/mailarchive/message.php?msg_name=4A72B1E1.5080201%40mondeca.com"/>
	<rdf:li rdf:resource="http://currents.cwrl.utexas.edu/Spring08/Liu"/>
	<rdf:li rdf:resource="http://www.w3.org/TR/2008/WD-owl2-new-features-20081202/#F12:_Punning"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://w3c-facade-x.github.io/facade-x-metamodel/">
    <title>Façade-X concepts and meta model specification</title>
    <dc:date>2026-01-31T00:26:25+00:00</dc:date>
    <link>https://w3c-facade-x.github.io/facade-x-metamodel/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Façade-X is the (meta-)model resulting from the abstraction of all the basic data structures used to represent source data formats, combined into a unified model. RDF languages can implement it to provide users direct access to external, heterogeneus data formats.]]></description>
<dc:subject>data modeling rdf</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b62876598659/</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:rdf"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/DigiClass/LOD-People/tree/main/sample-data">
    <title>LOD-People/sample-data at main · DigiClass/LOD-People</title>
    <dc:date>2025-08-11T15:51:46+00:00</dc:date>
    <link>https://github.com/DigiClass/LOD-People/tree/main/sample-data</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This directory contains sample person data in a range of (currently unspecified) open formats. Data needs to be open licensed, or a sample published under an open license with permission of the rightsholder.]]></description>
<dc:subject>people modeling linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7dba411e36fd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:people"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://web.archive.org/web/20241009144707/https://ics.uci.edu/~alspaugh/cls/shr/allen.html">
    <title>Allen’s interval algebra</title>
    <dc:date>2025-08-11T15:17:41+00:00</dc:date>
    <link>https://web.archive.org/web/20241009144707/https://ics.uci.edu/~alspaugh/cls/shr/allen.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In 1983 James F. Allen published a paper [Allen1983-mkti] in which he proposed thirteen basic relations between time intervals that are distinct, exhaustive, and qualitative. 

distinct because no pair of definite intervals can be related by more than one of the relationships
exhaustive because any pair of definite intervals are described by one of the relations
qualitative (rather than quantitative) because no numeric time spans are considered
These relations and the operations on them form Allen's interval algebra.]]></description>
<dc:subject>time temporal reasoning modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5f3c4dc93fc3/</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:temporal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reasoning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.minizinc.org/">
    <title>MiniZinc</title>
    <dc:date>2024-12-03T14:29:08+00:00</dc:date>
    <link>https://www.minizinc.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[MiniZinc is a high-level constraint modelling language that allows you to easily express and solve discrete optimisation problems.
]]></description>
<dc:subject>optimization constraints modeling language</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c64f8ce7203c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:optimization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:constraints"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/karpathy/nanoGPT">
    <title>karpathy/nanoGPT: The simplest, fastest repository for training/finetuning medium-sized GPTs.</title>
    <dc:date>2023-01-04T22:00:49+00:00</dc:date>
    <link>https://github.com/karpathy/nanoGPT</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The simplest, fastest repository for training/finetuning medium-sized GPTs. It's a re-write of minGPT, which I think became too complicated, and which I am hesitant to now touch. Still under active development, currently working to reproduce GPT-2 on OpenWebText dataset. The code itself aims by design to be plain and readable: train.py is a ~300-line boilerplate training loop and model.py a ~300-line GPT model definition, which can optionally load the GPT-2 weights from OpenAI. That's it.

]]></description>
<dc:subject>language modeling python</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0e01ceb77970/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:python"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://jena.apache.org/documentation/notes/rdf-frames.html">
    <title>Apache Jena - Presenting RDF as frames</title>
    <dc:date>2023-01-04T21:57:20+00:00</dc:date>
    <link>https://jena.apache.org/documentation/notes/rdf-frames.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The origins of RDF as a representation language include frame languages, in which an object, or frame, was the main unit of structuring data. Frames have slots, for example a Person frame might have an age slot, a heightslot etc. RDF, however, has taken a step beyond frame languages by making rdf:Property a first class value, not an element of a frame or resource per se. In RDF, for example, an age property can be defined: <rdf:Property rdf:ID="age">, and then applied to any resource, including, but not limited to a Person resource.

]]></description>
<dc:subject>rdf data modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4f6525c4acb0/</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:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.wikidata.org/wiki/Help:Dates">
    <title>Help:Dates - Wikidata</title>
    <dc:date>2022-11-03T16:02:01+00:00</dc:date>
    <link>https://www.wikidata.org/wiki/Help:Dates</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Wikidata offers a series of properties with datatype time, which allow storage of basic information defining single point in time. Time datatype can be further expanded with custom qualifiers to allow great range of possible time expressions. Adding and querying dates may seem simple, but available precision and changing calendars add complexity.]]></description>
<dc:subject>wikidata time temporal modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:62d7ff15f4ca/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wikidata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:temporal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gams.uni-graz.at/archive/objects/o:depcha.bookkeeping/methods/sdef:Ontology/get">
    <title>DEPCHA - Digital Edition Publishing Cooperative for Historical Accounts</title>
    <dc:date>2021-03-13T15:52:27+00:00</dc:date>
    <link>http://gams.uni-graz.at/archive/objects/o:depcha.bookkeeping/methods/sdef:Ontology/get</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The "Bookkeeping Ontology", a conceptual model being based on the REA model and CIDOC CRM, is developed in an ontology engineering process in which historians, software developers and digital humanists were involved. It formalizes the interpretation of a transaction (bk:Transaction) as combination of transfers (bk:Transfer) of measurable objects (bk:Measurable) from one accounting object (bk:Between) to another. bk:Between defines an abstract class, which unites bookkeeping categories (bk:Accounts,e.g. a cash account) and actors (individual bk:Partye.g. Washington or an unknown group of individuals bk:Group e.g. four farmers). Its physical representation in a historical source is an entry in a written accounting record (bk:Entry). The bk:Entry is an information fragment of a bk:Transaction often naming only one party, while the other party is implicit in the textual context of the entry. Further information on the temporal (bk:when), spatial (bk:where) dimension of a bk:Transaction as, well as the status (bk:status) of it (e.g. "partly paid", "settled"), can be expressed optionally. In regard to a research question a bk:Transaction can be assigned to a specific context. Every transaction consists (bk:consistsOf) at least one transfer (bk:Transfer). A single bk:Transfer describes the action of transferring a bk:Measurable in one direction (bk:from or bk:to). bk:Measurable is defined as everything that can be quantified. It has subclasses for economic goods (bk:EconomicGood, as labor: bk:Service or as physical things: bk:Commodity) and money (bk:MonetaryValues). bk:Measurable is describe by its quantity (bk:quantity) and the unit of calculation (bk:unit). The bk:Entry is described by the transcription fragment of the original source (bk:text). bk:EconomicGoodscan be categorized (what is measured) and can be assigned a price. A bk:Transfercan be carried out by (bk:by) someone who conducts the transfer process in place of the business partner (bk:Agent). When writing it down into the ledger, accounting categories (bk:debit and bk:credit) are coded optionally.]]></description>
<dc:subject>business accounting history ontology modeling linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cee464724981/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:accounting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://pleiades.stoa.org/vocabularies/">
    <title>Pleiades Vocabularies</title>
    <dc:date>2021-01-15T15:02:09+00:00</dc:date>
    <link>https://pleiades.stoa.org/vocabularies/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Controlled vocabularies employed by Pleiades including time periods and place categories]]></description>
<dc:subject>gazetteer ncgazetteer linkeddata modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:16f6ce7fa935/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:gazetteer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ncgazetteer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/isawnyu/pleiades-geographer/blob/1af9d06e53e590df6376c24121e4acb5c1b847e3/pleiades/geographer/geo.py#L555-L629">
    <title>How Pleiades sets representative points for places without geometry</title>
    <dc:date>2021-01-15T15:01:03+00:00</dc:date>
    <link>https://github.com/isawnyu/pleiades-geographer/blob/1af9d06e53e590df6376c24121e4acb5c1b847e3/pleiades/geographer/geo.py#L555-L629</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[There's a cascading set of selection criteria for connection types to use in the absence of published location objects for the place.

For Magnesia, it's using a subset of the inbound connections: those with type "part of (regional)":
https://pleiades.stoa.org/places/540923

The map shows all the inbound connections with green bowties, so you get not only the markers for "part of (regional)" that were used for reprPoint calc, but also "bounds" and the one "founded by" across to Aegean to the east (that's Magnesia on the Meander).]]></description>
<dc:subject>gazetteer ncgazetteer modeling linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e3a253cefc51/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:gazetteer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ncgazetteer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/TR/owl-primer/">
    <title>OWL 2 Web Ontology Language Primer (Second Edition)</title>
    <dc:date>2020-10-07T21:26:22+00:00</dc:date>
    <link>https://www.w3.org/TR/owl-primer/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[4.3 Class Disjointness

In Section 4.1, we stated that an individual can be an instance of several classes. However, in some cases membership in one class specifically excludes membership in another. For example, if we consider the classes Man and Woman, we know that no individual can be an instance of both classes (for the sake of the example, we disregard biological borderline cases). This “incompatibility relationship” between classes is referred to as (class) disjointness. Again, the information that two classes are disjoint is part of our background knowledge and has to be explicitly stated for a reasoning system to make use of it. This is done as follows:

Functional-Style Syntax
 DisjointClasses( :Woman :Man )
In practice, disjointness statements are often forgotten or neglected. The arguable reason for this could be that intuitively, classes are considered disjoint unless there is other evidence. By omitting disjointness statements, many potentially useful consequences can get lost. Note that in our example, the disjointness axiom is needed to deduce that Mary is not a man. Moreover, given the above axioms, a reasoner can infer the disjointness of the classes Mother and Man.]]></description>
<dc:subject>ontology bias modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:73b122ce8ce1/</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:bias"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://martinfowler.com/eaaDev/timeNarrative.html">
    <title>Temporal Patterns</title>
    <dc:date>2019-10-30T13:23:25+00:00</dc:date>
    <link>https://martinfowler.com/eaaDev/timeNarrative.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Summarizes various patterns that you can use to answer questions about the state of an information in the past. These include questions of the form "what was Martin's address on 1 Jul 1999" and "what did we think Martin's address was on 1 Jul 1999 when we sent him a bill on 12 Aug 1999".]]></description>
<dc:subject>time temporality data modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9422cecd5dad/</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:temporality"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nlphist.hypotheses.org/356">
    <title>Some Thoughts on Inform 7 for Teaching about Formal Modeling | NLP for Historical Texts</title>
    <dc:date>2017-09-02T19:52:42+00:00</dc:date>
    <link>http://nlphist.hypotheses.org/356</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The last two days I’ve been teaching a course on formal modeling in the context of our new doctoral program in Digital Studies (Programme doctoral en études numériques); in fact, it was the first ever course taught in this program. It would certainly have been easier to give a course on the basis of material that you already have, but I wanted to teach something new rather than just warming up old material. In accordance with my ideas for developing the digital humanities at UNIL, I decided on the topic of formal modeling. This meant, however, a lot of work over the summer and, with the date of the course coming closer, nagging doubts about the—newly developed and thus untested—content. Would I have enough material? Would the participants be able to relate to it, or would it be too hard? And so on.

I had a small but very diverse group of doctoral students from archeology, literary studies, film studies, and sociology, and I’m happy to report that the program on which I had eventually settled turned out to be just right. The course still included one very experimental section on Friday afternoon: I wanted to explore the feasibility of using Inform 7  to introduce formal modeling.]]></description>
<dc:subject>modeling language digitalhumanities narrative interactive fiction</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cbbe9451787a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:narrative"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interactive"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:fiction"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.betaversion.org/~stefano/linotype/news/91/">
    <title>Stefano’s Linotype » Closed World vs. Open World: the First Semantic Web Battle</title>
    <dc:date>2015-08-24T13:00:00+00:00</dc:date>
    <link>http://www.betaversion.org/~stefano/linotype/news/91/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Note how the open world assumption is considered evil by the entire range of XML and web service technologies that try really hard to standardize, normalize, describe and validate everything that goes on, hoping to create an ordered world in which things work smoothly.

The open world assumption tries hard to avoid that: validation, in a open world assumption, is, well, limiting, if not directly out of place.

But then again, validation is a fact of life and a very strong requirement for some environments that at least try to uniform and minimize differences and disorder within a particular application or closed community.

So, the question on the table, and it’s a big one, is: how do we allow open world and closed world assumptions to coexist? is it just a parameter in the way the inferencing engines run (one empowers doubt, the other rejects it) or is something impossible to achieve?]]></description>
<dc:subject>semanticweb modeling inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f5ae59133b25/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semanticweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://docstore.mik.ua/orelly/xml/schema/ch04_01.htm#xmlschema-CHP-4-SECT-1">
    <title>Using Predefined Simple Datatypes (XML Schema)</title>
    <dc:date>2014-06-25T17:55:14+00:00</dc:date>
    <link>http://docstore.mik.ua/orelly/xml/schema/ch04_01.htm#xmlschema-CHP-4-SECT-1</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[W3C XML Schema introduced a decoupling between the data, as it can be read from the instance documents (the "lexical space"), and the value, as interpreted according to the datatype (the "value space").]]></description>
<dc:subject>xml data modeling types</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:aad019e6d2a1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:types"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/TR/swbp-xsch-datatypes/">
    <title>XML Schema Datatypes in RDF and OWL</title>
    <dc:date>2014-06-25T17:29:14+00:00</dc:date>
    <link>http://www.w3.org/TR/swbp-xsch-datatypes/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The RDF and OWL Recommendations use the simple types from XML Schema. This document addresses three questions left unanswered by these Recommendations: Which URIref should be used to refer to a user defined datatype? Which values of which XML Schema simple types are the same? How to use the problematic xsd:duration in RDF and OWL? In addition, we further describe how to integrate OWL DL with user defined datatypes (in appendix B).]]></description>
<dc:subject>owl rdf xml data modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:53efb1481b0f/</dc:identifier>
<taxo:topics><rdf:Bag>	<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:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://external.opengeospatial.org/twiki_public/TemporalDWG/TemporalCrsUris">
    <title>TemporalCrsUris &lt; TemporalDWG &lt; OGC Public Wiki</title>
    <dc:date>2014-06-18T22:05:38+00:00</dc:date>
    <link>http://external.opengeospatial.org/twiki_public/TemporalDWG/TemporalCrsUris</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In this page we show (+ discuss?) the initial set of URIs for temporal coordinate reference systems (and subcomponents) going to be submitted to OGC Naming Authority. This is first set of well-known temporal coordinate reference systems, which does not want to be exhaustive but a starting point: future new of URIs and resources will hopefully be established alongside the development of the Temporal DWG.]]></description>
<dc:subject>time temporal modeling rdf owl</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c8d808e9fa8c/</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:temporal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:owl"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://def.seegrid.csiro.au/isotc211/iso19108/2002/temporal">
    <title>OWL representation of ISO 19108 (Geographic Information - Temporal Schema)</title>
    <dc:date>2014-06-18T21:16:49+00:00</dc:date>
    <link>http://def.seegrid.csiro.au/isotc211/iso19108/2002/temporal</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[An OWL representation of part of the model for Temporal objects and reference systems from ISO 19108:2002 Geographic Information - Temporal Schema

]]></description>
<dc:subject>time temporal ontology modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:31c8c22360a7/</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:temporal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.fig.net/pub/fig_2003/ts_10/ts10_3_sumrada.pdf">
    <title>Temporal Data and Temporal Reference Systems</title>
    <dc:date>2014-06-18T21:13:29+00:00</dc:date>
    <link>http://www.fig.net/pub/fig_2003/ts_10/ts10_3_sumrada.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This paper describes the significance and role of temporal data in spatial information systems. Temporal characteristics of spatial objects unable us to describe and interpret the reality around us with additional aspects. Time is the dimension, which is according to its geometry and topology similar to other spatial extensions. Processes of updating and temporal analyses of spatial data offer an important source of spatial information. This article also presents the importance and describes the content of the international standard ISO 19108:2002 GI - Temporal schema that was developed, among others related geographic information standards, by ISO technical committee (TC) 211 Geographic Information/Geomatics. Further on, the usage of standardized temporal schema that forms a part of metadata is described and emphasized.]]></description>
<dc:subject>time temporal modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e2739250d104/</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:temporal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.galdosinc.com/archives/151">
    <title>Dealing with time in GML « Galdos Systems Inc.</title>
    <dc:date>2014-06-18T20:28:16+00:00</dc:date>
    <link>http://www.galdosinc.com/archives/151</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Several time representations are possible for timePosition including:
XML Schema time or dataTime (this is also based on ISO 8601)
CalDate – enables a very llexible encoding of calendar dates.
A URI reference
A decimal value
The interpretation of the timePosition value is determined by the optional attributes of timePosition. In particular the frame attribute allows the user to specify the temporal reference system to be used for interpretation of the value of gml:timePosition.]]></description>
<dc:subject>time temporal modeling xml</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9b8d236f1145/</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:temporal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.fgdc.gov/standards/news/TSPI">
    <title>FGDC endorses the Time Space Position Information (TSPI) Version 2.0 standard — Federal Geographic Data Committee</title>
    <dc:date>2014-06-18T20:07:09+00:00</dc:date>
    <link>http://www.fgdc.gov/standards/news/TSPI</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Time-Space-Position Information (TSPI) Version 2.0 standard provides a single means of encoding spatiotemporal information for the storage, manipulation, interchange, and exploitation of spatiotemporal data. As US government systems become more interoperable, the need to unambiguously encode spatiotemporal data for exchange among systems is paramount. The TSPI common core standard is designed to be that unambiguous eXtensible Markup Language (XML) encoding standard. 
 
The TSPI Version 2.0 standard is a robust mechanism for expressing "Where" and "When" spatiotemporal data in various core and extended XML-based information schemata throughout the US Federal Sector. Spatial information includes position, extent (shape), size, orientation, and rates of change in these characteristics, while temporal information includes position (instant), extent (duration), and periodic recurrence characteristics. ]]></description>
<dc:subject>time space temporal spatial data modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6aa6d522f65e/</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:space"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:temporal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:spatial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/spumko/joi">
    <title>spumko/joi</title>
    <dc:date>2014-06-09T13:36:18+00:00</dc:date>
    <link>https://github.com/spumko/joi</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Object schema description language and validator for JavaScript objects.

]]></description>
<dc:subject>javascript nodejs validation data modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:be231d2c2e27/</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:nodejs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:validation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nlp.stanford.edu/~manning/papers/CICLing2011-manning-tagging.pdf">
    <title>Part-of-Speech Tagging from 97% to 100%: Is It Time for Some Linguistics?</title>
    <dc:date>2014-03-29T11:27:30+00:00</dc:date>
    <link>http://nlp.stanford.edu/~manning/papers/CICLing2011-manning-tagging.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[I examine what would be necessary to move part-of-speech tagging performance from its current level of about 97.3% token accuracy (56% sentence accuracy) to close to 100% accuracy. I suggest that it must still be possible to greatly increase tagging performance and examine some useful improvements that have recently been made to the Stanford Part-of-Speech Tagger. However, an error analysis of some of the remaining errors suggests that there is limited further mileage to be had either from better machine learning or better features in a discriminative sequence classifier. The prospects for further gains from semi- supervised learning also seem quite limited. Rather, I suggest and begin to demonstrate that the largest opportunity for further progress comes from improving the taxonomic basis of the linguistic resources from which taggers are trained. That is, from improved descriptive linguistics. How- ever, I conclude by suggesting that there are also limits to this process. The status of some words may not be able to be adequately captured by assigning them to one of a small number of categories. While conventions can be used in such cases to improve tagging consistency, they lack a strong linguistic basis.]]></description>
<dc:subject>nlp linguistics modeling representation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4467b9981603/</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:linguistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:representation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://alessandrovermeulen.me/2013/07/13/the-difference-between-shallow-and-deep-embedding/">
    <title>The difference between shallow and deep embedding - Alessandro Vermeulen</title>
    <dc:date>2013-07-15T13:30:14+00:00</dc:date>
    <link>http://alessandrovermeulen.me/2013/07/13/the-difference-between-shallow-and-deep-embedding/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Con­cep­tu­ally, a shal­low em­bed­ding cap­tures the se­man­tics of the data of the do­main in a data type and pro­vides a fixed in­ter­pre­ta­tion of the data, whereas a deep em­bed­ding goes be­yond this and cap­tures the se­man­tics of the op­er­a­tions on the do­main en­abling vari­able in­ter­pre­ta­tions.]]></description>
<dc:subject>modeling data semantics functional haskell</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f6df2dce8802/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semantics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:functional"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:haskell"/>
</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.w3.org/DesignIssues/RDB-RDF.html">
    <title>Relational Databases and the Semantic Web (in Design Issues)</title>
    <dc:date>2013-02-08T17:23:24+00:00</dc:date>
    <link>http://www.w3.org/DesignIssues/RDB-RDF.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Is the RDF model an entity-relationship mode? Yes and no. It is great as a basis for ER-modelling, but because RDF is used for other things as well, RDF is more general. RDF is a model of entities (nodes) and relationships. If you are used to the "ER" modelling system for data, then the RDF model is basically an openning of the ER model to work on the Web. In typical ER model involved entity types, and for each entity type there are a set of relationships (slots in the typical ER diagram). The RDF model is the same, except that relationships are first class objects: they are identified by a URI, and so anyone can make one. Furthurmore, the set of slots of an object is not defined when the class of an object is defined. The Web works though anyone being (technically) allowed to say anything about anything. This means that a relationship between two objects may be stored apart from any other information about the two objects. This is different from object-oriented systems often used to implement ER models, which generally assume that information about an object is stored in an object: the definition of the class of an object defines the storage implied for its properties.]]></description>
<dc:subject>database modeling semweb rdf relationships</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2603731fdd34/</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:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:relationships"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://delivery.acm.org/10.1145/1970000/1961297/p30-meijer.pdf?ip=152.2.82.226&amp;acc=OPEN&amp;CFID=167332848&amp;CFTOKEN=68292005&amp;__acm__=1359659924_04872f77bfa393f3abf563a4a75cfa34">
    <title>A co-Relational Model of Data for Large Shared Data Banks</title>
    <dc:date>2013-01-31T19:15:17+00:00</dc:date>
    <link>http://delivery.acm.org/10.1145/1970000/1961297/p30-meijer.pdf?ip=152.2.82.226&amp;acc=OPEN&amp;CFID=167332848&amp;CFTOKEN=68292005&amp;__acm__=1359659924_04872f77bfa393f3abf563a4a75cfa34</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In this article we present a mathematical data model for the most common noSQL databases—namely, key/value relationships—and demonstrate that this data model is the mathematical dual of SQL's relational data model of foreign-/primary-key relationships. Following established mathematical nomenclature, we refer to the dual of SQL as coSQL. We also show how a single generalization of the relational algebra over sets—namely, monads and monad comprehensions—forms the basis of a common query language for both SQL and noSQL. Despite common wisdom, SQL and coSQL are not diabolically opposed, but instead deeply connected via beautiful mathematical theory.]]></description>
<dc:subject>database modeling theory math nosql</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cf36d06b8488/</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:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:theory"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:math"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nosql"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.loc.gov/marc/marc-functional-analysis/functional-analysis.html">
    <title>Functional Analysis of MARC 21 (Library of Congress)</title>
    <dc:date>2013-01-03T16:23:03+00:00</dc:date>
    <link>http://www.loc.gov/marc/marc-functional-analysis/functional-analysis.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In 2001, the Network Development and MARC Standards Office (NDMSO) at the Library of Congress commissioned a study to examine MARC 21 from several perspectives:

the FRBR model
the AACR cataloging code model
a set of user tasks that MARC 21 might logically support
The study used the models from IFLA's Functional Requirements for Bibliographic Records (FRBR) and the related Logical Structure of the Anglo-American Cataloguing Rules and was carried out by the consultant who was largely responsible for those studies, Tom Delsey, of Thomas J. Delsey Consulting. By sponsoring this analysis and making it available, the Network Development and MARC Standards Office and others hoped to use the information when analyzing or making decisions relating to format maintenance, system implementation, and data sharing. As a result, the study has proven to be an important tool for the continuing development of the MARC 21 standards.]]></description>
<dc:subject>FRBR MARC standards modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a9754b8b5ee0/</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:MARC"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215/?tag=cc-preschool-20">
    <title>Domain-Driven Design: Tackling Complexity in the Heart of Software: Eric Evans: 9780321125217: Amazon.com: Books</title>
    <dc:date>2012-12-27T14:38:39+00:00</dc:date>
    <link>http://www.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215/?tag=cc-preschool-20</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA["It’s a great primer on how to turn a problem space into a beautiful OO domain model. What should your models be called? What logic goes where? How do we reproduce reality into an object model."]]></description>
<dc:subject>modeling entities oop</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e5ad439877cb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:entities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:oop"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://plato.stanford.edu/entries/process-philosophy/">
    <title>Process Philosophy (Stanford Encyclopedia of Philosophy)</title>
    <dc:date>2012-12-23T02:54:53+00:00</dc:date>
    <link>http://plato.stanford.edu/entries/process-philosophy/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[...the purpose of philosophy is to enhance human understanding, and philosophical ‘explanations’ so-called are in the end re-descriptions in technical terms that cannot be defined by axioms alone but must somehow be grounded in experience.

 If we admit that the basic entities of our world are processes, we can generate better philosophical descriptions of all the kinds of entities and relationships we are committed to when we reason about our world in common sense and in science: from quantum entanglement to consciousness, from computation to feelings, from things to institutions, from organisms to societies, from traffic jams to climate change, from spacetime to beauty.

...process philosophers assume that the only primary or basic ontological categories should be terms for occurring entities, and that certain formal theories—for example, set theory—are ill-suited of themselves, without modifications, to express the dynamic relationships among occurrences.

Bergson argued that the process-character of being is precisely out of our cognitive reach, at least in so far as we try to conceptualize what we experience. As long as we understand conscious experience as a subject-object relation, Bergson pointed out, we merely follow the theoretical habits in which we have been conditioned by the substance-metaphysical tradition. However, when we carefully attend to what we take in during conscious experience and who we are, without forcing a conceptualization of that experiential content or the act of experience, we find not a relation and ready-made relata but an interactivity or ongoing interfacing with the world. In immediate, non-conceptualized experience we grasp the dynamicity of this interfacing as becoming or the flow of duration (“durée”), but this felt dynamic content of our experience transcends what we can conceptually articulate. As soon as we try to conceptualize what we have grasped in “intuition” we turn the continuous complex flow of experience into a sequence of discrete units, into pluralities of states of objects at locations that engender Zeno’s paradoxes of motion, and we transform our entangled being with the world into the ever puzzling opposition of a subject and an object.

G. W. Leibniz (1646–1716) developed a fully-fledged process-based metaphysics, postulating as basic individuals so-called “monads.” Monads are ordered sequences of states of affairs consisting of the co-exemplification of properties during some period of time. But monads are not static: they are endowed with an inherent “active force” that engenders the transitions between states. Moreover, since Leibniz took temporal relations to be “founded” in the properties of monads, states of monads are per se not temporally discrete.]]></description>
<dc:subject>process philosophy modeling description monads</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b77e508802d1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:process"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:philosophy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:monads"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://wiki.jvmlangsummit.com/images/a/ab/HickeyJVMSummit2009.pdf">
    <title>Are We There Yet?</title>
    <dc:date>2012-12-14T16:04:30+00:00</dc:date>
    <link>http://wiki.jvmlangsummit.com/images/a/ab/HickeyJVMSummit2009.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Rich Hickey gave an interesting prez on rethinking time and state in programming inspired by A.N. Whitehead.]]></description>
<dc:subject>functional programming modeling time whitehead ontology</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:931511fcbb10/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:functional"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:whitehead"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.infoq.com/presentations/Are-We-There-Yet-Rich-Hickey">
    <title>Are We There Yet?</title>
    <dc:date>2012-12-14T16:03:15+00:00</dc:date>
    <link>http://www.infoq.com/presentations/Are-We-There-Yet-Rich-Hickey</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In his keynote at JVM Languages Summit 2009, Rich Hickey advocated for the reexamination of basic principles like state, identity, value, time, types, genericity, complexity, as they are used by OOP today, to be able to create the new constructs and languages to deal with the massive parallelism and concurrency of the future. ]]></description>
<dc:subject>functional programming modeling time whitehead ontology</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:35557187c0c9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:functional"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:whitehead"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ontology"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://t-machine.org/index.php/2012/03/16/entity-systems-what-makes-good-components-good-entities/">
    <title>T=Machine » Entity Systems: what makes good Components? good Entities?</title>
    <dc:date>2012-12-12T15:25:13+00:00</dc:date>
    <link>http://t-machine.org/index.php/2012/03/16/entity-systems-what-makes-good-components-good-entities/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[What makes a good Component?
How should I split my conceptual model into Entities and Components?
How should I split my algorithms and methods into Systems?]]></description>
<dc:subject>ECS design data modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:62e94a6f4e72/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ECS"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.chris-granger.com/2012/12/11/anatomy-of-a-knockout/">
    <title>Chris Granger - Anatomy of a knockout</title>
    <dc:date>2012-12-12T15:10:58+00:00</dc:date>
    <link>http://www.chris-granger.com/2012/12/11/anatomy-of-a-knockout/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[So what we're doing is exploding all these monolithic objects apart, and turning entities in the game into simple groupings of components.]]></description>
<dc:subject>clojure games design data modeling ECS</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ac196608047b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:clojure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:games"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<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:ECS"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://listserv.loc.gov/cgi-bin/wa?A2=ind1211&amp;L=bibframe&amp;D=0&amp;T=0&amp;P=4506">
    <title>BIBFRAME Archives -- November 2012 (#35)</title>
    <dc:date>2012-11-28T16:59:39+00:00</dc:date>
    <link>http://listserv.loc.gov/cgi-bin/wa?A2=ind1211&amp;L=bibframe&amp;D=0&amp;T=0&amp;P=4506</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA["Recorded elements are distinctly and uniquely associated with each class of entity."]]></description>
<dc:subject>FRBR data modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6dc57943101d/</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:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://wiki.dublincore.org/index.php/Cataloger_Scenarios">
    <title>Cataloger Scenarios - DCMI_MediaWiki</title>
    <dc:date>2012-11-27T22:08:20+00:00</dc:date>
    <link>http://wiki.dublincore.org/index.php/Cataloger_Scenarios</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[These scenarios are intended to assist catalogers in visualizing how their work might flow in a setting that used RDA Vocabularies and FRBR relationships. The goal here is just to show how these packages of information might fit together and how catalogers can use their knowledge and experience in different contexts.]]></description>
<dc:subject>cataloging rda standards modeling data</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c01bb1856757/</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:rda"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.recognition.su/wiki/images/8/85/Breiman01stat-ml.pdf">
    <title>Statistical Modeling: The Two Cultures</title>
    <dc:date>2012-11-25T23:26:45+00:00</dc:date>
    <link>http://www.recognition.su/wiki/images/8/85/Breiman01stat-ml.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[There are two cultures in the use of statistical modeling to reach conclusions from data. One assumes that the data are generated bya given stochastic data model. The other uses algorithmic models and treats the data mechanism as unknown. The statistical communityhas been committed to the almost exclusive use of data models. This commitment has led to irrelevant theory, questionable conclusions, and has kept statisticians from working on a large range of interesting current problems. Algorithmic modeling, both in theoryand practice, has developed rapidlyin ﬁelds outside statistics. It can be used both on large complex data sets and as a more accurate and informative alternative to data modeling on smaller data sets. If our goal as a ﬁeld is to use data to solve problems, then we need to move awayfrom exclusive dependence on data models and adopt a more diverse set of tools.]]></description>
<dc:subject>statistics models modeling algorithms</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6442520a0a30/</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:models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:algorithms"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.dataversity.net/a-short-history-of-the-er-diagram-and-information-modeling/">
    <title>A Short History of the ER Diagram and Information Modeling | Articles | DATAVERSITY</title>
    <dc:date>2012-11-25T23:20:20+00:00</dc:date>
    <link>http://www.dataversity.net/a-short-history-of-the-er-diagram-and-information-modeling/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Data modeling came into vogue in the 1970s driven by the need to properly model databases or even real-world business processes. Peter Chen, an attendee at this year’s Enterprise Data World conference, popularized the Entity-Relationship model in a paper published in 1976.

The previous year, A. P. G. Brown, in a publication for the International Federation for Information Processing (IFIP), published an article called Modelling (sic) a Real-World System and Designing a Schema to Represent It. While Brown’s seminal volume is surely relevant to this discussion, Chen’s paper, especially since it focused on the terms “entity” and “relationship,” is generally considered to be the beginning of the Data Modeling practice as it is known today.

Bachman Diagrams, a form of Data Modeling, also deserve some mention. Charles Bachman’s seminal late 60s article in DATA BASE put forth the concept of database “entities” and one of the first data structure diagrams, later to be known as a Bachman Diagram. Bachman was highly influential on Peter Chen.

Bachman wasn’t alone in contributing to the dawn of the Data Modeling practice. In the early 1970s, a UK-based systems engineer for IBM, J. Barrie Leigh, developed nascent ER diagrams for annuity system he worked on for the Royal Insurance.

Clive Finkelstein’s work as the progenitor for the practice of Information Engineering remains a relevant part of the history of data or process modeling. James Martin, for a time an associate of Finkelstein, is also a major player behind the history of Computer Aided Software Engineering (CASE) and Business Process Reengineering which plays an important role in Enterprise Information Architecture as a whole.

A closer look at these progenitors of the Information Modeling practice reveals how a few software and systems engineers were able to influence an entire history. Their work still echoes today whenever a DBA places an entity on a model or draws a line denoting a one-to-many relationship.]]></description>
<dc:subject>data modeling history</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3c035502817a/</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:history"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kcoyle.blogspot.com/2012/07/futures-and-options.html">
    <title>Coyle's InFormation: Futures and Options</title>
    <dc:date>2012-10-16T01:12:04+00:00</dc:date>
    <link>http://kcoyle.blogspot.com/2012/07/futures-and-options.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[It helps to remember the three database scenarios of RDA. These show a progressive view of moving from the flat record format of MARC to a relational database. The three RDA scenarios (which should be read from the bottom up) are:

Relational database model -- In this model, data is stored as separate entities, presumably following the entities defined in FRBR. Each entity has a defined set of data elements and the bibliographic description is spread across these entities which are then linked together using FRBR-like relationships.

Linked authority files -- The database has bibliographic records and has authority records, and there are machine-actionable links between them. These links should allow certain strings, like name headings, to be stored only once, and should reflect changes to the authority file in the related bibliographic records.

Flat file model -- The database has bibliographic records and it has authority records, but there is no machine-actionable linking between the two. This is the design used by some library systems, but it is also a description of the situation that existed with the card catalog.]]></description>
<dc:subject>library data structure models modeling cataloging</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0a7e58383e5b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:structure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cataloging"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.springerlink.com.libproxy.lib.unc.edu/content/d3403g33023l7m3m/fulltext.html">
    <title>How Modeling Can Go Wrong</title>
    <dc:date>2012-10-06T02:19:47+00:00</dc:date>
    <link>http://www.springerlink.com.libproxy.lib.unc.edu/content/d3403g33023l7m3m/fulltext.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Modeling and simulation clearly have an upside. My discussion here will deal with the inevitable downside of modeling — the sort of things that can go wrong. It will set out a taxonomy for the pathology of models — a catalogue of the various ways in which model contrivance can go awry. In the course of that discussion, I also call on some of my past experience with models and their vulnerabilities.]]></description>
<dc:subject>modeling models model simulation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d2dfab8fcee6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:model"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:simulation"/>
</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://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://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://vimeo.com/42186274">
    <title>Lecture - Professor Roberto Franzosi (Emory University): Quantitative Narrative Analysis (QNA) on Vimeo</title>
    <dc:date>2012-08-13T13:42:58+00:00</dc:date>
    <link>http://vimeo.com/42186274</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The talk will illustrate Quantitative Narrative Analysis (QNA), a methodological approach to texts that allows researchers to structure the information contained in narrative texts in ways that make possible a statistical analysis of the information. The approach exploits the invariant linguistic structural properties of narrative (namely, the chronological sequential order of narrative clauses and their simple linguistic structure SVO, or Subject-Verb-Object. In narrative, Subjects are typically social actors, Verbs are social actions, and Objects are either social actors or physical objects. Each SVO element can also have attributes (e.g., time and space of action). The SVO and their attributes provide an invariant structure of narrative also known as “story grammar” (basically, the 5 W’s and H of journalism: Who, What, When, Where, Why, and How). The talk will highlight the power of QNA using data from two datasets: on the rise of Italian fascism (1919-1922) (50,000 newspaper articles for some 200,000 clauses) and on lynchings in Georgia (1875-1930) (1,300 articles coded for some 8,000 clauses).]]></description>
<dc:subject>narrative contentanalysis events modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0c871321429f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:narrative"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:contentanalysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:events"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kcoyle.blogspot.com/2012/07/authorities-and-entities.html">
    <title>Coyle's InFormation: Authorities and entities</title>
    <dc:date>2012-07-25T18:30:23+00:00</dc:date>
    <link>http://kcoyle.blogspot.com/2012/07/authorities-and-entities.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Because we have authority records for some of the same things that are entities in the entity-relationship model of FRBR, there seems to be a wide-spread assumption that an authority record is the same as an entity record. In fact, IFLA has developed "authority data" models for names and for subjects that are intended to somehow mix with the FRBR model to create a more complete view of the bibliographic description.

This may be a wholly mis-guided activity, for the reason that authority control and entities (in the entity-relation sense) are not at all the same thing.]]></description>
<dc:subject>cataloging library data models modeling authority structure</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:e672fecb9caa/</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:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authority"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:structure"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://datamineruk.com/2012/04/03/data-journalism-and-the-problem-of-narrativity/">
    <title>Data, Journalism and the Problem of Narrativity « Data Miner UK</title>
    <dc:date>2012-04-09T20:24:34+00:00</dc:date>
    <link>http://datamineruk.com/2012/04/03/data-journalism-and-the-problem-of-narrativity/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Information is costly to manipulate and retrieve. By finding the pattern, the logic of the series, you no longer need to memorize it all. You just store the pattern. And, as we can see here, a pattern is obviously more compact than raw information. We have a hunger for rules because we need to reduce the dimension of matters so they can get into our heads. A novel, a story, a myth, or a tale, all have the same function: they spare us from the complexity of the world. They help build in our mind an idea. And that’s what true narratives do. They don’t just paint pictures they build structures in our mind upon which logic is built.]]></description>
<dc:subject>data journalism information modeling narrative</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:befea541924d/</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:information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:narrative"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://datasymposium.wordpress.com/readings/">
    <title>Readings | Knowledge Organization and Data Modeling in the Humanities</title>
    <dc:date>2012-03-16T15:22:27+00:00</dc:date>
    <link>http://datasymposium.wordpress.com/readings/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The following materials have been suggested by participants in the workshop, and have been organized into rough groupings for ease of navigation. This is not intended as a comprehensive list of readings on data modeling in the humanities, but (at the moment) reflects the textual emphasis of the workshop.]]></description>
<dc:subject>digitalhumanities modeling knowledge organization</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8ae73d781327/</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:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:knowledge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:organization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.seegrid.csiro.au/wiki/CGIModel/GeologicTime">
    <title>GeologicTime &lt; CGIModel &lt; SEEGrid</title>
    <dc:date>2012-02-29T18:32:10+00:00</dc:date>
    <link>https://www.seegrid.csiro.au/wiki/CGIModel/GeologicTime</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The classic "geological time scale" is a hierarchical ordinal system, in which the eras are ranked: "stages" nest within "series" within "systems" within "eras" within "eons" (in the most common version of the ranking system).

The time positions of the start and end points or geological eras are not known precisely, except for most of the Precambrian, where the boundaries are defined chronometrically. Typically there will be a number of estimates available, based on dating specimens retrieved from particular localities believed to correspond to the boundary of interest. A locality ratified by ICS is known as a "Global Boundary Stratotype Section and Point (GSSP)" and is indicated by a "golden spike" on the chart.

The complete definition of a geological time scale requires a description of the hierarchical structure of named eras the temporal positions of the boundaries between the eras.]]></description>
<dc:subject>geology periodization modeling standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:610fdb18d2ad/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:geology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:periodization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://books.google.com/books?id=YqpZKTp-Wh0C&amp;dq=Hierarchical+Modeling+and+Analysis+for+Spatial+Data&amp;source=gbs_navlinks_s">
    <title>Hierarchical modeling and analysis for spatial data - Sudipto Banerjee, Bradley P. Carlin, Alan E. Gelfand - Google Books</title>
    <dc:date>2012-02-28T16:02:24+00:00</dc:date>
    <link>http://books.google.com/books?id=YqpZKTp-Wh0C&amp;dq=Hierarchical+Modeling+and+Analysis+for+Spatial+Data&amp;source=gbs_navlinks_s</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Among the many uses of hierarchical modeling, their application to the statistical analysis of spatial and spatio-temporal data from areas such as epidemiology And environmental science has proven particularly fruitful. Yet to date, the few books that address the subject have been either too narrowly focused on specific aspects of spatial analysis, or written at a level often inaccessible to those lacking a strong background in mathematical statistics.Hierarchical Modeling and Analysis for Spatial Data is the first accessible, self-contained treatment of hierarchical methods, modeling, and data analysis for spatial and spatio-temporal data. Starting with overviews of the types of spatial data, the data analysis tools appropriate for each, and a brief review of the Bayesian approach to statistics, the authors discuss hierarchical modeling for univariate spatial response data, including Bayesian kriging and lattice (areal data) modeling. They then consider the problem of spatially misaligned data, methods for handling multivariate spatial responses, spatio-temporal models, and spatial survival models. The final chapter explores a variety of special topics, including spatially varying coefficient models.]]></description>
<dc:subject>bayes space temporality modeling statistics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1eddad2ec1c7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bayes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:space"/>
	<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:statistics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://listserv.loc.gov/cgi-bin/wa?A2=ind1202&amp;L=id&amp;T=0&amp;P=303">
    <title>If French language is a class ...</title>
    <dc:date>2012-02-16T20:10:57+00:00</dc:date>
    <link>http://listserv.loc.gov/cgi-bin/wa?A2=ind1202&amp;L=id&amp;T=0&amp;P=303</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[... any idea of what an instance could be?

Looking closely at http://id.loc.gov/vocabulary/iso639-1/fr for the first
time seriously (shame on me, can't even tell since when this URI has been
available) ...
I read that it is a *rdfs:subClassOf*
http://id.loc.gov/vocabulary/iso639-1/iso639-1_Language

Well, why isn't it an *instance* of this class?
I can see the rationale  : there is not "one" French language, one can
imagine further subclasses such as Canadian French, Middle-Age French etc.
so French is a class of languages OK.
But are there any subclasses of French defined at id.loc.gov ?

And if it were the case, where do one stop the subclasses recursion and
introduce instances, if any? Is it turtles all the way down?]]></description>
<dc:subject>modeling classification inls520 taxonomy</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0f69e48882a0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<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:taxonomy"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://plato.stanford.edu/entries/model-theory/">
    <title>Model Theory (Stanford Encyclopedia of Philosophy)</title>
    <dc:date>2011-11-21T22:55:06+00:00</dc:date>
    <link>http://plato.stanford.edu/entries/model-theory/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Model theory began with the study of formal languages and their interpretations, and of the kinds of classification that a particular formal language can make. Mainstream model theory is now a sophisticated branch of mathematics (see the entry on first-order model theory). But in a broader sense, model theory is the study of the interpretation of any language, formal or natural, by means of set-theoretic structures, with Alfred Tarski's truth definition as a paradigm. In this broader sense, model theory meets philosophy at several points, for example in the theory of logical consequence and in the semantics of natural languages.]]></description>
<dc:subject>logic representation language interpretation modeling models linguistics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:474ab153c3cc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:logic"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:representation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interpretation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linguistics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://worrydream.com/LadderOfAbstraction/">
    <title>Up and Down the Ladder of Abstraction</title>
    <dc:date>2011-11-09T18:00:30+00:00</dc:date>
    <link>http://worrydream.com/LadderOfAbstraction/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[How do we explore? If you move to a new city, you might learn the territory by walking around. Or you might peruse a map. But far more effective than either is both together — a street-level experience with higher-level guidance.

Likewise, the most powerful way to gain insight into a system is by moving between levels of abstraction. Many designers do this instinctively. But it's easy to get stuck on the ground, experiencing concrete systems with no higher-level view. It's also easy to get stuck in the clouds, working entirely with abstract equations or aggregate statistics.

This interactive essay presents the ladder of abstraction, a technique for thinking explicitly about these levels, so a designer can move among them consciously and confidently.]]></description>
<dc:subject>modeling visualization explanation thinking</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0d6839da5fce/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:explanation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:thinking"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://worrydream.com/ExplorableExplanations/">
    <title>Explorable Explanations</title>
    <dc:date>2011-11-09T16:44:54+00:00</dc:date>
    <link>http://worrydream.com/ExplorableExplanations/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The reactive document integrates spreadsheet-like models into authored text. It can be read at multiple levels, depending on the reader's level of interest. The hurried reader can skim it. The casual reader can read it as-is. The curious reader can adjust the author's scenarios. The engaged reader can explore scenarios of his own devising.]]></description>
<dc:subject>interactive reading interpretation explanation modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9babbb5382f6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interactive"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interpretation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:explanation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mitpress.mit.edu/books/chapters/0262693143chapm1.pdf">
    <title>What Goes Around Comes Around - Stonebraker &amp; Hellerstein (35 years of data model proposals)</title>
    <dc:date>2011-09-12T15:48:21+00:00</dc:date>
    <link>http://mitpress.mit.edu/books/chapters/0262693143chapm1.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This paper provides a summary of 35 years of data model proposals, grouped into 9
different eras.  We discuss the proposals of each era, and show that there are only a few
basic data modeling ideas, and most have been around a long time.  Later proposals
inevitably bear a strong resemblance to certain earlier proposals.  Hence, it is a
worthwhile exercise to study previous proposals.]]></description>
<dc:subject>data modeling models history</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1f8d94221e6a/</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:models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://semanticweb.cs.vu.nl/derive2011/Programme.html">
    <title>Detection, Representation, and Exploitation of Events in the Semantic Web Workshop in conjunction with the 10th International Semantic Web Conference 2011 23 October Registration now open at: http://iswc2011.semanticweb.org/attending/registration</title>
    <dc:date>2011-09-09T20:53:24+00:00</dc:date>
    <link>http://semanticweb.cs.vu.nl/derive2011/Programme.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In recent years, researchers in several communities involved in aspects of the web have begun to realise the potential benefits of assigning an important role to events in the representation and organisation of knowledge and media. While a good deal of relevant research has been done in the semantic web community (for example on the modeling of events), a lot of complementary research has been done in other communities, such as multimedia processing and information retrieval. The goal of this workshop is to advance research on this general topic within the semantic web community, by both building on existing semantic web work and integrating results and methods from other areas, with a particular focus on issues that are central to the semantic web.]]></description>
<dc:subject>events modeling semweb nlp</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4e0ff593310b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:events"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nlp"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.morganclaypool.com/doi/abs/10.2200/S00374ED1V01Y201107DTM019">
    <title>Morgan &amp; Claypool Publishers - Synthesis Lectures on Data Management - 3(4):1 - Abstract</title>
    <dc:date>2011-08-16T16:27:13+00:00</dc:date>
    <link>http://www.morganclaypool.com/doi/abs/10.2200/S00374ED1V01Y201107DTM019</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[With the proliferation of citizen reporting, smart mobile devices, and social media, an increasing number of people are beginning to generate information about events they observe and participate in. A significant fraction of this information contains multimedia data to share the experience with their audience. A systematic information modeling and management framework is necessary to capture this widely heterogeneous, schemaless, potentially humongous information produced by many different people. This book is an attempt to examine the modeling, storage, querying, and applications of such an event management system in a holistic manner. It uses a semantic-web style graph-based view of events, and shows how this event model, together with its query facility, can be used toward emerging applications like semi-automated storytelling.]]></description>
<dc:subject>events modeling semweb multimedia</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d9e995da8ee2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:events"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:multimedia"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://narrative.csail.mit.edu/ws12/">
    <title>CMN'12 Computational Models of Narrative</title>
    <dc:date>2011-07-13T20:12:28+00:00</dc:date>
    <link>http://narrative.csail.mit.edu/ws12/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Narratives are ubiquitous in human experience. We use them to communicate, convince, explain, and entertain. As far as we know, every society in the world has narratives, which suggests they are rooted in our psychology and serve an important cognitive function. It is becoming increasingly clear that, to truly understand and explain human intelligence, beliefs, and behaviors, we will have to understand why narrative is universal and explain (or explain away) the function it serves. The aim of this workshop series is to address key, fundamental questions about narrative, using computational techniques, so to advance our understanding of cognition, culture, and society.]]></description>
<dc:subject>narrative modeling workshop</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:46fc214b6923/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:narrative"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:workshop"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://people.csail.mit.edu/regina/6892/index.html">
    <title>6.892: Computational Models of Discourse</title>
    <dc:date>2011-06-28T20:30:43+00:00</dc:date>
    <link>http://people.csail.mit.edu/regina/6892/index.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This course is a graduate level introduction to automatic discourse processing. The emphasis will be on methods and models that have applicability to natural language and speech processing.

The class will cover the following topics: discourse structure, models of coherence and cohesion, plan recognition algorithms, and text segmentation. We will study symbolic as well as machine learning methods for discourse analysis. We will also discuss the use of these methods in a variety of applications ranging from dialogue systems to automatic essay writing.]]></description>
<dc:subject>discourse modeling nlp</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:bba5fbd75b77/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:discourse"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:nlp"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://jis.sagepub.com/content/37/3/332.abstract?etoc">
    <title>Modelling ancient Chinese time ontology</title>
    <dc:date>2011-06-10T22:22:45+00:00</dc:date>
    <link>http://jis.sagepub.com/content/37/3/332.abstract?etoc</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Temporal information is one of the essential components in many domains, especially those related to history. Up until the twentieth century, the Chinese used a lunisolar calendar with the title of an Emperor and a reign period to express temporal information. When describing a historical event in Chinese history, it is inadequate to use existing time ontologies as presented in the traditional Chinese way of thinking to capture and encode time. To date, no attention in the field has been given to modelling ancient Chinese time. In this paper, we identify the problems encountered when modelling Chinese time resulting from the distinctive nature of a non-western time scale. We design a new model of temporal information with combined approaches, which are more appropriate for Chinese dynasties, emperors, and reign periods, and apply the OWL-Time ontology onto the ancient Chinese lunisolar calendar. This approach can also be applied to other ancient time-keeping methods in non-western time scales.]]></description>
<dc:subject>modeling temporality periodization history digitalhumanities</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:86763a73f5c4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:temporality"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:periodization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://faculty.poly.edu/~onov/Nov_Living%20In%20a%20Bubble%20Toward%20a%20Unified%20Bubble%20Theory_2008_IJGS.pdf">
    <title>Living in a bubble? Toward a unified bubble theory</title>
    <dc:date>2011-04-26T15:53:29+00:00</dc:date>
    <link>http://faculty.poly.edu/~onov/Nov_Living%20In%20a%20Bubble%20Toward%20a%20Unified%20Bubble%20Theory_2008_IJGS.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[We generalise the notion of a bubble beyond the financial domain, by showing how a single social mechanism, based on an information feedback-loop, explains both financial bubbles and other seemingly disparate social phenomena, such as the recognition of academic articles, website popularity, and the spread of rumours.
We discuss examples of phenomena explained by this bubble mechanism, as well as other phenomena that exhibit certain bubble characteristics, yet are not bubbles according to our model. Finally, we present mathematical mechanisms for two phenomena that conform with our model, and show by computer simulation how they exhibit bubble behaviour.]]></description>
<dc:subject>economics history bibliometrics modeling websearch</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0cefe361f03f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:economics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bibliometrics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:websearch"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sourceforge.net/mailarchive/message.php?msg_name=4A72B1E1.5080201%40mondeca.com">
    <title>[Dbpedia-discussion] Inconsistency Feedback from DBpedia to Wikipedia</title>
    <dc:date>2009-08-01T00:14:17+00:00</dc:date>
    <link>http://sourceforge.net/mailarchive/message.php?msg_name=4A72B1E1.5080201%40mondeca.com</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA["As Bruno Bachimont uses to say, an ontology is mainly a tool to explicit inconsistencies of our knowledge, pointing to new questions for research. After that, you can throw it away."
]]></description>
<dc:subject>data ontology logic semantics semweb quote modeling research philosophy</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:f694afff2e06/</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:ontology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:logic"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semantics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:quote"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:philosophy"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://currents.cwrl.utexas.edu/Spring08/Liu">
    <title>Literature + | Currents In Electronic Literacy</title>
    <dc:date>2009-06-07T17:51:02+00:00</dc:date>
    <link>http://currents.cwrl.utexas.edu/Spring08/Liu</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Because of the recent, shared emphasis in many fields on digital methods, scholars in the humanities, arts, social sciences, and sciences increasingly need to collaborate across disciplines. This course reflects theoretically and practically on the new digitally facilitated interdisciplinarity by asking students to choose a literary work and treat it according to one or more of the research paradigms prevalent in other fields of study.
]]></description>
<dc:subject>humanities digitalhumanities syllabus interpretation modeling tools theory</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:ed23e44901e2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:humanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:syllabus"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interpretation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:theory"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/TR/2008/WD-owl2-new-features-20081202/#F12:_Punning">
    <title>OWL 2 Web Ontology Language:New Features and Rationale</title>
    <dc:date>2009-03-18T20:46:12+00:00</dc:date>
    <link>http://www.w3.org/TR/2008/WD-owl2-new-features-20081202/#F12:_Punning</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Class and ObjectProperty punning might be convenient for when one wants to model attributes of relations themselves.
]]></description>
<dc:subject>ontology owl time provenance modeling temporality</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:b96253747b42/</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:owl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:provenance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:temporality"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>