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 an offline meeting with @lzehl and @aeidi89, we concluded that our existing CommonCoordinateSpace(Version) (CoCS(V)) don't work well based on feedback from others using the schemas and to some degree also in relation to AtOM.
High-level summary: CoCS will be changed into CommonCoordinateFramework. The properties of CoCSV will be split into CommonCoordinateFrameworkVersion and a CommonCoordinateSpace schema. The latter will not be versioned anymore.
@aeidi89 and I are working on a first draft for the changes and should be discussed/reviewed by the @openMetadataInitiative/openminds-admins and @openMetadataInitiative/openminds-developer (and other such as e.g., @xgui3783) when ready.
Please note that these changes will affect multiple other openMINDS models. Details are still unknown, but I will prepare an overview of the affected schemas/properties so that we can discuss the consequences and required changes to corresponding schemas.
The text was updated successfully, but these errors were encountered:
In an offline meeting with @lzehl and @aeidi89, we concluded that our existing CommonCoordinateSpace(Version) (CoCS(V)) don't work well based on feedback from others using the schemas and to some degree also in relation to AtOM.
High-level summary: CoCS will be changed into CommonCoordinateFramework. The properties of CoCSV will be split into CommonCoordinateFrameworkVersion and a CommonCoordinateSpace schema. The latter will not be versioned anymore.
@aeidi89 and I are working on a first draft for the changes and should be discussed/reviewed by the @openMetadataInitiative/openminds-admins and @openMetadataInitiative/openminds-developer (and other such as e.g., @xgui3783) when ready.
Please note that these changes will affect multiple other openMINDS models. Details are still unknown, but I will prepare an overview of the affected schemas/properties so that we can discuss the consequences and required changes to corresponding schemas.
The text was updated successfully, but these errors were encountered: