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
For the overall structure of the repository I would suggest the following:
General approach: from generic / common terms to specific (collecting most generic terms in a kind of "top-level vocabulary") - each term should be defined, if possible, only once, and as broad as possible:
We should discuss with @nmoust . - I proposed to him some guidelines how to model (in private). For example we should use broader/narrower for is_a relation put not for part_of. part_of is collection territory.
@markdoerr - #48 is the result of what @nmoust and I had worked on internally. We propose few top level concepts and give some reasons for the proposed structure.
Description
For the overall structure of the repository I would suggest the following:
General approach: from generic / common terms to specific (collecting most generic terms in a kind of "top-level vocabulary") - each term should be defined, if possible, only once, and as broad as possible:
(I will create the corresponding sections in the config file)
The text was updated successfully, but these errors were encountered: