18 Matching Annotations
  1. Apr 2017
    1. "position: relative"

      position: relative = peripheral position: absolute = central

    2. position: absolute

      position: absolute = at the center position: relative = at the periphery

    1. abstract class

      Abstract classes may not be instantiated, and require subclasses to provide implementations for the abstract methods. (Google: "what is an abstract class")

  2. Dec 2016
    1. createFactory

      The HTML object creator--the object being separate and secondary, supplementary, from this as what is happening is happening qua propagation in media res.

    2. To align our terminology we now use the term ReactElement instead of descriptor. Likewise, we use the term ReactNode instead of renderable.

      FASCINATING language change! From description and rendering (pumping heart) to elements and nodes (grey matter)...Wittgenstein would say the game is dying, Foucault the discourse being born, Derrida wouldn't know what to say first, Deleuze would have a field day. Deleuze wins.

    1. You use literals to represent values in JavaScript. These are fixed values, not variables, that you literally provide in your script.

      Literals are fixed values hard-coded in.

    1. Conceptually, components are like JavaScript functions. They accept arbitrary inputs (called "props") and return React elements describing what should appear on the screen.

      Components are JS doing rendering.

      For a given component: I = props (arbitrary inputs) O = elements (describe view)

      So a view on a screen is associated with components or haecceities, What's Happening, rather than with a background-environment Document, or Object, or Model, or quid-whatness-or-THING (person subj or substance) abut which they occur. D&G would have a field day over React. See also "Thinking in React."

    1. latitude Number  or Text The latitude of a location. For example 37.42242 (WGS 84). longitude Number  or Text The longitude of a location. For example -122.08585 (WGS 84).
  3. Oct 2016
    1. commenting Instance The motivation for when the user intends to comment about the Target. For example to provide a commentary about a particular PDF document.

      Do translations count as comments? The "Melanie" example further along in this document - "Melanie wants to associate a comment that she wrote in English within the annotation or a external mp3 of the same content in German by someone else" - is motivated by "commenting." Ok, Melanie could be commenting in another language; single conversations can flow between multiple languages. But let's say Melanie is translating the German into English. To call this commenting doesn't give us the whole picture. Melanie is both commenting in a general sense and doing something much more formal and specific to language itself. Let's say someone else, person #2, trying to figure out what the German Melanie has commented on means in English, reads Melanie's annotation. Let's say person #2 doesn't recognize the English Melanie has used. If Melanie's annotation isn't identified as a translation, if it's only motivated by commenting (and let's say this means it gets displayed like any other comment, or like any other description for that matter, as "describing" also comes up as motivation in the Melanie example), person #2 would have no idea that Melanie is in fact providing exactly the information person #2 is seeking. Melanie's real motivation, not just to comment but to translate, would be lost.

    2. describing Instance The motivation for when the user intends to describe the Target, as opposed to (for example) a comment about it.

      Do translations count as descriptions? Perhaps the closest analogue in the Motivations list to "translating" is "describing." I'm inclined to say it'd be misleading to treat translations as descriptions, however, even while it'd not be misleading to treat definitions as descriptions. While describing a term's contents is certainly necessary in translating a term, and perhaps even sufficient in defining one, "describing" isn't sufficient to account for what translation accomplishes - a term is translated from language A to language B when its contents are (1) described (2) in language B.

    3. Motivations

      What about "translating" - the motivation when a user intends to associate for the purpose of establishing equivalence a particular set of words in one language with a particular set in another one?

    4. classifying Instance The motivation for when the user intends to classify the Target as something. For example to classify an image as a portrait.

      Do translations count as classifications? On the one hand translation entails de dicto "classifying" - a cat, e.g., es un gato, est un chat, etc., in a matter of speaking. On the other hand, translation is not mereology - "gato" and "chat" are not de re instances of the class "cat." A chat is not what a cat is "about."

    5. By starting with the first Annotation in the first Page, and traversing the Pages to the last Annotation of the last Page, all Annotations in the Collection will have been discovered.

      I'm confused why linear traversal is a good thing. It strikes me as more intuitive to traverse a subset of annotations in a collection that all have to do with the same thing, rather than go through all the annotations in the collection, for any particular purpose. Plus, the more annotations, the quicker a non-linear lookup method becomes than a linear one - to the point where I wonder, isn't there a limit to which ordering annotations in a collection is viable? Put it another way, what are collections intended to do such that my previous concern is a non-issue?

    6. always ordered

      Why order annotations?