Context: This is the opening comment I made to a conversation at the GitHub repository for Schema.org where folks are considering a proposal or recommendation to "Add Exhibition as a subtype of Event".
We again thank the Museum Computer Network Association and PICTION for sponsoring our Emerging Professional scholarship that enabled Jim Salmons and Timlynn Babitsky to attend the conference on behalf of our projects to learn, network with Kindred Spirits, and make our presentation to the museum technology community. The opportunity to attend this excellent conference was phenomenal and will be a source of enthusiasm and inspiration for our continued evolution of our grassroots Citizen Science/History projects.
We invite you to view the "Lively Talkin' Slide" Edition of our recent presentation about FactMiners and The Softalk Apple Project at #MCN2014, the premiere museum informatics conference. We again thank the Museum Computer Network Association and PICTION for sponsoring our Emerging Professional scholarship that enabled Jim Salmons and Timlynn Babitsky to attend the conference to learn, network with Kindred Spirits, and make our presentation to the museum informatics community. The opportunity for growth of both our projects was phenomenal and will be a source of enthusiasm for our continued evolution of these grassroots Citizen Science/History projects.
I am using the CIDOC-CRM – the Conceptual Reference Model developed by the International Council of Museums – as the primary domain reference model guiding design and development of the FactMiners social-game platform. In a recent post I looked at the Conceptual Reference Model from a "pure graph" perspective, re-imagining the CRM's Property Declarations as "just another" labeled subset of model elements, that is, as just another important subset of CRM Classes. In this post, I explore the "entity-ness" of the CIDOC-CRM Class Declarations.
One aspect of the metamodel subgraph design pattern we are using for the FactMiners Fact Cloud is a graph transformation that can be viewed as "node-ifying" a relationship. That is, if our source database has a relationship, we model the relationship as a node in the metamodel so we can more fully model the relationship. In this post I explore an aspect of the UI view of such an approach and wonder if Structr and KeyLines could be used to create an intuitive and easy-to-use visualization of such a dynamic graph transformation at the view level. My particular interest here is use this design pattern to create a Neo4j-based exploratory viewer on the CIDOC-CRM.
FactMiners.org is very pleased to announce that we are adopting METS/ALTO as the "drill down" metadata and file/data format specifications that will guide our DSL (Domain Specific Language) extensions of the CIDOC-CRM as part of the design of the Open Source FactMiners LAM-based social-game platform.