WHAT DO YOU RECOMMEND?
hierarchically classified and semantically versioned object and attribute definitions which may be consumed by all / authored by (one,many,all)
I listed this here in my original post, but reposting as I think it’s gotten lost.
I think it makes sense to have a way of allowing the community to emit / curate / (collaborate / depend on )
a hierarchically arranged, classified, namespaced set of objects/attributes … the taxonomical hierarchy of objects and attributes…
HOW COULD IT BE DONE?
My earlier post has some initial ideas, but I envision a way of users, orgs, authoring object constructs and releasing them in a testable, versioned fashion via the any ecosystem.
I see this as both toil reduction (why should everyone recreate their own thing constructs?)
and an upside to collaboration as it allows one’s set of spaces to depend on resource definitions in a structured manner
For example if I define a server construct… that has several resources, each with sub-objects, and attributes
and someone else defines a server construct… the term gets overloaded our spaces are likely to be incompatible.
having a way to share the constructs that I crafted in an elegant, dependable, versioned fashion allows the community to iterate on existing primitives and expand them rather than reinventing their own.
REAL WORLD USE CASES
- Organizations emitting virtual objects which resemble their real-world counterparts so users can adopt them into their spaces.
- Teams will have easier times building up workflows/representations of their things, as a cornucopia of community-minted resources can be ingested
- Creators can craft fancy things and get some form of benefit for reducing the toil of others
- Increased consistency of terminology, relations, and object hierarchy will likely benefit everyone
RECOMMENDED ALTERNATIVES
¯\_(ツ)_/¯
ADDITIONAL CONTEXT
I looked to see if this has gained any traction, but either I’m blind, or it musta gotten lost in the stack of better ideas 