Tidy up pages

bact · herrboyer · progval · commit e1a35617965e · 2025-10-01T13:08:32.000+02:00
- Put missing title metadata to pages - Update developer guide to use v3 context file - Update User guide to use v3 context file (by @herrboyer) - Update JSON-LD page to use v3 context file (by @herrboyer) - Update Python versions for tools in Tools (by @herrboyer) - Sort entries in table - Sort column names in tables "File Generation" and "Integrations" to be the same order - Fix small case "codemeta" to "CodeMeta" Co-Authored-By: Renaud Boyer <52666720+herrboyer@users.noreply.github.com>
diff --git a/content/create.md b/content/create.md
@@ -3,8 +3,7 @@ title: "Create a CodeMeta file"
 #layout: login
 ---
 
-Need to generate a CodeMeta compliant metadata file? Try out the [CodeMeta Generator](https://codemeta.github.io/codemeta-generator), which was created by the folks at [Software Heritage](https://www.softwareheritage.org). 
-
+Need to generate a CodeMeta compliant metadata file? Try out the [CodeMeta Generator](https://codemeta.github.io/codemeta-generator), which was created by the folks at [Software Heritage](https://www.softwareheritage.org).
 
 {{< rawhtml >}}
   <a href="https://www.softwareheritage.org">
diff --git a/content/crosswalk/R.md b/content/crosswalk/R.md
@@ -4,6 +4,6 @@ image: "/img/R.png"
 date: "2017-06-01"
 ---
 
-The following table displays the crosswalk mapping of terms from the R package DESCRIPTION file to codemeta properties.
+The following table displays the crosswalk mapping of terms from the R package DESCRIPTION file to CodeMeta properties.
 
 {{< crosswalk name="R Package Description" >}}
diff --git a/content/crosswalk/_index.md b/content/crosswalk/_index.md
@@ -3,9 +3,8 @@ title: "Crosswalks"
 #layout: single
 ---
 
-The codemeta crosswalk provides an explicit map between the metadata fields used by a broad range of software repositories, registries and archives.  Here are the currently available mappings from existing standards into CodeMeta properties.  Mapping onto a common set of properties should facilitate translation between any two crosswalked standards.  The full crosswalk table is [available as a `.csv`](https://github.com/codemeta/codemeta/tree/master/crosswalk.csv) file on the CodeMeta repository.  
+The CodeMeta crosswalk provides an explicit map between the metadata fields used by a broad range of software repositories, registries and archives.  Here are the currently available mappings from existing standards into CodeMeta properties.  Mapping onto a common set of properties should facilitate translation between any two crosswalked standards.  The full crosswalk table is [available as a `.csv`](https://github.com/codemeta/codemeta/tree/master/crosswalk.csv) file on the CodeMeta repository.  
 
 ## Contribute!
 
-CodeMeta encourages submissions of additional vocabularies by making Pull Requests against the [full crosswalk table](https://github.com/codemeta/codemeta/tree/master/crosswalk.csv).  Feel free to propose corrections or extensions in the [codemeta issues tracker](https://github.com/codemeta/codemeta/issues).
-
+CodeMeta encourages submissions of additional vocabularies by making Pull Requests against the [full crosswalk table](https://github.com/codemeta/codemeta/tree/master/crosswalk.csv).  Feel free to propose corrections or extensions in the [CodeMeta issues tracker](https://github.com/codemeta/codemeta/issues).
diff --git a/content/developer-guide.md b/content/developer-guide.md
@@ -1,5 +1,6 @@
-
-# CodeMeta Developer Guide
+---
+title: CodeMeta Developer Guide
+---
 
 This guide is intended for software developers who require detailed information about the CodeMeta project's
 usage of JavaScript Object Notation for Linked Data ([JSON-LD](http://json-ld.org/)) for defining a
@@ -28,7 +29,7 @@ The JSON-LD [Best Practices guide](http://json-ld.org/spec/latest/json-ld-api-be
 > Linked Data is a way to create a network of standards-based machine interpretable data
 > across different documents and Web sites. It allows an application to start at one piece of Linked
 > Data, and follow embedded links to other pieces of Linked Data that are hosted on different
-> sites across the Web."
+> sites across the Web.
 
 JSON-LD is a W3C standard, specified at https://www.w3.org/TR/json-ld/
 
@@ -43,11 +44,11 @@ A CodeMeta software description, or *CodeMeta document*, uses the JSON names con
 Because the CodeMeta document refers to the context file, the mapping between the local JSON names and the
 IRIs is always known, thereby giving the local names universal context.
 
-An example usage of the CodeMeta document is for the author of research software package to generate a CodeMeta Document when the software package is published to a repository. The  CodeMeta Document can be used to aid in any repository ingest processing. The  CodeMeta Document can be made available in the repository with the software package as it may contain additional metadata that was not used by the repository. In addition this file may be used in other transactions involving the software package after the package has been downloaded from the repository.
+An example usage of the CodeMeta document is for the author of research software package to generate a CodeMeta Document when the software package is published to a repository. The CodeMeta Document can be used to aid in any repository ingest processing. The CodeMeta Document can be made available in the repository with the software package as it may contain additional metadata that was not used by the repository. In addition this file may be used in other transactions involving the software package after the package has been downloaded from the repository.
 
-The producer of an  CodeMeta Document, i.e. the creators of the software, must use the JSON names from the CodeMeta context file. The consumer of the  CodeMeta Document can use these same JSON names from the  CodeMeta Document for any necessary processing tasks.
+The producer of an CodeMeta Document, i.e. the creators of the software, must use the JSON names from the CodeMeta context file. The consumer of the CodeMeta Document can use these same JSON names from the CodeMeta Document for any necessary processing tasks.
 
-As an alternative to using the producer supplied JSON names, the consumer can use the [JSON-LD API](https://www.w3.org/TR/json-ld-api/) to translate the JSON names to their own local JSON names that may be in use by their local processing scripts. This is done by first using the JSON-LD *expand* function that replaces each JSON name in the  CodeMeta Document with it's corresponding IRI from the CodeMeta context file. For example, the producer's CodeMeta Document may contain the following line:
+As an alternative to using the producer supplied JSON names, the consumer can use the [JSON-LD API](https://www.w3.org/TR/json-ld-api/) to translate the JSON names to their own local JSON names that may be in use by their local processing scripts. This is done by first using the JSON-LD *expand* function that replaces each JSON name in the CodeMeta Document with it's corresponding IRI from the CodeMeta context file. For example, the producer's CodeMeta Document may contain the following line:
 
 ```json
       "codeRepository": "https://github.com/DataONEorg/rdataone"
@@ -59,7 +60,7 @@ Using the JSON-LD API *expand* function, this is converted to:
      "http://schema.org/codeRepository": "https://github.com/DataONEorg/rdataone"
 ```
 
-Next, the consumer can use their own context file that maps from each IRI to their own local JSON names. For example, the consumer may have a context that maps the local JSON name 'repository' (as in `package.json` documents used by NPM, see [/crosswalk/node/]) to "http://schema.org/codeRepository", so using the JSON API *compact* function would result in a new  CodeMeta Document with the entry:
+Next, the consumer can use their own context file that maps from each IRI to their own local JSON names. For example, the consumer may have a context that maps the local JSON name 'repository' (as in `package.json` documents used by NPM, see [/crosswalk/node/]) to "http://schema.org/codeRepository", so using the JSON API *compact* function would result in a new CodeMeta Document with the entry:
 
 ```json
      "repository": "https://github.com/DataONEorg/rdataone"
@@ -84,10 +85,10 @@ Tools will be created that assist in the generation of CodeMeta documents. For e
 
 ## Extending the CodeMeta Context
 
-CodeMeta explicitly defines the terms it uses from <http://schema.org>, rather than merely extending <http://schema.org> with a few additional terms.  To use additional terms from <http://schema.org> not listed on the [terms page](/terms/) (or terms from any other context), you must extend your context appropriately.  For instance, to combine codemeta (v2.0-rc) with all terms available in schema.org, you would do:
+CodeMeta explicitly defines the terms it uses from <http://schema.org>, rather than merely extending <http://schema.org> with a few additional terms.  To use additional terms from <http://schema.org> not listed on the [terms page](/terms/) (or terms from any other context), you must extend your context appropriately.  For instance, to combine CodeMeta (v3.0) with all terms available in schema.org, you would do:
 
 ```json
-"@context": ["https://raw.githubusercontent.com/codemeta/codemeta/2.0-rc/codemeta.jsonld", "http://schema.org/"]
+"@context": ["https://w3id.org/codemeta/3.0", "http://schema.org/"]
 ```
 
 Note the default context should be listed last.  
diff --git a/content/examples.md b/content/examples.md
@@ -1,4 +1,3 @@
 ---
 title: Examples
 ---
-
diff --git a/content/jsonld.md b/content/jsonld.md
@@ -2,21 +2,20 @@
 title: "The CodeMeta JSON-LD Representation"
 ---
 
-
-CodeMeta uses JSON-LD to represent and translate between software metadata formats.  JSON-LD lead developer Manu Sporny explains how JSON-LD works in this short clip:
-
+CodeMeta uses JSON-LD to represent and translate between software metadata formats.
+JSON-LD lead developer Manu Sporny explains how JSON-LD works in this short clip:
 
 {{< youtube Tm3fD89dqRE >}}
 
-
-
 ## The JSON-LD Context File
 
-The current codemeta context file can be found at [![DOI](https://img.shields.io/badge/doi%3A-10.5063%2FSCHEMA%2FCODEMETA--2.0-blue.svg)](https://doi.org/10.5063/schema/codemeta-2.0)
-
-
-
-CodeMeta properties are built on and extend software properties from <https://schema.org>.  A list of all properties provided by the current CodeMeta `context` file can be found on the [terms](/terms) page. Here's an example [codemeta.json file](https://github.com/codemeta/codemetar/blob/master/codemeta.json) for the `codemetar` R package.  
+[![W3IDCodeMeta v3](https://img.shields.io/badge/W3ID-CodeMeta_v3-blue)](https://w3id.org/codemeta/3.0)
 
-## Compaction & expansion examples: 
+The current CodeMeta context file can be found at[`https://w3id.org/codemeta/3.0`](https://w3id.org/codemeta/3.0).
 
+CodeMeta properties are built on and extend software properties from
+<https://schema.org>.
+A list of all properties provided by the current CodeMeta `context` file can be
+found on the [terms](/terms) page. Here's an example
+[codemeta.json file](https://github.com/gem-pasteur/macsyfinder/blob/master/codemeta.json)
+for the `gem-pasteur/macsyfinder` project.
diff --git a/content/terms.md b/content/terms.md
@@ -18,5 +18,4 @@ The CodeMeta project also introduces the following additional properties, which
 
 {{< properties-description matchParentType="codemeta:">}}
 
-
-Please suggest additional terms or adjustments to this representation in the [codemeta issues](https://github.com/codemeta/codemeta/issues)
+Please suggest additional terms or adjustments to this representation in the [CodeMeta issues](https://github.com/codemeta/codemeta/issues).
diff --git a/content/tools.md b/content/tools.md
@@ -1,39 +1,42 @@
-# Tools
+---
+title: Tools
+---
 
-This page lists some existing tools to help with CodeMeta files
+This page lists some existing tools to help with CodeMeta files.
 
 ## File Generation
 
-Some of the early tools still need a little updating to use the latest version of the codemeta context.
+Some of the early tools still need a little updating to use the latest version of the CodeMeta context.
 
 {.table .table-striped}
 
-tool | language | codemeta version | maintainer | notes
------|----------|------------------|------------|--------------
-[CodeMeta file generator](https://gist.github.com/arfon/478b2ed49e11f984d6fb) | Ruby | 0.1.0 | [arfon](http://github.com/arfon) | (no support for current schema)
-[Bolognese](https://github.com/datacite/bolognese) | Ruby | 1.0.0 | [mfenner](https://github.com/mfenner) | primarily a tool for conversion between formats provided by DataCite, including codemeta and schema.org
-[codemetar](https://ropensci.github.io/codemetar) | R | 2.0.0 | [cboettig](https://github.com/cboettig) | Generate codemeta for R packages; + generic codemeta manipulation
-[codemetapy](https://github.com/proycon/codemetapy) | Python | 2.0.0 | [proycon](https://github.com/proycon) | Generate codemeta for Python, NodeJS, Java packages and others; + generic codemeta manipulation
-[tributors](https://con.github.io/tributors/) | Python | 2.0.0 | [vsoch](https://github.com/vsoch) | Generate codemeta contributors section from GitHub API and Orcid API
+Name | Language | CodeMeta versions | Maintainers | Description
+-----|----------|-------------------|------------|--------------
+[AutoCodemeta Generator](https://w3id.org/autocodemeta) | JavaScript | 3.0.0 | [dgarijo](http://github.com/dgarijo) | Optimized version of CodeMeta Generator that automatically creates a CodeMeta file from a given repository
+[Bolognese](https://github.com/datacite/bolognese) | Ruby | 1.0.0 | [mfenner](https://github.com/mfenner) | Primarily a tool for conversion between formats provided by DataCite, including CodeMeta and schema.org
 [cff-converter](https://github.com/citation-file-format/cff-converter-python) | Python | 2.0.0 | [jspaaks](https://github.com/jspaaksh) | Convert `CITATION.cff` files to codemeta
-[CodeMeta generator](https://codemeta.github.io/codemeta-generator/) | Javascript | 2.0.0 | [ProgVal](https://github.com/ProgVal) | Online form to create or complete a codemeta file
-[codemeta-harvester](https://github.com/proycon/codemeta-harvester) | POSIX Shell | 2.0.0 | [proycon](https://github.com/proycon) | Automatic software metadata conversion pipeline that uses codemetapy and other tools
-[codemeta-server](https://github.com/proycon/codemeta-server) | Python | 2.0.0 | [proycon](https://github.com/proycon) | Webservice offering an API (including SPARQL) and simple human web-interface so search and browse software metadata
-[openCARP-CI](https://opencarp.org/CI) | Python | openCARP developers | GitLab CI pipelines including the conversion from CodeMeta to other formats (Citation File Format (CFF), DataCite, BagIt and BagPack)
-[AutoCodemeta Generator](https://w3id.org/autocodemeta) | Javascript | 3.0.0 | [dgarijo](http://github.com/dgarijo) | Optimized version of CodeMeta Generator that automatically creates a codemeta file from a given repository
-[Somef](https://github.com/KnowledgeCaptureAndDiscovery/somef) | Python | OEG developers | [dgarijo](http://github.com/dgarijo) | Tool that automatically extracts software metadata from repositories and scientific publications.
+[CodeMeta file generator](https://gist.github.com/arfon/478b2ed49e11f984d6fb) | Ruby | 0.1.0 | [arfon](http://github.com/arfon) | (no support for current schema)
+[CodeMeta generator](https://codemeta.github.io/codemeta-generator/) | JavaScript | 2.0.0, 3.0.0 | [ProgVal](https://github.com/ProgVal) | Online form to create or complete a CodeMeta file
+[codemeta-harvester](https://github.com/proycon/codemeta-harvester) | POSIX Shell | 2.0.0, 3.0.0 | [proycon](https://github.com/proycon) | Automatic software metadata conversion pipeline that uses codemetapy and other tools
+[codemeta-server](https://github.com/proycon/codemeta-server) | Python | 2.0.0, 3.0.0 | [proycon](https://github.com/proycon) | Webservice offering an API (including SPARQL) and simple human web-interface so search and browse software metadata
+[codemetapy](https://github.com/proycon/codemetapy) | Python | 2.0.0, 3.0.0 | [proycon](https://github.com/proycon) | Generate CodeMeta for Python, NodeJS, Java packages and others; + generic CodeMeta manipulation
+[codemetar](https://ropensci.github.io/codemetar) | R | 2.0.0 | [cboettig](https://github.com/cboettig) | Generate CodeMeta for R packages; + generic CodeMeta manipulation
+[openCARP-CI](https://opencarp.org/CI) | Python | 2.0.0| [openCARP developers](https://opencarp.org/) | GitLab CI pipelines including the conversion from CodeMeta to other formats (Citation File Format (CFF), DataCite, BagIt and BagPack)
+[Somef](https://github.com/KnowledgeCaptureAndDiscovery/somef) | Python | OEG developers | [dgarijo](http://github.com/dgarijo) | Tool that automatically extracts software metadata from repositories and scientific publications
+[tributors](https://con.github.io/tributors/) | Python | 2.0.0 | [vsoch](https://github.com/vsoch) | Generate CodeMeta contributors section from GitHub API and ORCID API
 
 ## Integrations
 
-Integrations indicate existing platforms & services which understand CodeMeta descriptions. These do not provide a user-facing software tool for generating codemeta.json, but can ingest
+Integrations indicate existing platforms & services which understand CodeMeta descriptions.
+These do not provide a user-facing software tool for generating codemeta.json, but can ingest
 existing codemeta.json files automatically.
 
 {.table .table-striped}
 
-Name | Description |  Authors | Language | CodeMeta Version
+Name | Language | CodeMeta versions | Maintainers | Description
 -----|-------------|----------|----------|--------------------
-[Fidgit](https://github.com/arfon/fidgit): | An ungodly union of GitHub and Figshare | Arfon Smith, Kaitlin Thaney, Mark Hahnel | Ruby | 0.1.0
-[Software Heritage](https://docs.softwareheritage.org/devel/swh-indexer/metadata-workflow.html#adding-support-for-additional-ecosystem-specific-metadata)|The metadata indexers | SWH team | Python | 2.0
+[Fidgit](https://github.com/arfon/fidgit) | Ruby | 0.1.0 | Arfon Smith, Kaitlin Thaney, Mark Hahnel | An ungodly union of GitHub and Figshare
+[Software Heritage](https://docs.softwareheritage.org/devel/swh-indexer/metadata-workflow.html#adding-support-for-additional-ecosystem-specific-metadata) | Python | 2.0 | SWH team | The metadata indexers
 
 Pending:
 
diff --git a/content/user-guide.md b/content/user-guide.md

-Original file line number
+Diff line change
@@ @@ -1,4 +1,3 @@ @@
 ---
 title: Examples
 ---
+-