search

emmo-repo / EMMO

Elementary Multiperspective Material Ontology (EMMO)
Other
61 stars 16 forks source link

Updated computer science #255

Closed jesper-friis closed 6 months ago

jesper-friis commented 8 months ago

Updated computer science based on the categorisation on https://en.wikipedia.org/wiki/Computer_language

Added elucidations and other annotations.

NOTE: This PR builds on top of PR https://github.com/emmo-repo/EMMO/pull/254. Either merge that PR first or only consider the changes in disciplines/computerscience.ttl.

hothello commented 8 months ago

A bunch of random comments.

  1. In the openmodel ontology for D5.5, I have added the class Filename, which is a subclass of URL and the union of Root and Extension. I used these classes to break down the ResourceDescription into their constituents.
  2. Given point 1, the class File could have an additional restriction: hasURL exactly 1 Filename.
  3. Would it make sense to make ResourceDescriptionalso a subclass of String? In this way, we make it a SymbolicConstruct. Currently, only the class Path is a subclass of String.
  4. The class Filecontains only a subclass LanguageInterpretableFile. I would also add BinaryFile.
  5. I like very much the classification of ComputerSystem.
jesper-friis commented 8 months ago

Thanks a lot Otello. Some quick comments:

  1. How established are the terminology Root and Extension? Python pathlib uses the terms: name, suffix and stem. Are these more established terms? Possible altLabels?

  2. What about hard and symbolic links? They allow associating several filenames to a file. I think it is better to change the relation to hasURL some Filename.

  3. Good question. But must all resource descriptions really be strings? In OTEAPI we use Python dicts. Transferred between memory and CPU they are just data.

  4. Agree

  5. Thanks :-)