Skip to content
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

Purpose of the "orphans" directory #1

Open
ronaldtse opened this issue Aug 15, 2019 · 2 comments
Open

Purpose of the "orphans" directory #1

ronaldtse opened this issue Aug 15, 2019 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@ronaldtse
Copy link
Contributor

@BrodeurJS we have a question on what the "orphans" directory (link) is used for.

  • It seems like it contains files (appropriate to its name) not belonging to any particular ontology.

  • Is that resource temporary, or it’s expected to be existing normally?

If it’s inevitable, can we rearrange the data so that “orphans” is not located among ontologies? It would allow for a more elegant solution if directory contents were homogenous & we could treat each subdirectory as an ontology, with ontology ID as subdirectory name.

Thanks!

Originally from: ISO-TC211/jekyll-theme-isotc211#6 (comment)

@jetgeo
Copy link

jetgeo commented Aug 15, 2019

I will let @BrodeurJS decide this, just a few comments about the origin of the directory. The «Orphans» directory is derived from the package with the same name in the Harmonized UML model. The elements in that package were put there during a cleanup of the model. They do not belong to any standard, but they may have been used in some models. They will hopefully be removed from the HM after a new cleanup.

@BrodeurJS
Copy link
Contributor

BrodeurJS commented Aug 16, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants