authored_by As an example, consider the assertion that "Variant X causes Disease Y". At an abstract level this represents a bfo: information content entity (or frbr:Work). This abstract assertion can be concretized / encoded various formats - e.g. a free-text sentence, an rdf graph, a blob of json, or stanza of XML. Each such manifestation might use a different model or structure to represent this knowledge. Each such concrete form is considered a separate resource/digital artifact at the 'manifestation' level, but each expresses the same knowledge. The authored_by and date_authored properties allow us connect an abstract or concrete representation of this assertion to who and when the knowledge was originally generated. This will be the same agent and date for all formats/manifestations listed above. The created_by and date_created properties allow us to connect a representation of the abstract or concrete assertion to who and when the specific manifestation was created in a particular format. The agent/dates here will be different for each of the formats/manifestations listed above. A relation between an information content entity (or concrete manifestation of it as a particular resource/digital artifact), and the agent that originally generated the information content. Older note - remove before releasing: We intentionally avoid use of a more generic "creator" property here, as this term is used in established standards such as PAV and DC to specifically describe agents who generated a specific representation of an information content entity. For example, the pav:createdBy property is used specifically to describe agents contributing to a specific representation. SEPIO, by contrast, aims to describe the agent(s) responsible for generating the abstract information content these concretized artifacts express. For this reason, SEPIO creates the more specific "stated_by" relation to explicitly distinguish the act of making a statement (generating its information content) from the act of creating a specific digital representation of the statement (generating a particular concretized artifact). A explicit commitment to this more abstracted level of representation is a core feature of the SEPIO model, and has implications for how instances in the data are described, identified, and distinguished in practice. In the case that the information artifact is an assertion, the responsible agent is the one who originally generated an assertion based on their evaluation of relevant evidence. If more than one agent is involved in this process, we may consider them collectively as a group or organization representing a single agent. has_contributor