The ACT database will store pertinent information about the ACT community. Online users can query the database with a search box and the results will be formatted for readability. Developers can query the database with an API to gather insights about the ACT community.
Like a wiki, the editing of the data is crowd-sourced to all users. Unlike a wiki, the users do not directly edit pages – instead, they edit the data in the database, which can then be queried and displayed. In the future, the scope may expand to include more expository content on the developing applications of category theory, to help the community connect to other domains.
The database will be structured to provide users with pertinent information regarding the people, activities, trends, goals and endeavors of the ACT community. When creating an account, most fields will be optional. Contributors have the ability to propose and create new types, attributes, and forms of metadata.
Activity is organized by scope and generality: works, which may contribute to projects, which may contribute to programs. These can be tagged with topics and categorized under domains.
make a work —> link to project —> link to program
these links are not just boolean claims, but a justification
Work.Publication :
Past and present roles, both formal and informal.
Since these are subjective, each claim that someone has a certain skill or knowledge will be tagged with the list of users who made the claim.
There are many ways to interact with a person: propose collaboration, solicit a service (“teach me Python”), offer a service (“I can translate your ideas into a form that systems engineers will understand.”), casual conversation, etc. Which of these forms of interaction do you accept? Which do you seek?