Repository navigation
Ontology Mapping storage: one page per ontology or per Schema+ontology? #1065
JeroenDeDauw
started this conversation in
General
Replies: 2 comments
|
I investigated how big a single Mapping:CIDOC (with mappings for all Schemas for a typical CH wiki) would get. The example Fable came up with is 44 KB / ~1,300 lines. That is well within what can be managed in a single wiki page. My take remains to change our implementation to one page per ontology. Any additional reasons not to do that? Btw the current implementation is there because Fable thought that to be the better approach. After having read this thread it changed it's mind and "now at a weak lean toward one page per ontology". |
0 replies
|
PR to change to "one page per ontology": |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The options
Mapping:PersonToEDM,Mapping:CityToEDM,Mapping:PersonToCidocCRM, ...Mapping:EDMcontaining entries for every mapped Schema.The current prototype on NeoWiki master uses the first approach. I'm personally leaning towards updating our implementation to the second approach. Which approach do you think is best, and why?
Pros of per Schema+ontology
Mapping:PersonToEDMin your wiki and want to import additional "standard ECHOLOT mappings to EDM", you could do so by importing pages likeMapping:CityToEDM. MediaWiki import works with pages. You would simply be importing those new pages, rather than needing to merge into an existing page, as would be the case with the one page per ontology approach, which would just haveMapping:EDM.The current prototype on NeoWiki master uses
Mapping:PersonToEDM-style names. Open question if we should change those toMapping:EDM/Person, using MediaWiki sub-pages.Pros of one page per ontology
Product questions
All reactions