Standardised common traits would allow for third party apps to better access and visualise an agents data (DNA-instances/zomes/entries) but also to interact with the data in a meaningful way. It would also faciltate better interopability between apps as well as speed up development.
Topic for discussion: What possible standard traits are there and how could we get a process going where we develop a few of these?
Working doc: https://hackmd.io/QSVLhFcVRsmkeuhEAOIcfw?both
List which other standard traits (and possibly trait versions) a zome uses. Or Rust possibly provides that functionality already? But the information has to be accessible not only for the app developer but for third party apps calling zome functions.
The notion of “ownership” over a digital resource is a basic pattern many Holochain applications will need. With ownership comes the user expectance of being able to transfer that ownership, to renounce ownership, etc.
A common way to manage ownership would faciltate better interopability between apps as well as speed up development.
Doc for collaboration here: https://hackmd.io/kWfnGNR4Ta-K1h0jpK71Hw?both
Both zome level fields and entry level fields. Standard info found in zome.json (
zome_description, …) as well as zome/app specific.
Renders a human readable preview of an entry or list of entries, possibly in the form of a webcomponent. Example: embed a nice looking representation of a chat entry in a humm blog post @nickmitchell?
Returns a plugin editor that can be embedded in other apps. Example: Every Humm blog post embeds a “Comments Editor” from the “HoloComments” app allowing for users to comment posts.