Skip to main content

semantify

Semantification of the CEUR-WS publication workflow

PyPi PyPI Status License pypi format downloads
GitHub Github Actions Build Release Contributors Last Commit GitHub issues GitHub closed issues
Code style-black imports-isort
Docs API Docs formatter-docformatter style-google

See Issue #1: Semantify CEUR-WS for the project vision and definition of done.

Installation

pip install pyCEURsemantify

The command line tool is ceursemantify; ceursemantify -h lists the options. Releases are on PyPI, the milestones on GitHub.

Generator

ceursemantify generates year, volume and paper pages for volume numbers and ranges, see #24. The JSON-LD of each volume is fetched from ceur-spt and mapped to the research model of cr.bitplan.com. The year of a volume is the year of the start date of its event.

# generate volumes into the year of their event
ceursemantify 3649-4202 -o /tmp/ceur-ws-yyyy --progress
# rebuild the page of a year from the volumes present
ceursemantify --year 2024 -o /tmp/ceur-ws-yyyy
# fetch and write the volumes of a year again and rebuild its page
ceursemantify --year 2024 --regenerate -o /tmp/ceur-ws-yyyy --progress
# load all JSON-LD files into memory and serve them as SPARQL endpoint, see #18
ceursemantify --serve -o /tmp/ceur-ws-yyyy

Written are yyyy/index.html, yyyy/Vol-N/index.html and yyyy/Vol-N/paperK/index.html, each volume and paper page with an index.jsonld beside it and the same JSON-LD as a json-ld fence in an HTML comment that semantify3 extracts again.

Embedding

For a volume published on ceur-ws.org the page of the proceedings chair stays as it is; --embed parses it, maps it to the research model and embeds the JSON-LD into it, see #28.

# embed the JSON-LD into the volume pages of the chairs and write index.jsonld next to them
ceursemantify --embed /path/to/Vol-4280 /path/to/Vol-4281/index.html

The page gets a CEURSTATE=embedded comment, the alternate link and the fence in its head; the page is only rewritten if the embedded page parses to the same proceedings as the original one. Embedding again replaces the embedded parts. Example: Vol-4280 with its index.jsonld.

Generating from local volume pages

--generate reads local volume pages instead of ceur-spt and writes the volume and paper pages from them, see #33 and #34. An embedded page is read from its index.jsonld; the fence in the page is only the copy and is read when there is no index.jsonld, see #42. So the DOIs that the registration script writes into index.jsonld reach the pages.

# volume and paper pages into the year tree of the output directory
ceursemantify --generate /path/to/Vol-4298 -o /tmp/ceur-ws-yyyy
# in place: index.html, index.jsonld and the paper pages Vol-N/paperK/ into the volume directory itself
ceursemantify --generate /path/to/Vol-4298 --in-place

With --in-place the page of the proceedings chair is replaced by the generated one, see #43. The sequence for a newly published volume per #14 is --embed, the DOI registration writing into index.jsonld, --generate --in-place.

Endpoint

--serve loads all index.jsonld files into memory and serves them over the SPARQL protocol as the single point of truth, see #18. The named queries of the competency questions are in ceursemantify/resources/queries.yaml:

# with an entry ceur-ws-spt for the endpoint in ~/.pylodstorage/endpoints.yaml
sparqlquery -qp ceursemantify/resources/queries.yaml -en ceur-ws-spt -qn AllVolumes -f csv
File Role
ceursemantify/model.py research model: Proceedings, Paper, Event, Scholar, Publisher, City, Country
ceursemantify/resources/ceurspt_mapping.yaml input mapping: ceur-spt JSON-LD to the research model
ceursemantify/volume_html.py input mapping: volume page of the proceedings chair to the research model
ceursemantify/loctime.py parser of the location and time text of a volume page
ceursemantify/embed.py embedding of the JSON-LD into a volume page
ceursemantify/resources/context.yaml JSON-LD context of the research model, with the terms the ontology does not have yet
ceursemantify/resources/queries.yaml named queries of the competency questions for the endpoint
ceursemantify/resources/site.yaml site configuration
ontology/ceur-ws.ttl CEUR-WS proceedings ontology, see discussion 6

Prototype: 2023, 2024, 2025, 2026

Project Role
pyCEURmake CEUR-WS metadata extraction and Volume Browser
ceur-spt Single Point of Truth server — content negotiation (FastAPI)
SemPubFlow Metadata-first publishing workflow (nicegui)
pyLoDStorage List-of-Dict storage with named query support
geograpy3 Location NER/NEL with Wikidata linking
semantify3 YAML-to-triples — syntax matters
snapquery Named parameterized query middleware

Papers

Paper Venue Status
Semantification of CEUR-WS with Wikidata as a target Knowledge Graph text2kg 2023 accepted
SemPubFlow: a novel Scientific Publishing Workflow using Knowledge Graphs, Wikidata and LLMs Semantic Web Journal rejected
Semantify CEUR-WS ISWC 2026 In-Use Track to be submitted

License

Apache 2.0 (under discussion)

Metadata

Release files for pyCEURsemantify 0.0.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pyCEURsemantify 0.0.2
File Size Uploaded Provenance
pyceursemantify-0.0.2.tar.gz 296.6 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for pyCEURsemantify 0.0.2
File Interpreter ABI Platform
pyceursemantify-0.0.2-py3-none-any.whl Python 3 none any Details

Total release size: 346.8 kB

Release files / pyceursemantify-0.0.2.tar.gz

Download URL pyceursemantify-0.0.2.tar.gz
Size 296.6 kB
Tags Source
SHA-256 checksum
How to use checksums
61651b0568d90d11b49447d70ec1cda7cfa773a658374e85be65f7d168e85fa7
BLAKE2b-256 checksum
How to use checksums
75c0bcf9f5f78e0c3bb96d7af3dd27c1bf991386935b4e1f4beef6dbb2e53c45
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.

Transparency log

Release files / pyceursemantify-0.0.2-py3-none-any.whl

Download URL pyceursemantify-0.0.2-py3-none-any.whl
Size 50.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4f168a926e9521d90f74a95a3a9daa9870bfc61d43a86d06cab4b09f999a6e75
BLAKE2b-256 checksum
How to use checksums
4fef71d12adb519502d035adab4cf292ed8c609cb716b70cb4dfa6032f659fb2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.

Transparency log

Security for pyCEURsemantify 0.0.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for pyceursemantify-0.0.2.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.0.2 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page