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

Results of validating PECO using OOPS and FOOPS #7

Open
inaja opened this issue May 6, 2023 · 3 comments
Open

Results of validating PECO using OOPS and FOOPS #7

inaja opened this issue May 6, 2023 · 3 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@inaja
Copy link
Contributor

inaja commented May 6, 2023

I know I should have done this before creating the release, but here we are:

  1. OOPS
    1.1. Important:
    1.1.1. Missing disjointness
    1.1.2. Missing domain or range: these are only for the sosa properties, not for any of our properties
    1.2. Minor
    1.2.1. Unconnected elements: prov:Activity, prov:Entity, foaf:Organization, sosa: Result, and sosa:Sensor,
    1.2.2. Missing annotations: 13 missing but all of them are the imported concepts
    1.2.3. Missing explicit declaration of inverse relationshipts: 8 cases, 2 are peco: inEmissionActivityContext and hasEmissionScore. the rest are sosa and qudt relationships
    1.2.4.URI contains file extension
  2. FOOPS
    2.1. Findable:
    2.1.1. OM1: Minimum metadata: The following metadata was not found: author (we have creator)
    2.1.1. FIND3: 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 basic provenance metadata: author and contributor (same as 2.2.1, we have creator)
    2.4.4. Missing detailed provenance metadata: issued, publisher
@inaja inaja changed the title Validation Results of validating PECO using OOPS and FOOPS May 6, 2023
@dgarijo
Copy link
Member

dgarijo commented May 6, 2023

ok, these are recommendations, but I think we are mostly good to go:

  • From OOPS we are getting those because of the missing classes because we are extending instead of importing. No further action needed.
  • I added both peco and ecfo in prefix.cc.
  • I also suggested them in LOV (waiting)
  • Missing metadata, we can include citation (I think I did in ecfo) and publised date or similar. We don't have an official publisher though.

@dgarijo dgarijo added documentation Improvements or additions to documentation enhancement New feature or request labels May 6, 2023
@dgarijo
Copy link
Member

dgarijo commented May 8, 2023

Decisions: publisher should be the github organization TEC.
We now have the ontology in LOV. Add schema:includedInDataCatalog https://lov.linkeddata.es/dataset/lov/vocabs/peco

@inaja
Copy link
Contributor Author

inaja commented May 8, 2023

Update on FOOPS which is now 98%

  1. Findable: all good
  2. Accessible: all good
  3. Interoperable: all good
  4. Reusable: 8.42/9
    4.1 Missing recommended metadata: citation. also optionally contributor.
    4.2. Missing detailed metadata: doi and source. also optionally backwards compatibility
    4.3. Missing basic optional provenance metadata: contributor

@inaja inaja mentioned this issue May 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants