Fix build info after first upload

.github/workflows/build.yaml

@@ -25,6 +25,6 @@ jobs:
   build:
     uses: ./.github/workflows/_core.yaml
     with:
-      deploy: true
+      deploy: false
     secrets:
       PYCGMES_PYPI_TOKEN: ${{ secrets.PYCGMES_PYPI_TOKEN }}

pyproject.toml

@@ -12,9 +12,7 @@ repository = "https://github.com/alliander-opensource/pycgmes"
 license = "Apache 2.0"
 classifiers = [
     "Development Status :: 5 - Production/Stable",
-    "Environment :: Web Environment",
-    "Framework :: AWS CDK :: 2",
-    "Framework :: FastAPI",
+    "Framework :: Pydantic",
     "Operating System :: OS Independent",
     "Programming Language :: Python :: 3.10",
     "Programming Language :: Python :: 3.11",

shacl/Readme.md

@@ -1,33 +1 @@
-<!--
-SPDX-FileCopyrightText: 2023 Alliander
-
-SPDX-License-Identifier: Apache-2.0
--->
-
-# Why this directory
-
-It contains the SHACL build files, only meant to build a second distribution package.
-The CI & co happen in the main poetry/github files.
-
-The main `pycgmes` package does not have the SHACL files.
-
-# Actual Shacl files
-
-They are in the [main tree](../pycgmes/shacl/).
-
-# Build
-
-To be able to build multiple pacakges based om the same source, things need to be a bit different, because:
-
-- poetry does not allow another name for `pyproject.toml`
-- you cannot by default include files outside the directory of the `pyproject.toml`
-
-This is neatly worked around via a plugin, written by one of the maintainer of poetry, so it feels safe enough.
-
-```bash
-poetry self add poetry-multiproject-plugin
-poetry build-project --with-top-namespace pycgmes
-```
-
-Note that to build pycgmes-shacl, you **need to** be in the shacl directory. Using `-C` will not work
-because of some relative paths.
+Addition to [pycgmes](https://pypi.org/project/pycgmes/) to handle shacl validation.

shacl/build.md

@@ -0,0 +1,33 @@
+<!--
+SPDX-FileCopyrightText: 2023 Alliander
+
+SPDX-License-Identifier: Apache-2.0
+-->
+
+# Why this directory
+
+It contains the SHACL build files, only meant to build a second distribution package.
+The CI & co happen in the main poetry/github files.
+
+The main `pycgmes` package does not have the SHACL files.
+
+# Actual Shacl files
+
+They are in the [main tree](../pycgmes/shacl/).
+
+# Build
+
+To be able to build multiple pacakges based om the same source, things need to be a bit different, because:
+
+- poetry does not allow another name for `pyproject.toml`
+- you cannot by default include files outside the directory of the `pyproject.toml`
+
+This is neatly worked around via a plugin, written by one of the maintainer of poetry, so it feels safe enough.
+
+```bash
+poetry self add poetry-multiproject-plugin
+poetry build-project --with-top-namespace pycgmes
+```
+
+Note that to build pycgmes-shacl, you **need to** be in the shacl directory. Using `-C` will not work
+because of some relative paths.

shacl/pyproject.toml

@@ -7,14 +7,11 @@ name = "pycgmes-shacl"
 version = "0.9.11"
 description = "Python dataclasses for CGMES 3.0.0"
 authors = ["pycgmes <pycgmes@alliander.com>"]
-# readme = "README.md"
+readme = "Readme.md"
 repository = "https://github.com/alliander-opensource/pycgmes"
 license = "Apache 2.0"
 classifiers = [
     "Development Status :: 5 - Production/Stable",
-    "Environment :: Web Environment",
-    "Framework :: AWS CDK :: 2",
-    "Framework :: FastAPI",
     "Operating System :: OS Independent",
     "Programming Language :: Python :: 3.10",
     "Programming Language :: Python :: 3.11",