commonmeta-schema 1.0rc1__tar.gz

commonmeta_schema-1.0rc1/.gitignore

@@ -0,0 +1,16 @@
+# macOS
+.DS_Store
+
+# Editor
+.vscode/
+.idea/
+*.swp
+
+# Python build artifacts
+dist/
+build/
+*.egg-info/
+
+# Rust build artifacts
+target/
+rust/target/

commonmeta_schema-1.0rc1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Front Matter
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

commonmeta_schema-1.0rc1/PKG-INFO

@@ -0,0 +1,152 @@
+Metadata-Version: 2.4
+Name: commonmeta-schema
+Version: 1.0rc1
+Summary: Commonmeta JSON Schemas and conformance fixtures
+Project-URL: Homepage, https://github.com/front-matter/commonmeta-schema
+Project-URL: Repository, https://github.com/front-matter/commonmeta-schema
+Project-URL: Issues, https://github.com/front-matter/commonmeta-schema/issues
+Author: Front Matter
+License-Expression: MIT
+License-File: LICENSE
+Keywords: commonmeta,fixtures,json-schema,metadata,schema
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Topic :: Text Processing
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+
+# commonmeta-schema
+
+Language-neutral JSON Schema definitions and conformance fixtures for
+[Commonmeta](https://commonmeta.org), the scholarly metadata interchange format.
+
+This repository is the shared source of truth consumed by the following Commonmeta
+implementations:
+
+- [commonmeta-rs](https://github.com/front-matter/commonmeta-rs) (Rust)
+- [commonmeta-py](https://github.com/front-matter/commonmeta-py) (Python)
+
+Keeping the schema and the golden fixtures in one place lets every
+implementation validate against the same contract and run the same
+cross-format conformance tests.
+
+## Layout
+
+```
+schemas/
+  commonmeta_v1.0rc1.json      # the Commonmeta JSON Schema (current: v1.0rc1)
+fixtures/
+  commonmeta/                  # canonical Commonmeta records (round-trip + expected output)
+  <format>/                    # input fixtures in a given source format
+  <format>_out/                # expected writer output (Commonmeta -> format)
+  <format>_commonmeta/         # expected reader output for non-JSON inputs
+```
+
+## Schema versions
+
+Schemas are versioned by filename. The current version is
+`commonmeta_v1.0rc1.json`; new versions are added alongside it rather than
+replacing existing files, so implementations can pin a version. The
+`schema_version` field of a Commonmeta record is the URL
+`https://commonmeta.org/commonmeta_v1.0rc1.json`.
+
+## Fixture conventions
+
+The conformance harness in each implementation follows these naming rules
+(a missing pair is skipped, so partial coverage is fine):
+
+| Test kind            | Input                                  | Expected                                    |
+|----------------------|----------------------------------------|---------------------------------------------|
+| Round-trip           | `fixtures/commonmeta/<name>.json`      | itself (re-serialized, semantically equal)  |
+| Reader (JSON input)  | `fixtures/<format>/<name>.json`        | `fixtures/commonmeta/<name>.json`           |
+| Reader (text input)  | `fixtures/<format>/<name>.<ext>`       | `fixtures/<format>_commonmeta/<name>.json`  |
+| Writer               | `fixtures/commonmeta/<name>.json`      | `fixtures/<format>_out/<name>.<ext>`        |
+
+Formats currently covered: `crossref`, `crossref_xml`, `datacite`,
+`datacite_xml`, `schemaorg`, `csl`, `bibtex`, `cff`, `ris`, `jsonfeed`,
+`inveniordm`, `codemeta`.
+
+### Semantic comparison
+
+Fixtures are compared as parsed JSON trees, not as strings, using an
+omitempty-aware and numeric-aware diff: key order and whitespace are
+irrelevant, an absent field equals an empty/zero/null value, and `52`
+equals `52.0`. This keeps hand-authored fixtures robust across
+implementations.
+
+## Using this repository
+
+Each implementation vendors (copies) the schema and fixtures it needs from
+here. Update the canonical files in this repository first, then sync them
+into `commonmeta-rs` and `commonmeta-py`.
+
+## Packaging and publishing
+
+This repository can be published as both:
+
+- a Python package on PyPI (`commonmeta-schema`)
+- a Rust crate on crates.io (`commonmeta-schema`)
+
+For the initial release, publish explicitly via CLI (not CI automation).
+
+Package versions follow the schema version:
+
+- PyPI uses PEP 440 form: `1.0rc1`
+- crates.io uses SemVer form: `1.0.0-rc.1`
+
+### Python (PyPI) via `uv publish`
+
+1. Ensure you are authenticated for PyPI (recommended: trusted publisher or API token).
+2. Build distribution artifacts:
+
+  ```bash
+  uv build
+  ```
+
+3. Optionally validate the build metadata:
+
+  ```bash
+  uvx twine check dist/*
+  ```
+
+4. Publish to PyPI:
+
+  ```bash
+  uv publish
+  ```
+
+### Rust (crates.io) via `cargo publish`
+
+1. Log in once with a crates.io token:
+
+  ```bash
+  cargo login
+  ```
+
+2. Validate package contents from the crate directory:
+
+  ```bash
+  cargo package --manifest-path rust/Cargo.toml --allow-dirty
+  ```
+
+3. Publish:
+
+  ```bash
+  cargo publish --manifest-path rust/Cargo.toml
+  ```
+
+### Recommended first-release order
+
+1. Publish `1.0rc1` to PyPI with `uv publish`.
+2. Publish `1.0.0-rc.1` to crates.io with `cargo publish`.
+3. Create a git tag `v1.0rc1` after both uploads succeed.
+
+## License
+
+[MIT](LICENSE) © 2026 Front Matter

commonmeta_schema-1.0rc1/README.md

@@ -0,0 +1,129 @@
+# commonmeta-schema
+
+Language-neutral JSON Schema definitions and conformance fixtures for
+[Commonmeta](https://commonmeta.org), the scholarly metadata interchange format.
+
+This repository is the shared source of truth consumed by the following Commonmeta
+implementations:
+
+- [commonmeta-rs](https://github.com/front-matter/commonmeta-rs) (Rust)
+- [commonmeta-py](https://github.com/front-matter/commonmeta-py) (Python)
+
+Keeping the schema and the golden fixtures in one place lets every
+implementation validate against the same contract and run the same
+cross-format conformance tests.
+
+## Layout
+
+```
+schemas/
+  commonmeta_v1.0rc1.json      # the Commonmeta JSON Schema (current: v1.0rc1)
+fixtures/
+  commonmeta/                  # canonical Commonmeta records (round-trip + expected output)
+  <format>/                    # input fixtures in a given source format
+  <format>_out/                # expected writer output (Commonmeta -> format)
+  <format>_commonmeta/         # expected reader output for non-JSON inputs
+```
+
+## Schema versions
+
+Schemas are versioned by filename. The current version is
+`commonmeta_v1.0rc1.json`; new versions are added alongside it rather than
+replacing existing files, so implementations can pin a version. The
+`schema_version` field of a Commonmeta record is the URL
+`https://commonmeta.org/commonmeta_v1.0rc1.json`.
+
+## Fixture conventions
+
+The conformance harness in each implementation follows these naming rules
+(a missing pair is skipped, so partial coverage is fine):
+
+| Test kind            | Input                                  | Expected                                    |
+|----------------------|----------------------------------------|---------------------------------------------|
+| Round-trip           | `fixtures/commonmeta/<name>.json`      | itself (re-serialized, semantically equal)  |
+| Reader (JSON input)  | `fixtures/<format>/<name>.json`        | `fixtures/commonmeta/<name>.json`           |
+| Reader (text input)  | `fixtures/<format>/<name>.<ext>`       | `fixtures/<format>_commonmeta/<name>.json`  |
+| Writer               | `fixtures/commonmeta/<name>.json`      | `fixtures/<format>_out/<name>.<ext>`        |
+
+Formats currently covered: `crossref`, `crossref_xml`, `datacite`,
+`datacite_xml`, `schemaorg`, `csl`, `bibtex`, `cff`, `ris`, `jsonfeed`,
+`inveniordm`, `codemeta`.
+
+### Semantic comparison
+
+Fixtures are compared as parsed JSON trees, not as strings, using an
+omitempty-aware and numeric-aware diff: key order and whitespace are
+irrelevant, an absent field equals an empty/zero/null value, and `52`
+equals `52.0`. This keeps hand-authored fixtures robust across
+implementations.
+
+## Using this repository
+
+Each implementation vendors (copies) the schema and fixtures it needs from
+here. Update the canonical files in this repository first, then sync them
+into `commonmeta-rs` and `commonmeta-py`.
+
+## Packaging and publishing
+
+This repository can be published as both:
+
+- a Python package on PyPI (`commonmeta-schema`)
+- a Rust crate on crates.io (`commonmeta-schema`)
+
+For the initial release, publish explicitly via CLI (not CI automation).
+
+Package versions follow the schema version:
+
+- PyPI uses PEP 440 form: `1.0rc1`
+- crates.io uses SemVer form: `1.0.0-rc.1`
+
+### Python (PyPI) via `uv publish`
+
+1. Ensure you are authenticated for PyPI (recommended: trusted publisher or API token).
+2. Build distribution artifacts:
+
+  ```bash
+  uv build
+  ```
+
+3. Optionally validate the build metadata:
+
+  ```bash
+  uvx twine check dist/*
+  ```
+
+4. Publish to PyPI:
+
+  ```bash
+  uv publish
+  ```
+
+### Rust (crates.io) via `cargo publish`
+
+1. Log in once with a crates.io token:
+
+  ```bash
+  cargo login
+  ```
+
+2. Validate package contents from the crate directory:
+
+  ```bash
+  cargo package --manifest-path rust/Cargo.toml --allow-dirty
+  ```
+
+3. Publish:
+
+  ```bash
+  cargo publish --manifest-path rust/Cargo.toml
+  ```
+
+### Recommended first-release order
+
+1. Publish `1.0rc1` to PyPI with `uv publish`.
+2. Publish `1.0.0-rc.1` to crates.io with `cargo publish`.
+3. Create a git tag `v1.0rc1` after both uploads succeed.
+
+## License
+
+[MIT](LICENSE) © 2026 Front Matter

commonmeta_schema-1.0rc1/fixtures/bibtex/crossref.bib

@@ -0,0 +1,14 @@
+@article{Sankar_2014,
+  doi = {10.7554/elife.01567},
+  url = {http://elifesciences.org/lookup/doi/10.7554/eLife.01567},
+  year = 2014,
+  month = {feb},
+  publisher = {{eLife} Sciences Organisation, Ltd.},
+  volume = {3},
+  author = {Martial Sankar and Kaisa Nieminen and Laura Ragni and Ioannis Xenarios and Christian S Hardtke},
+  title = {Automated quantitative histology reveals vascular morphodynamics during Arabidopsis hypocotyl secondary growth},
+  abstract = {Among various advantages, their small size makes model organisms preferred subjects of investigation. Yet, even in model systems detailed analysis of numerous developmental processes at cellular level is severely hampered by their scale.},
+  journal = {eLife},
+  issn = {2050-084X},
+  copyright = {http://creativecommons.org/licenses/by/3.0/}
+ }

commonmeta_schema-1.0rc1/fixtures/bibtex/journal_article.bib

@@ -0,0 +1,14 @@
+@article{10.5555/12345678,
+author = {Lovelace, Ada},
+copyright = {https://creativecommons.org/licenses/by/4.0/legalcode},
+date = {2024-03-15},
+doi = {10.5555/12345678},
+issn = {1234-5678},
+issue = {3},
+journal = {Journal of Examples},
+language = {English},
+pages = {100--110},
+title = {A Study of Things},
+url = {https://example.org/article/1},
+volume = {12},
+}

commonmeta_schema-1.0rc1/fixtures/bibtex/pure.bib

@@ -0,0 +1,14 @@
+@phdthesis{dbbe66e459a446a0b6fddf42d3401ccb,
+  title     = "A multiscale analysis of the urban heat island effect: from city averaged temperatures to the energy demand of individual buildings",
+  abstract  = "Designing the climates of cities",
+  author    = "Y. Toparlar",
+  note      = "Proefschrift",
+  year      = "2018",
+  month     = "4",
+  day       = "25",
+  language  = "English",
+  isbn      = "978-90-386-4503-2",
+  series    = "Bouwstenen",
+  publisher = "Technische Universiteit Eindhoven",
+  school    = "Department of Built Environment",
+}

commonmeta_schema-1.0rc1/fixtures/bibtex_commonmeta/crossref.json

@@ -0,0 +1,82 @@
+{
+    "id": "https://doi.org/10.7554/elife.01567",
+    "type": "JournalArticle",
+    "container": {
+        "identifier": "2050-084X",
+        "identifier_type": "ISSN",
+        "type": "Journal",
+        "title": "eLife",
+        "volume": "3"
+    },
+    "contributors": [
+        {
+            "type": "Person",
+            "person": {
+                "given_name": "Martial",
+                "family_name": "Sankar"
+            },
+            "roles": [
+                "Author"
+            ]
+        },
+        {
+            "type": "Person",
+            "person": {
+                "given_name": "Kaisa",
+                "family_name": "Nieminen"
+            },
+            "roles": [
+                "Author"
+            ]
+        },
+        {
+            "type": "Person",
+            "person": {
+                "given_name": "Laura",
+                "family_name": "Ragni"
+            },
+            "roles": [
+                "Author"
+            ]
+        },
+        {
+            "type": "Person",
+            "person": {
+                "given_name": "Ioannis",
+                "family_name": "Xenarios"
+            },
+            "roles": [
+                "Author"
+            ]
+        },
+        {
+            "type": "Person",
+            "person": {
+                "given_name": "Christian S",
+                "family_name": "Hardtke"
+            },
+            "roles": [
+                "Author"
+            ]
+        }
+    ],
+    "date_published": "2014-02",
+    "description": "Among various advantages, their small size makes model organisms preferred subjects of investigation. Yet, even in model systems detailed analysis of numerous developmental processes at cellular level is severely hampered by their scale.",
+    "identifiers": [
+        {
+            "identifier": "https://doi.org/10.7554/elife.01567",
+            "identifier_type": "DOI"
+        }
+    ],
+    "license": {
+        "id": "CC-BY-3.0",
+        "title": "Creative Commons Attribution 3.0 Unported",
+        "url": "http://creativecommons.org/licenses/by/3.0/"
+    },
+    "publisher": {
+        "name": "eLife Sciences Organisation, Ltd."
+    },
+    "schema_version": "https://commonmeta.org/commonmeta_v1.0.json",
+    "title": "Automated quantitative histology reveals vascular morphodynamics during Arabidopsis hypocotyl secondary growth",
+    "url": "http://elifesciences.org/lookup/doi/10.7554/eLife.01567"
+}

commonmeta_schema-1.0rc1/fixtures/bibtex_commonmeta/journal_article.json

@@ -0,0 +1,42 @@
+{
+  "id": "https://doi.org/10.5555/12345678",
+  "type": "JournalArticle",
+  "title": "A Study of Things",
+  "container": {
+    "identifier": "1234-5678",
+    "identifier_type": "ISSN",
+    "type": "Journal",
+    "title": "Journal of Examples",
+    "first_page": "100",
+    "last_page": "110",
+    "volume": "12",
+    "issue": "3"
+  },
+  "contributors": [
+    {
+      "type": "Person",
+      "person": {
+        "given_name": "Ada",
+        "family_name": "Lovelace"
+      },
+      "roles": [
+        "Author"
+      ]
+    }
+  ],
+  "date_published": "2024-03-15",
+  "identifiers": [
+    {
+      "identifier": "https://doi.org/10.5555/12345678",
+      "identifier_type": "DOI"
+    }
+  ],
+  "language": "en",
+  "license": {
+    "id": "CC-BY-4.0",
+    "title": "Creative Commons Attribution 4.0 International",
+    "url": "https://creativecommons.org/licenses/by/4.0/legalcode"
+  },
+  "schema_version": "https://commonmeta.org/commonmeta_v1.0.json",
+  "url": "https://example.org/article/1"
+}

commonmeta_schema-1.0rc1/fixtures/bibtex_out/journal_article.bib

@@ -0,0 +1,16 @@
+@article{10.5555/12345678,
+    abstract = {An abstract about things.},
+    author = {Lovelace, Ada},
+    copyright = {https://creativecommons.org/licenses/by/4.0/legalcode},
+    doi = {{10.5555/12345678}},
+    issn = {1234-5678},
+    issue = {3},
+    journal = {Journal of Examples},
+    language = {English},
+    month = {mar},
+    pages = {100--110},
+    title = {A Study of Things},
+    url = {{https://example.org/article/1}},
+    volume = {12},
+    year = {2024},
+}

commonmeta_schema-1.0rc1/fixtures/cff/CITATION.cff

@@ -0,0 +1,83 @@
+# This CITATION.cff file was created by ruby-cff (v 0.9.0).
+# Gem: https://rubygems.org/gems/cff
+# CFF: https://citation-file-format.github.io/
+
+cff-version: 1.2.0
+message: If you use ruby-cff in your work, please cite it using the following metadata
+title: Ruby CFF Library
+abstract: This library provides a Ruby interface to manipulate Citation File Format files
+authors:
+- family-names: Haines
+  given-names: Robert
+  orcid: https://orcid.org/0000-0002-9538-7919
+  affiliation: The University of Manchester, UK
+- name: The Ruby Citation File Format Developers
+keywords:
+- ruby
+- credit
+- software citation
+- research software
+- software sustainability
+- metadata
+- citation file format
+- CFF
+version: 0.9.0
+doi: 10.5281/zenodo.1184077
+date-released: 2021-08-18
+license: Apache-2.0
+repository-artifact: https://rubygems.org/gems/cff
+repository-code: https://github.com/citation-file-format/ruby-cff
+references:
+- type: software
+  title: Citation File Format
+  authors:
+  - family-names: Druskat
+    given-names: Stephan
+    orcid: https://orcid.org/0000-0003-4925-7248
+  - family-names: Spaaks
+    given-names: Jurriaan H.
+    orcid: https://orcid.org/0000-0002-7064-4069
+  - family-names: Chue Hong
+    given-names: Neil
+    orcid: https://orcid.org/0000-0002-8876-7606
+  - family-names: Haines
+    given-names: Robert
+    orcid: https://orcid.org/0000-0002-9538-7919
+  - family-names: Baker
+    given-names: James
+    orcid: https://orcid.org/0000-0002-2682-6922
+  - family-names: Bliven
+    given-names: Spencer
+    orcid: https://orcid.org/0000-0002-1200-1698
+    email: spencer.bliven@gmail.com
+  - family-names: Willighagen
+    given-names: Egon
+    orcid: https://orcid.org/0000-0001-7542-0286
+  - family-names: Pérez-Suárez
+    given-names: David
+    orcid: https://orcid.org/0000-0003-0784-6909
+    website: https://dpshelio.github.io
+  - family-names: Konovalov
+    given-names: Alexander
+    orcid: https://orcid.org/0000-0001-5299-3292
+  identifiers:
+  - type: doi
+    value: 10.5281/zenodo.1003149
+    description: The concept DOI for the collection containing all versions of the Citation File Format.
+  - type: doi
+    value: 10.5281/zenodo.5171937
+    description: The versioned DOI for the version 1.2.0 of the Citation File Format.
+  keywords:
+  - citation file format
+  - CFF
+  - citation files
+  - software citation
+  - file format
+  - YAML
+  - software sustainability
+  - research software
+  - credit
+  abstract: CITATION.cff files are plain text files with human- and machine-readable citation information for software. Code developers can include them in their repositories to let others know how to correctly cite their software. This is the specification for the Citation File Format.
+  date-released: 2021-08-09
+  license: CC-BY-4.0
+  version: 1.2.0

commonmeta_schema-1.0rc1/fixtures/cff_commonmeta/CITATION.json

@@ -0,0 +1,76 @@
+{
+    "id": "https://doi.org/10.5281/zenodo.1184077",
+    "type": "Software",
+    "contributors": [
+        {
+            "type": "Person",
+            "person": {
+                "id": "https://orcid.org/0000-0002-9538-7919",
+                "given_name": "Robert",
+                "family_name": "Haines",
+                "affiliations": [
+                    {
+                        "name": "The University of Manchester, UK"
+                    }
+                ]
+            },
+            "roles": [
+                "Author"
+            ]
+        },
+        {
+            "type": "Organization",
+            "organization": {
+                "name": "The Ruby Citation File Format Developers"
+            },
+            "roles": [
+                "Author"
+            ]
+        }
+    ],
+    "date_published": "2021-08-18",
+    "description": "This library provides a Ruby interface to manipulate Citation File Format files",
+    "license": {
+        "id": "Apache-2.0",
+        "title": "Apache License 2.0",
+        "url": "https://www.apache.org/licenses/LICENSE-2.0"
+    },
+    "publisher": {
+        "name": "GitHub"
+    },
+    "references": [
+        {
+            "id": "https://doi.org/10.5281/zenodo.1003149"
+        }
+    ],
+    "schema_version": "https://commonmeta.org/commonmeta_v1.0.json",
+    "subjects": [
+        {
+            "subject": "ruby"
+        },
+        {
+            "subject": "credit"
+        },
+        {
+            "subject": "software citation"
+        },
+        {
+            "subject": "research software"
+        },
+        {
+            "subject": "software sustainability"
+        },
+        {
+            "subject": "metadata"
+        },
+        {
+            "subject": "citation file format"
+        },
+        {
+            "subject": "CFF"
+        }
+    ],
+    "title": "Ruby CFF Library",
+    "url": "https://github.com/citation-file-format/ruby-cff",
+    "version": "0.9.0"
+}