search

the-human-colossus-foundation / oca-spec

Overlay Capture Architecture Specification
European Union Public License 1.2
7 stars 7 forks source link

Rename meta overlay to descriptive overlay #16

Open mitfik opened 1 year ago

mitfik commented 1 year ago

Requirement: Change the name of the overlay from "Meta overlay" to "Descriptive overlay" and add two types:

(i.) Descriptive (language-specific) overlay: for adding schema-level descriptive information that is language-specific.

(ii.) Descriptive (language-agnostic) overlay: for adding schema-level descriptive information that is language-agnostic.

This would allow use to stay consistent with the naming in oca ecosystem. Metadata is defined as "sets of data that provide meaning to any stored sequence of bytes."

Most overlays are treated as metadata and having meta overlay gets in conflict with naming.

RFC not needed.

pknowl commented 10 months ago

I suggest replacing the "Meta overlay" with a "Cataloguing Bundle" for handling catalogue records separately. This solution would separate cataloging information from the OCA schema, enabling updates to catalogue records without affecting the schema. Such separation would ensure the integrity of the OCA schema while offering flexibility for catalogue record edits. It would involve adding a "meta_record_digest" attribute to the OCA capture base for secure linkage, improving data management's flexibility, security, and efficiency. This method keeps the schema intact and offers a dedicated space for managing dynamic "metadata" records. It also simplifies authorization rights, allowing a repository guardian to focus solely on managing catalogue listings without having to get involved in managing the schema itself.

pknowl commented 6 months ago

I propose changing an attribute name in the current "Meta Overlay" from "name" to "title" for more granular accuracy and alignment with the current cataloging naming convention, which would free up the schema name (e.g., userProfile) as an asset reference where the SAID may be deemed inappropriate.

As we delve into more ecosystem use cases, evolving the OCA functionality to address cataloguing metadata will be helpful. It would involve adopting and refining overlay types that address the nuances of stored-asset documentation, discoverability, and usage guidelines.

Here's an overview of potential cataloguing overlays for future consideration:

Description Overlay: to describe a stored asset or resource, providing essential details like the title, description, language, version, and usage guidelines. This overlay type would serve as the primary entry point for understanding the purpose and scope of the asset/resource.

Citation Overlay: to correctly cite the stored asset or resource, including citation formats, attribution requirements, and any specific guidelines for academic or commercial use. This overlay type would ensure proper acknowledgment and consideration of intellectual property.

Tagging Overlay: to provide keywords, tags, and categories to enhance asset/resource discoverability and thematic classification. This overlay type would aid in indexing and searching for datasets across platforms and repositories.

Dataset Relationship Overlay: to define relationships with other assets/resources, such as derivation, complementarity, or equivalence. This overlay type would aid in understanding resource lineage, dependencies, and interoperability.

Usage Statistics Overlay: to provide metrics on dataset engagement, such as downloads, views, and citation counts. This overlay type would offer insights into the stored resources' impact and reach within the community.

Rating Overlay: to aggregate user feedback and ratings, offering a crowd-sourced assessment of the quality, usability, and relevance of a stored asset or resource. This overlay type would guide users in selecting the most valuable assets for their needs.

Licensing Overlay: to specify the legal terms under which the asset/resource is made available, including any restrictions or obligations for users. This overlay type would help navigate copyright and usage rights.

Dataset Provenance Overlay: to chronicle the history, source, and modifications of an asset/resource over time. This overlay type would ensure transparency and traceability, supporting data governance and integrity.

Multilingual Metadata Overlay: to facilitate resource metadata provision in multiple languages, promoting accessibility and inclusivity across linguistic boundaries.