Free up "capture" in favor of "collection"

[mitfik]

REF https://oca.colossi.network/specification/#basic-concepts

Requirement: In the "Basic concepts" section of the OCA spec, change "Capture" to "Collection" and tweak the associated diagram to reflect that change.

Suggested prose (ref):

"Collection

Data collection is the process of gathering information in a meaningful and reliable manner.

Data collection MAY involve Semantic, Inputs, and Presentation Overlays."

This suggested tweak frees up the word "capture" so it can be used to describe metadata capture for any computing process, including data collection, validation, transformation, and presentation.

[pknowl]

The terms "collection" and "capture" are quite different. The terms are often ill-defined and, therefore, often misunderstood and ultimately misused. So, what is the difference? In computer science, (i.) "collection" refers to "data collection", the process of gathering accurate data from various sources; and (ii.) "capture" refers to "metadata capture", an essential process for the digital preservation of anything objectual, which in computer science can be a variable, a data structure, a function, or a method. These terms often get muddled up. I have also been guilty of convoluting "collection" and "capture" in the past. Anyway, I thought that I would share this acquired knowledge.

In terms of OCA, the architecture is for capturing metadata. As the "decentralised semantics" space starts to mature, I envisage that OCA will naturally evolve to capture all task-specific metadata for "collection", "validation", "transformation", and "presentation" processes.