Are.na Makers
Want to add your project to the list? Connect your channel to the Are.na Makers channel.
I’m thinking about how to represent hierarchy/nesting in the distant future (to enable something like file system organization or nested tags).
Maybe to do this from a schema POV, all I need is an option for relation properties to “enforce hierarchy”, which if enabled, prevents you from selecting an item’s ancestor as one of its children.
And then in the interface, I think that would necessitate:
- the option to represent a class through nested elements
- in item selection for relation properties, the ability to display/select the options with a nested presentation of some sort
- this actually has logical implications as well, because selecting a child element would mean selecting its parent as well
Obviously would be a (fascinating) challenge to try to come up with a legible UI for all of this.
An interesting dilemma that’s occurring to me as I think through this is, would I want the hierarchy on a class to be applied from within a class, i.e. in one of its own properties? Or externally, as part of a relation property which selects from that class?
WELCOME TO THE PROCESS ARCHIVE ROOM, WHERE YOU CAN FIND ALL SORTS OF NONLINEAR NOTES AND DOCUMENTATION OF KÉLANIE’S CREATIVE PROCESS.








