search

buildingSMART / IFC4.3.x-development

Repository to collect updates to the IFC4.3 Specification
Other
167 stars 83 forks source link

Description required for COMMUNICATION in IfcDistributionSystemEnum #68

Open Moult opened 3 years ago

Moult commented 3 years ago

There seems to be a missing description. Ping @CyrilWaechter.

CyrilWaechter commented 3 years ago

I personally do not understand how it is not a duplicate of AUDIOVISUAL or TELEPHONE or DATA.

Moult commented 3 years ago

Ping @TLiebich - do you know who we can reach out to to shed some light on this?

TLiebich commented 3 years ago

my understanding is, that the enum allows for keywords that can be used also for a hierarchical definition of system

Moult commented 3 years ago

@CyrilWaechter does that make sense? Is it valid? As a non-MEP guy it makes sense to me :)

CyrilWaechter commented 3 years ago

Why not. Then I think hierarchy should be made explicit visually in doc. But I do not see how to make it explicit in schema as it is a simple string enum ?

What do you think about following definition ?

A data transport dedicated to any type of human communication.

I specified human because otherwise I don't see the difference with DATA.

Moult commented 2 years ago

@CyrilWaechter I thought data is a subpart of the communications system (wikipedia - Communications_system), especially as nowadays aren't telephone stuff also going through data? I don't know anything about this domain so I'll trust what you say :)

Ping @trond-graphisoft and @kennethsolvik can you confirm / comment on @CyrilWaechter 's proposal?

This is in theory an easy docfix, so hopefully we can get this resolved in the next couple of days.

kennethsolvik commented 2 years ago

@Moult, as you indicate list is getting a bit old fazion even most of these systems still applies in some countries, it is soon due for a proper update.... I can't say we had issues with how it is and I don't see that we bring more value to the content by doing the proposed changes. Perhaps someone can explain why the change is needed? :)

Nowadays Phone, Audiovisual, etc. are embedded as functionality in data network that are wireless and/or wired!

It would be of value to be able to define a data network (system) as wireless or wired, designed for a purpose: -Data -Communication -Control

Unless the need for change argument is good, I would keep the: -AUDIOVISUAL -TELEPHONE -AUDIOVISUAL -etc

I would argue there are still cases where such systems are made and can't be used for other purposes. (even it's rare).