Comments (7)
Isn't this a bit in conflict with the impression that Pset_WallCommon.ThermalTransmittance and PSet_DoorCommon.Thermaltransmittance are not seen as the same? Or are they both instances of the unique property or characteristic "thermal transmittance" (the way the user perceives it)?
Is any property name in whatever property set it resides in by definition unique or can it indeed be shared among property sets (and thus needs to be identical)? Is this in line with the way properties are managed and measured? (Probably discussion for CEN/TC 442/WG4)
They currently seem to be defined always in the context of a property set. However, if they are indeed unique, you don't need the property set anymore or the propertyset is only a convenience of grouping (comparable to a Tag).
I don't have a "right" answer to this question, but it needs to be resolved somehow
from bsdd.
this is a well known and recognised issue - it needs to be addressed by making each property (having the same name) unique within the scope of the ifc specification, and not only within a single psets. Hence those properties, like ThermalTransmittance, have to have a single GUID. Inprovements of ifcDoc are currently developed to ensure that this is fixed.
from bsdd.
They currently seem to be defined always in the context of a property set. However, if they are indeed unique, you don't need the property set anymore or the propertyset is only a convenience of grouping (comparable to a Tag).
I like the comparison of a PSet to a "Tag".
One Property would have one or many relations to a PSet. There are properties, that are defined globally and others, that are defined on the level of a Property Set. The grouping of properties in a PSet itself is a separate information and has its own ID. So this is a valueable information too. IMHO we need booth, the property and the group of properties (e.g. purpose driven , like a PDT).
from bsdd.
I have made a try with a "normalized PSet" that references the included properties.
I have made a copy of the Pset_ActionRequest.YAML into the Pset_ActionRequest_normalized.YAML and created individual properties in the subfolder "Properties".
The three properties are now referenced with this syntax:
$ref: '#/Properties/R/NameOfMyPropertyFile'
This could make it possible to eliminate duplicate properties in different PSets.
from bsdd.
from bsdd.
Hi Roger, thanks for your Feedback.
The question is: "What are same properties?"
I think, when the following information about a property is identical, then a property can be seen as identical and they can be merged onto one GUID:
Name
Definition
DataType
MeasureType
For the properties, you have listed, these information is identical und these properties can be normalized and merged.
In the YAML-proposal, I have added in addition in the relation of the PSet to the normalized property the "usage_definition". That could help to further define the normalized property in the context of the PSet.
In the IfcDoc-Group alre parallel discussions about the same topic, @TLiebich and @timchipman are also involved. We should speak about that in Düsseldorf.
from bsdd.
from bsdd.
Related Issues (20)
- What does the “1” mean right to the star symbol in the bSDD UI?
- CORS headers are not set, disabling usage from javascript in browsers HOT 9
- bSDD GraphQL schema HOT 2
- How to search for a classification just by a specific attribute ? HOT 1
- namespaceURI otl.amsterdam.nl doesn't exist within bSDD HOT 1
- GraphQL - non-nullable field symbol - unit HOT 1
- Importing properties require Classifications HOT 2
- Member "PropertyKind" not found HOT 1
- Update IFC classification names CSV HOT 2
- Ontology quick comments HOT 3
- Missing Properties HOT 4
- Import: JSON schema and documentation are not congruent HOT 1
- namespaceURI .../csi/omniclass-1 doesn't exist within bSDD HOT 2
- GET method to retriev all properties of a domain. HOT 7
- get API for the test domain HOT 3
- Classification DocumentReference HOT 1
- IFC attributes HOT 5
- Fraction HOT 3
- the system does not authorize my graphql query HOT 2
- Import model version HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bsdd.