@J-Oliveros and I have both done some work on developing schemas for the major entity types in the GeoKB. These are challenging in that the schemas are very much in flux, but I need to nail down an iterative approach to building them as part of each entity we are addressing. I'll couple this with the work in #19 rework the main page where I want to be linking to the schema for each entity as I document it.
Along with this, I need to look again at the property constraint aspect of the Wikibase architecture and schema validation techniques. Functionally, I want to do something similar to how Wikidata operates in that we have a visual clue in the UI when a schema deviation has occurred. I also want to start constraining the type ahead functionality for Item-type properties so that the system is looking for the right pool of resources as objects. I don't know how to do this yet with the entity schema structure.
@J-Oliveros and I have both done some work on developing schemas for the major entity types in the GeoKB. These are challenging in that the schemas are very much in flux, but I need to nail down an iterative approach to building them as part of each entity we are addressing. I'll couple this with the work in #19 rework the main page where I want to be linking to the schema for each entity as I document it.
Along with this, I need to look again at the property constraint aspect of the Wikibase architecture and schema validation techniques. Functionally, I want to do something similar to how Wikidata operates in that we have a visual clue in the UI when a schema deviation has occurred. I also want to start constraining the type ahead functionality for Item-type properties so that the system is looking for the right pool of resources as objects. I don't know how to do this yet with the entity schema structure.