On 2021-01-12 , at 16:21, Andrii Berezovskyi <andriib@...> wrote:

A new poll has been created:

Do the PGB members approve publishing OSLC Automation 2.1 as the PSD 01?

Release materials are located under https://github.com/oslc-op/oslc-specs/releases Intent to publish: https://lists.oasis-open-projects.org/g/oslc-op/message/427?p=,,,50,0,0,0::Created,,am,50,2,0,78714754

The ballot opens immediately and will close on January 19.

Best regards, Andrew Berezovskyi

1. YES, approve the publication
2. NO, reject the publication

Vote Now

Do not reply to this message to vote in the poll. You can vote in polls only through the group's website.

From: Sebastian Hellmann <pr-aksw@...>
Date: 7 December 2020 at 10:23:54 CET
To: public-lod@...
Subject: [ANN] DBpedia Archivo - Call to improve the web of ontologies
Reply-To: streitmatter@...



Apologies for cross-posting

Dear all, 

We are proud to announce DBpedia Archivo (https://archivo.dbpedia.org) an augmented ontology archive and interface to implement FAIRer ontologies. Each ontology is rated with 4 stars measuring basic FAIR features. We discovered 890 ontologies reaching on average 1.95 out of 4 stars. Many of them have no or unclear licenses and have issues w.r.t. retrieval and parsing. 

# Community action on individual ontologies 

We would like to call on all ontology maintainers and consumers to help us increase the average star rating of the web of ontologies by fixing and improving its ontologies. You can easily check an ontology at https://archivo.dbpedia.org/info. If you are an ontology maintainer just release a patched version - archivo will automatically pick it up 8 hours later. If you are a user of an ontology and want your consumed data to become FAIRer, please inform the ontology maintainer about the issues found with Archivo.

The star rating is very basic and only requires fixing small things. However, the impact on technical and legal usability can be immense.

# Community action on all ontologies (quality, FAIRness, conformity)

Archivo is extensible and allows contributions to give consumers a central place to encode their requirements. We envision fostering adherence to standards and strengthening incentives for publishers to build a better (FAIRer) web of ontologies.

1. SHACL (https://www.w3.org/TR/shacl/, co-edited by DBpedia’s CTO D. Kontokostas) enables easy testing of ontologies. Archivo offers free SHACL continuous integration testing for ontologies. Anyone can implement their SHACL tests and add them to the SHACL library on Github. We believe that there are many synergies, i.e. SHACL tests for your ontology are helpful for others as well. 

2. We are looking for ontology experts to join DBpedia and discuss further validation (e.g. stars) to increase FAIRness and quality of ontologies. We are forming a steering committee and also a PC for the upcoming Vocarnival at SEMANTiCS 2021. Please message hellmann@... if you would like to join. We would like to extend the Archivo platform with relevant visualisations, tests, editing aides, mapping management tools and quality checks. 

# How does Archivo work?

Each week Archivo runs several discovery algorithms to scan for new ontologies. Once discovered Archivo checks them every 8 hours. When changes are detected, Archivo downloads and rates and archives the latest snapshot persistently on the DBpedia Databus.

# Archivo's mission

Archivo's mission is to improve FAIRness (findability, accessibility, interoperability, and reusability) of all available ontologies on the Semantic Web. Archivo is not a guideline, it is fully automated, machine-readable and enforces interoperability with its star rating.

- Ontology developers can implement against Archivo until they reach more stars. The stars and tests are designed to guarantee the interoperability and fitness of the ontology.

- Ontology users can better find, access and re-use ontologies. Snapshots are persisted in case the original is not reachable anymore adding a layer of reliability to the decentral web of ontologies.

Let’s all join together to make the web of ontologies more reliable and stable,

Johannes Frey, Denis Streitmatter, Fabian Götz, Sebastian Hellmann and Natanael Arndt

Paper: https://svn.aksw.org/papers/2020/semantics_archivo/public.pdf

On 2020-12-04 , at 17:08, Jim Amsden <jamsden@...> wrote:

IBM is pleased to provide statements of use to the following OASIS OSLC Open Project specifications. 

IBM Statements of use: for OSLC Core Version 3.0 Project Specification

IBM has successfully implemented the OASIS OSLC Core Version 3.0 Project Specification 01 (https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/oslc-core.html dated 17 September 2020), in accordance with the conformance clauses defined in Section "Conformance" of the specification. This use of the specification includes interoperation with other similar independent implementations in the jazz.net applications, specifically the Engineering Lifecycle Management suite of products, as well as integration with other 3rd party tools supporting this and other OSLC domain specifications.

Additionally, IBM jazz.net products include test suites covering the OSLC RM specification v2.0 that still conforms to the v2.1 specification and which can be used for ensuring backwards compatibility of the OSLC RM 2.1 tools according to the relevant conformance clauses. 

IBM Statements of use: for OSLC Requirements Management Version 2.1

IBM has successfully implemented the OASIS OSLC Requirements Management Version 2.1 Project Specification 01 (https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/ps01/requirements-management-spec.html dated 03 September 2020), in accordance with the conformance clauses defined in Section "Conformance" of the specification. This use of the specification includes interoperation with other similar independent implementations in the jazz.net applications, specifically DOORS Next, as well as integration with other 3rd party tools supporting this and other OSLC domain specifications.

Additionally, IBM jazz.net products include test suites covering the OSLC RM specification v2.0 that still conforms to the v2.1 specification and which can be used for ensuring backwards compatibility of the OSLC RM 2.1 tools according to the relevant conformance clauses. 

IBM Statements of use: for OSLC Change Management Version 3.0

IBM has successfully implemented the OASIS OSLC Change Management Version 3.0 Project Specification 01 (https://docs.oasis-open-projects.org/oslc-op/cm/v3.0/ps01/change-mgt-spec.html dated 17 September 2020), in accordance with the conformance clauses defined in Section "Conformance" of the specification. This use of the specification includes interoperation with other similar independent implementations in the jazz.net applications, specifically Engineering Workflow Management, as well as integration with other 3rd party tools supporting this and other OSLC domain specifications.

Additionally, IBM jazz.net products include test suites covering the OSLC RM specification v2.0 that still conforms to the v2.1 specification and which can be used for ensuring backwards compatibility of the OSLC RM 2.1 tools according to the relevant conformance clauses. 

IBM Statements of use: for OSLC Quality Management Version 2.1

IBM has successfully implemented the OASIS OSLC Quality Management Version 2.1 Project Specification 01 (https://docs.oasis-open-projects.org/oslc-op/qm/v2.1/ps01/quality-management-spec.html dated 27 August 2020), in accordance with the conformance clauses defined in Section "Conformance" of the specification. This use of the specification includes interoperation with other similar independent implementations in the jazz.net applications, specifically Engineering Test Management, as well as integration with other 3rd party tools supporting this and other OSLC domain specifications.

Additionally, IBM jazz.net products include test suites covering the OSLC RM specification v2.0 that still conforms to the v2.1 specification and which can be used for ensuring backwards compatibility of the OSLC RM 2.1 tools according to the relevant conformance clauses.