<h1 id="relator">Relator<a aria-hidden="true" class="anchor-heading icon-link" href="#relator"></a></h1>
<ul>
<li>aka: <a href="/wiki/notes/o99h4umwihpwctxh1uwle9u#relationship-to-entity-conversion-rec">Relationship to Entity Conversion</a></li>
</ul>
<h2 id="features">Features<a aria-hidden="true" class="anchor-heading icon-link" href="#features"></a></h2>
<ul>
<li>allows all n-ary relationships
<ul>
<li>even so-called unary relationships like "Dave walked" can be expressed, e.g.</li>
</ul>
</li>
</ul>
<pre class="language-turtle"><code class="language-turtle">:dave-walking a :walking-relationship;
 :walker :dave;
 :tense :past-tense

</code></pre>
<h2 id="issues">Issues<a aria-hidden="true" class="anchor-heading icon-link" href="#issues"></a></h2>
<ul>
<li>"If modelling relationships as classes is useful, then why not use this pattern for all non-trivial relationships in a model? The main reason is that it causes explosion in the number of terms in a vocabulary, e.g. each predicate is replaced with two predicates and a class. A vocabulary can quickly become unwieldy, so the value of the extra modelling structure needs to be justified with clear requirements for needing the extra complexity. As described here, the primary reason is to qualify the relation." </li>
</ul>
<h2 id="implementations">Implementations<a aria-hidden="true" class="anchor-heading icon-link" href="#implementations"></a></h2>
<ul>
<li><a href="https://bioportal.bioontology.org/ontologies/GFO?p=classes&#x26;conceptid=gfo%3ARelator">https://bioportal.bioontology.org/ontologies/GFO?p=classes&#x26;conceptid=gfo%3ARelator</a></li>
<li><a href="https://nemo-ufes.github.io/gufo/#Relator">https://nemo-ufes.github.io/gufo/#Relator</a></li>
<li><a href="https://patterns.dataincubator.org/book/qualified-relation.html">https://patterns.dataincubator.org/book/qualified-relation.html</a></li>
</ul>
<h2 id="references">References<a aria-hidden="true" class="anchor-heading icon-link" href="#references"></a></h2>
<ul>
<li><a href="https://ontouml.readthedocs.io/en/latest/classes/sortals/relator/index.html">https://ontouml.readthedocs.io/en/latest/classes/sortals/relator/index.html</a></li>
</ul>
<hr>
Backlinks
<ul>
<li><a href="/wiki/notes/JKp6mo9ZIuJMvvZQzSLcR">Beware the Relationship as Graph Edge</a></li>
</ul>

Relator

public-notes


Welcome! And beware!  

## Purpose

This vault is the "[[learning-in-public|ar.swyx.learn-in-public]]" part of my Second Brain. If you share some of my interests, please [reach out](https://djradon.github.io)! 

## Contents

- [[t]] my personal wikipedia
- [[idea]] (not necessarily mine)
- Resource Notes, including highlights, thoughts and metadata, for various things:
  - [[ar]] mostly articles, papers and web pages
  - [[book]]
  - [[community]]
  - [[course]]
  - [[event]]
  - [[game]]
  - [[loc]]
  - [[org]]
  - [[user]] 
  - [[prdct]] mostly software products, but also ontologies
  - [[recipe]]
  - [[video]] movies, tv episodes, youtube, etc
- [[vs]]
- [[wanted]]
- Some "Metadata Notes":
  - [[tags]] which may refer to any and multiple (or none) of the above
  - [[c]]: ways to categorize resources
  - [[p]]: ways to assert things about resources (mostly abandoned)

In terms of the [[t.km.zettelkasten]] method, this wiki is a commingling of literature notes with something @Sönke-Ahrens warned about: a "personal Wikipedia or a database" [^1]. 

In terms of [[t.tm.getting-things-done]], it's references, someday-maybe, next actions, and public projects.

## Beware!

This is a cluttered cupboard of jumbled jottings riddled with inaccuracies, confusion, and mistakes.

## What This Is Not

- evergreen-notes/digital-garden: for "synthesized" / original-ish publishable big-idea notes that should evolve over time, props to @andy-matuschak and @maggie-appleton
- blog: for "point-in-time" items to be shared: personal news, articles, etc.
  - e.g., [[ar.substack.carpe-noctem]]


[^1]: [[book.how-to-take-smart-notes]]  