Hi all, We are currently exploring creating xeto specs for our steam heating control systems. We often need to distinguish between "Domestic HOT Water" quantities and "Domestic COLD Water" quantities as a matter of course. To that end, we have attempted to write a Xeto spec for a "Domestic Hot Water Temperature Sensor Point" :
DomesticHotWaterTemperature: NumberPoint {
domestic
hot
point
sensor
temp
water
}
However, when we attempt to use this spec to validate pre-existing point records in our database, we come across this error:
Is there a workaround, say building a DomesticHotWater pointSubject choice, that would allow us to use the spec written above?
Brian FrankFri 8 Aug
Currently that is not allowed since we treat hot-water and domestic-water as an exclusive choice (the first for heating/process only purposes). That is probably something that needs to be discussed in Labs WG. I would image new/different tags is the suggestion to not create semantic confusions. I believe it was discussed years ago a bit, but with no outcome
Uri Craimer Fri 8 Aug
Hi all, We are currently exploring creating xeto specs for our steam heating control systems. We often need to distinguish between "Domestic HOT Water" quantities and "Domestic COLD Water" quantities as a matter of course. To that end, we have attempted to write a Xeto spec for a "Domestic Hot Water Temperature Sensor Point" :
However, when we attempt to use this spec to validate pre-existing point records in our database, we come across this error:
Slot
pointSubject
: Conflicting choiceph::Phenomenon
: DomesticWater, HotWaterIs there a workaround, say building a DomesticHotWater pointSubject choice, that would allow us to use the spec written above?
Brian Frank Fri 8 Aug
Currently that is not allowed since we treat hot-water and domestic-water as an exclusive choice (the first for heating/process only purposes). That is probably something that needs to be discussed in Labs WG. I would image new/different tags is the suggestion to not create semantic confusions. I believe it was discussed years ago a bit, but with no outcome