-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Formal abstract data model definition #258
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I think we still want to do this. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Some of the most important work done by the group is the definition of the resource type and the implied data model. To facilitate even greater understanding and clarity and to provide an option to have different syntactic representations it is proposed to define the abstract data model.
This would allow mappings to be done to other representations, notably RDF, and semantic EGDM via EGCL.
The text was updated successfully, but these errors were encountered: