You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our current schema, project media (e.g., photos, videos, and other marketing materials) is integrated alongside anchored project metadata. However, project media differs significantly in both usage and accessibility:
Anchored Project Metadata: This includes information that is publicly available, meant for other platforms to query, consume, and integrate into their applications. Anchored metadata informs about key project details and serves as an authoritative data source.
Project Media: These include assets like photos and videos, which are typically intended for marketing or communication purposes. While important, these media files:
Do not necessarily contribute to the core project metadata.
May be privately hosted.
Do not always need to be anchored or publicly available for querying.
Goal
To avoid mixing project media with core anchored metadata, we propose creating a separate schema specifically for project media. This will ensure that project media is treated appropriately, whether it's privately hosted or has limited public relevance.
By doing this, we maintain a clear separation between:
Anchored, public-facing metadata that informs about the project.
Optional, potentially private media files that are more aligned with project presentation or marketing needs.
The text was updated successfully, but these errors were encountered:
Context
In our current schema, project media (e.g., photos, videos, and other marketing materials) is integrated alongside anchored project metadata. However, project media differs significantly in both usage and accessibility:
Goal
To avoid mixing project media with core anchored metadata, we propose creating a separate schema specifically for project media. This will ensure that project media is treated appropriately, whether it's privately hosted or has limited public relevance.
By doing this, we maintain a clear separation between:
The text was updated successfully, but these errors were encountered: