Dear all,
I wasn't sure where to write my points. So I write here.
I also don't have access to shared notes but probably anyways the IDTA sharepoint is still not transparent enough.
Here are my points.
1- RDF de-/serialization is complete
At this point I am quite confident that the core code is finished. Current coverage rate is 84% and I need to focus on exception handling and refactoring. The whole logic is now pure Apache Jena without any dependency on jackson. I can explain why the previous code logic wasn't right or document it, but it is also briefly mentioned in the ongoing pull request:
2- RDF features/issues
Also there are certain issues with RDF right now that need to be fixed in the specification. Especially ordering of elements as already discussed in:
So it would be best to have open discussion with RDF experts (that might not be in IDTA working groups) regarding these features and issues.
3- Missing namespaces in SHACL
@Sebastian
As I pointed out, for RDF validation the SHACL shapes are not quite compatible with Apache Jena validator. Have you tried the shape validation with Protege or also you tried it with Jena?
The issue explained here:
4- Equals logic should allow subtypes
other than ordering of elements that is already mentioned:
We also have issues with the equals implementation in default implementations. A fix already provided:
5- SchemaValidator
The set of string as the output would be quite hard to work with. I suggest having <string, Referable> or something similar that indicates exactly which component or element that is violating the schema. Imagine an environment with 10 submodels and many elements.
Regards,
Hossein
