Agree. That’s not an easy change and before takes place we want to consult it with all interested. One reason for change is that right now we misuse some of the ISO terminology, for example, the term “domain”.
@Nata_Ke Those are not the same. PropertySet indicates where to export/find a property in an IFC model while GroupOfProperties is an aggregating object. There can be a property which is located in a different PSet depending on an IFC class (entity). Anyway, GroupOfPropeties is singular, isn’t it?
We’re adding identifiers to the resources lacking it, like the ClassificationProperty. Is the content of your ID the same as of our “namespaceUri” (forget the name for now): “https://identifier.buildingsmart.org/uri/bs-agri/fruitvegs-1.0/class/apple”?
@VladimirAlexiev, you gave definitions from the LD nomenclature, but words such as ontology are also used outside of this context. (ontology - a set of concepts and categories in a subject area or domain that shows their properties and the relations between them). Let’s not forget that bSDD is not made solely for LD purposes, but there are multiple use cases, with the primary one being classifying IFC models in the authoring software.
The bSDD is a place where LD ontologies can be uploaded, but you’re right that those won’t be full ontologies. They need to comply with our strict data model, so it’s not without effort or loss of some aspects. That is the only way we see for supporting openBIM use cases. I’m looking forward to discussing it at LDAC if you see better solutions.
I agree with this one. That’s part of the ongoing discussion.
That is not the resolution I remember. We do intend to remain the current approach with lists of values. As I explained before, the “units” is a list, as there can be multiple units assigned to a property (unlike classificationProperty). For example, the property “length” can be of unit: [mm, cm, m, ft, …], but when applied in a certain context (classificationProperty) it must be of a specific unit, e.g. “cm”.
The connections are represented by outgoing URIs, so they are connected and used in a way. If you are talking about objects not being properly returned by GraphQL, that is indeed something that should be fixed. As discussed in the other thread (bSDD schema diagrams - #8 by VladimirAlexiev), the GraphQL is important but not of high priority, but we are open to contributions in that area if you are interested.
See you at LDAC!