24 Matching Annotations
  1. Jan 2024
    1. Hierarchy is about relationships between things. The most common hierarchical relationships are items that have a parent/child relationship.
    1. This is true for other tasks besides design — frontend implementation, backend implementation, QA, etc — would we create unique types for each? Our suggestion here to teams today is often to break down the work into issues, or now tasks, for each uniquely assignable/trackable piece of work. You could do the same for design, where the task or issue is used to track status, discuss progress and maybe even WIP, but is focused on being SSOT for status rather than design.
  2. Mar 2023
    1. 9/8b2 "Multiple storage" als Notwendigkeit derSpeicherung von komplexen (komplex auszu-wertenden) Informationen.

      Seems like from a historical perspective hierarchical databases were more prevalent in the 1960s and relational databases didn't exist until the 1970s. (check references for this historically)

      Of course one must consider that within a card index or zettelkasten the ideas of both could have co-existed in essence even if they weren't named as such. Some of the business use cases as early as 1903 (earlier?) would have shown the idea of multiple storage and relational database usage. Beatrice Webb's usage of her notes in a database-like way may have indicated this as well.

  3. Jan 2023
  4. Nov 2022
    1. v5: added git and github (thanks @ceejbot), and RSS (thanks @zem42). Taking suggestions for hierarchical/distributed and hierarchical/decentralized.

      t Laurie Voss's crowdsourced set of examples of things that have structure & control in the form of the following: - centralized - hierarchical - federated - distributed - decentralized

      Picture below: Link to tweet: https://twitter.com/seldo/status/1486563446099300359?s=20&t=C6z9xUF_YBkOFmfcjfjpUA

  5. Sep 2022
    1. It is often the case that a group or "tree" of documents has been constructed to serve a common purpose, wherein the vast majority of URI references in these documents point to resources within the tree rather than outside it. Similarly, documents located at a particular site are much more likely to refer to other resources at that site than to resources at remote sites. Relative referencing of URIs allows document trees to be partially independent of their location and access scheme.
  6. Jul 2021
  7. Jun 2021
  8. Mar 2021
    1. In a broader sense, taxonomy also applies to relationship schemes other than parent-child hierarchies, such as network structures. Taxonomies may then include a single child with multi-parents, for example, "Car" might appear with both parents "Vehicle" and "Steel Mechanisms"
  9. Nov 2020
    1. Interaction with stable storage in the modern world isgenerally mediated by systems that fall roughly into oneof two categories: a filesystem or a database. Databasesassume as much as they can about the structure of thedata they store. The type of any given piece of datais known (e.g., an integer, an identifier, text, etc.), andthe relationships between data are well defined. Thedatabase is the all-knowing and exclusive arbiter of ac-cess to data.Unfortunately, if the user of the data wants more di-rect control over the data, a database is ill-suited. At thesame time, it is unwieldy to interact directly with stablestorage, so something light-weight in between a databaseand raw storage is needed. Filesystems have traditionallyplayed this role. They present a simple container abstrac-tion for data (a file) that is opaque to the system, and theyallow a simple organizational structure for those contain-ers (a hierarchical directory structure)

      Databases and filesystems are both systems which mediate the interaction between user and stable storage.

      Often, the implicit aim of a database is to capture as much as they can about the structure of the data they store. The database is the all-knowing and exclusive arbiter of access to data.

      If a user wants direct access to the data, a database isn't the right choice, but interacting directly with stable storage is too involved.

      A Filesystem is a lightweight (container) abstraction in between a database and raw storage. Filesystems are opaque to the system (i.e. visible only to the user) and allow for a simple, hierarchical organizational structure of directories.

    1. The standard cascade rules also apply to the CSS Variables.So, if a custom property is declared multiple times, the lowermost definition in the css file overwrites the ones above it.
  10. Sep 2020
  11. Jun 2020
  12. May 2020
  13. Apr 2020
  14. Mar 2020
  15. Feb 2014
    1. The real heart of the matter of selection, however, goes deeper than a lag in the adoption of mechanisms by libraries, or a lack of development of devices for their use. Our ineptitude in getting at the record is largely caused by the artificiality of systems of indexing. When data of any sort are placed in storage, they are filed alphabetically or numerically, and information is found (when it is) by tracing it down from subclass to subclass. It can be in only one place, unless duplicates are used; one has to have rules as to which path will locate it, and the rules are cumbersome. Having found one item, moreover, one has to emerge from the system and re-enter on a new path. The human mind does not work that way. It operates by association. With one item in its grasp, it snaps instantly to the next that is suggested by the association of thoughts, in accordance with some intricate web of trails carried by the cells of the brain. It has other characteristics, of course; trails that are not frequently followed are prone to fade, items are not fully permanent, memory is transitory. Yet the speed of action, the intricacy of trails, the detail of mental pictures, is awe-inspiring beyond all else in nature.

      With the advent of Google Docs we're finally moving away from the archaic indexing mentioned here. The filesystem metaphor was simple and dominated how everyone manages their data-- which extended into how we developed web content, as well.

      The declaration that Hierarchical File Systems are Dead has led to better systems of tagging and search, but we're still far from where we need to be since there is still a heavy focus on the document as a whole instead of also the content within the document.

      The linearity of printed books is even more treacherously entrenched in our minds than the classification systems used by libraries to store those books.

      One day maybe we'll liberate every piece of content from every layer of its concentric cages: artificial systems of indexing, books, web pages, paragraphs, even sentences and words themselves. Only then will we be able to re-dress those thoughts automatically into those familiar and comforting forms that keep our thoughts caged.