diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index b1a715c7..5774379f 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -19,10 +19,10 @@ jobs: matrix: jdk: [11, 14, 17] steps: - - uses: actions/checkout@v3 + - uses: actions/checkout@v4 # details https://github.com/actions/setup-java - name: Set up JDK ${{ matrix.jdk }} - uses: actions/setup-java@v3 + uses: actions/setup-java@v4 with: java-version: ${{ matrix.jdk }} distribution: 'zulu' @@ -34,7 +34,7 @@ jobs: FN=$(ls JAR/*.jar) mv ${FN} ${FN/.jar/_JDK-${{ matrix.jdk }}.jar} - name: Upload JAR - uses: actions/upload-artifact@v3 + uses: actions/upload-artifact@v4 with: name: widoco_JDK-${{ matrix.jdk }} path: JAR/*.jar @@ -42,11 +42,11 @@ jobs: runs-on: ubuntu-latest steps: - name: Set up QEMU - uses: docker/setup-qemu-action@v2 + uses: docker/setup-qemu-action@v3 - name: Set up Docker Buildx - uses: docker/setup-buildx-action@v2 + uses: docker/setup-buildx-action@v3 - name: Login to GitHub Container Registry - uses: docker/login-action@v2 + uses: docker/login-action@v3 with: registry: ghcr.io username: ${{ github.actor }} @@ -54,11 +54,11 @@ jobs: # https://github.com/docker/metadata-action (lower cases image name, etc.) - name: Extract Docker metadata id: meta - uses: docker/metadata-action@v4.6.0 + uses: docker/metadata-action@v5.4.0 with: images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }} - name: Build and push - uses: docker/build-push-action@v4.1.1 + uses: docker/build-push-action@v5.1.0 with: push: ${{ github.event_name != 'pull_request' && github.actor != 'dependabot[bot]' }} tags: ${{ steps.meta.outputs.tags }} diff --git a/Dockerfile b/Dockerfile index 4af297d0..f722f333 100644 --- a/Dockerfile +++ b/Dockerfile @@ -11,6 +11,9 @@ RUN mvn package && \ # ---- FROM openjdk:17-slim +RUN apt-get update +RUN apt-get install -y libfreetype6 fontconfig + WORKDIR /usr/local/widoco COPY --from=BUILD_IMAGE /var/build/widoco/JAR/widoco.jar . diff --git a/README.md b/README.md index 63ef2719..5e3e36d9 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,7 @@ WIDOCO helps you to publish and create an enriched and customized documentation **Author**: Daniel Garijo Verdejo (@dgarijo) -**Contributors**: María Poveda, Idafen Santana, Almudena Ruiz, Miguel Angel García, Oscar Corcho, Daniel Vila, Sergio Barrio, Martin Scharm, Maxime Lefrancois, Alfredo Serafini, @kartgk, Pat Mc Bennett, Christophe Camel, Jacobus Geluk, Martin Scharm, @rpietzsch, Jonathan Leitschuh, Jodi Schneider, Giacomo Lanza, Alejandra Gonzalez-Beltran, Mario Scrocca, Miguel Angel García, Flores Bakker, @JohnnyMoonlight, René Fritze, @telecsur, Jan Vlug, Han Kruiger, Johannes Theissen-Lipp and Roberto Polli. +**Contributors**: María Poveda, Idafen Santana, Almudena Ruiz, Miguel Angel García, Oscar Corcho, Daniel Vila, Sergio Barrio, Martin Scharm, Maxime Lefrancois, Alfredo Serafini, @kartgk, Pat Mc Bennett, Christophe Camel, Jacobus Geluk, Martin Scharm, @rpietzsch, Jonathan Leitschuh, Jodi Schneider, Giacomo Lanza, Alejandra Gonzalez-Beltran, Mario Scrocca, Miguel Angel García, Flores Bakker, @JohnnyMoonlight, René Fritze, @telecsur, Jan Vlug, Han Kruiger, Johannes Theissen-Lipp, Roberto Polli and Victor Chavez. **Citing WIDOCO**: If you used WIDOCO in your work, please cite the ISWC 2017 paper: https://iswc2017.semanticweb.org/paper-138 @@ -75,7 +75,7 @@ Examples of the features of WIDOCO can be seen on [the gallery](https://dgarijo. A tutorial explaining the main features of the GUI can be found [here](https://dgarijo.github.io/Widoco/doc/tutorial/) ## Metadata usage -To see how WIDOCO recognizes metadata annotations in your ontology to create the documentation files, see [the WIDOCO metadata documentation](doc/metadataGuide/guide.md). To learn which metadata properties we recommend adding to your ontology for producing a nice-looking documentation, have a look at our [best practices guide](doc/bestPractices/index-en.html). +To see how WIDOCO recognizes metadata annotations in your ontology to create the documentation files, see [the WIDOCO metadata documentation](doc/metadataGuide/guide.md). To learn which metadata properties we recommend adding to your ontology for producing a nice-looking documentation, have a look at our [best practices guide](https://dgarijo.github.io/Widoco/doc/bestPractices/index-en.html). For example, in order to show your logo in your documentation you just need to use `foaf:logo` as an annotation, as follows: ``` diff --git a/doc/bestPractices/sections/checklist-en.html b/doc/bestPractices/sections/checklist-en.html index 2bed613b..faab43e3 100644 --- a/doc/bestPractices/sections/checklist-en.html +++ b/doc/bestPractices/sections/checklist-en.html @@ -23,7 +23,7 @@
Example:
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix vann: <http://purl.org/vocab/vann/> . <https://w3id.org/example> rdf:type owl:Ontology ; - vann:preferredNamespaceUri <https://w3id.org/example#> . + vann:preferredNamespaceUri "https://w3id.org/example" .

Prefix [RECOMMENDED]

@@ -698,7 +698,7 @@
Example:

Status [OPTIONAL]

-Property indicating the usage status of the term. For example, whether the term is mature enough, whether it has been deprecated, curated, etc. Note that some of the properties proposed below, such as obo:IAO_0000114, have as range a set of fixed values. The registry vocabulary proposes a hierarchy of status that may be used to represent terms as well (reg:statusAccepted, reg:statusValid, reg:statusDeprecated, etc.). +Property indicating the usage status of the term. For example, whether the term is mature enough, whether it has been deprecated, curated, etc. Note that some of the properties proposed below, such as obo:IAO_0000114, have as range a set of fixed values. The registry vocabulary proposes a hierarchy of status that may be used to represent terms as well (reg:statusAccepted, reg:statusValid, reg:statusDeprecated, etc.).