Skip to content

Results of validating ECFO using OOPS and FOOPS #15

@inaja

Description

@inaja
OOPS
1.1. Important:
1.1.1. Missing disjointness
1.1.2. Missing domain or range: ecfo#hasApplicableLocation and 1 dc property (publisher), 2 qudt properties (abbreviation and value), and 1 schema (molecularFormula)
1.2. Minor
1.2.1. Unconnected elements: prov:Activity, prov:Entity, foaf:Organization, skos:Concept
1.2.2. Missing annotations: foaf:Organization
1.2.3. Missing explicit declaration of inverse relationshipts: 13 cases, 7 are peco: hasTag, hasEmissionTarget, hasScope, hasTargetUnit, hasApplicableLocation, hasSoutceUnit, hasApplicablePeriod, and hasEmissionSource. The rest are dc, time, and prov relationships.
1.2.4.URI contains file extension
FOOPS
2.1. Findable:
2.1.1.  Ontology in metadata registry: Ontology not found in a public registry
2.2. Accessible
2.2.1: FIND_3_BIS: Ontology not found in a public registry (would be solved along witl 2.1.1)
2.3. Interoperable: all good
2.4. Reusable:
2.4.1 Missing recommended metadata: citation and contributor.
2.4.2. Missing detailed metadata: doi, publisher, logo, status, source, issued, backwards compatibility
2.4.3. Missing optional basic provenance metadata: contributor
2.4.4. Missing detailed provenance metadata: issued, publisher

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationenhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions