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
@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.
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.
The "orphan" ontology is required to make any other ontology working. In
UML, several model have used types that were not defined in their model.
To make the UML model complete, these types have been defined in an
orphan package since they are not part of any other ISO/TC 211 package.
Once the cleanup of the Harmonized Model will be completed maybe this
package will be not relevant in the future except if old ontology
versions are made available.
Le 2019-08-15 à 01:00, Knut Jetlund a écrit :
I will let @BrodeurJS <https://github.com/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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1?email_source=notifications&email_token=AB2YVY6HS4747QXTNSWGENLQETPHZA5CNFSM4IL2JXS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4K22ZA#issuecomment-521514340>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB2YVY67ZQKUBJNTTCKPWATQETPHZANCNFSM4IL2JXSQ>.
@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)
The text was updated successfully, but these errors were encountered: