Error when building from source: 'extension' is already defined for 'build_Build'

[benjarobin]

Now when I try to generate the library from source, I have the following error when using the library.

'extension' is already defined for 'build_Build'

In the generated v3_0_1.py the following bloc is duplicated:

        # Specifies an Extension characterization of some aspect of an Element.
        cls._add_property(
            "extension",
            ListProp(ObjectProp(extension_Extension, False)),
            iri="https://spdx.org/rdf/3.0.1/terms/Core/extension",
            compact="extension",
            deprecated=False
        )

To reproduce this issue:

mkdir test
cd test
python3 -m venv .venv
. .venv/bin/activate
pip install shacl2code
shacl2code generate --input https://spdx.org/rdf/3.0.1/spdx-model.ttl  --input https://spdx.org/rdf/3.0.1/spdx-json-serialize-annotations.ttl  --context https://spdx.org/rdf/3.0.1/spdx-context.jsonld --license Apache-2.0 python -o out.py
grep extension_Extension out.py

Do you have any clue why now the generated spdx-python-model library is corrupted?

[JPEWdev]

This is caused by the new model splitting property validation and shacl2code not handling that. JPEWdev/shacl2code#61 should fix this in shacl2code and then we can bring in the fix here by upgrading shacl2code

[benjarobin]

Thank you for the quick fix (tested OK).
There is one thing that I do not understand, 2 months ago I was able to generate successfully the spdx-python-model library using the latest version of shacl2code (see JPEWdev/shacl2code#54 (comment)), why now it is broken?
The model (https://spdx.org/rdf/3.0.1/spdx-model.ttl) changed? If yes when?

[JPEWdev]

@benjarobin There was a bug in the TTL files where extensions didn't work properly, which was fixed in spdx/spec-parser#186. It was missed that shacl2code could not handle this (mostly an oversight on my part)