Evaluate subclasses of HDO:Information for suitability to be IAO:InformationContentEntity
currently we have under HDO:Information:
- HDO:LicenseInformation
- HDO:ProvenanceInformation
- HDO:Specification
- HDO:DataFormat (ff)
- HDO:DataStructureSpecification (ff)
- HDO:DataType
- HDO:FAIR principles
- HDO:FileFormat
- HDO:PlanSpecification
- HDO:ProgrammingLanguage
- HDO:Schema
- HDO:StandardSpecification
- HDO:UnitInformation
and under IAO:InformationContentEntity:
- IAO:DirectiveInformationEntity
- IAO:ActionSpecification
- IAO:ObjectiveSpecification
- IAO:PlanSpecification
- HDO:Software (ff)
- OBI:SourceCodeModule
- IAO:NarrativeObject
- HDO:ProgramCode
This is to evaluate how IAO:InformationContentEntity and HDO:Information are different and which HDO classes under HDO:Information might be moved in the hierarchy under IAO:informationContentEntity
The way the labels read, they imply that IAO:InformationContentEntity is something that is actually written down (i.e. the document) while HDO:Information points to something like the content of a document. Looking at the definitions shows:
HDO:Information def A generically dependent continuant which realises an information role. IAO:informationContentEntity def A generically dependent continuant that is about some thing.
The current defintion of Information content entity is relatively loose. Being about something does not neccessarily mean that this entity is "informative" in the sense of the HDO:InformationRoleSense. Also the defintion of HDO:Information is generic enough to