This is the second post I am making on Steemit related to the planning and development of BlockOrg. There will likely be several of these in the near future. If you are interested in getting involved in the project, let me know!
BlockOrg is intended to be an organizational and communication tool. As such, it is useful for blocks to be able to hold many different types of entries. Below I have listed a number of types of entries that I would like to see the finished product handle.
What other types of entries do you think would be useful?
Archival is just a generic phrase to say that we are storing data for historical purposes or later use. This can apply to governing documents, the minutes of a meeting, data related to event planning, official correspondence, or pretty much anything.
A DataBlock would be similar to an Archival Entry except that it is being stored for use by a specific application. It will be a JSON object that holds data formatted for the application that stored it.
These will be documents or commentary posted specifically for the purpose of getting people to respond. They will be identified in such a way that responses can be linked back to the original document.
These will be posts that are looking for a vote, either a straight up/down (yes/no) or giving a list of options to choose from. Polls can be flagged as Public or Members Only (Better term needed). This will determine if everyone with access can vote on the topic, or just those who are voting members of the organization.
Similar to Polls except that they will deal more directly with the governance of the organization. Resolutions are only open to response from voting members.
While this may seem obvious, a vote would be associated with a Resolution or a Poll, or perhaps another entry type that we haven't thought of yet. Votes will of course require a link back to the Poll or Resolution that they are associated with.
Messages sent from one user to another via the blockchain. While this is technically a category of Archival entries, code can be generated to get a user’s attention if a message is addressed specifically to them.
Hashes are long, random, and hard to remember. Those who wish to do so should be able to register an alias that the system will then link to the Public Key that is the user’s individual address.
A document representing an agreement between one or more person’s. The document will lay out the terms of the contract, who is bound by the contract, as well as whether the agreement is all or nothing (i.e. whether or not the contract is null and void if one person disagrees). A contract involving only two entities is automatically all or nothing. Ledger entries will then be made by each participant stating agreement or dissent.
Tags are like aliases for a specific ledger entry.
