Difference between infomodel and IDS-G:MetadataBroker regarding purpose of ConnectorUnavailableMessage

[SebastianOpriel]

It is stated here
https://github.com/International-Data-Spaces-Association/InformationModel/blob/4f9dcb7b7f41421148cbe0a9fccf35336e17364f/taxonomies/Message.ttl#L108
that a ConnectorUnavailableMessage says, that a connector may be available again in the future.

In the Broker docs, it is stated, that a connector won't be ever available again, thus currently all Resources are deleted from the Metadata Broker when a connector sends an unavailable message. See

IDS-G/Components/MetaDataBroker/FunctionsAndCorrelatedMessages/MessagesReceivedByABroker.md

Line 6 in e470175

| Unregister a Connector | Event notifying the recipient(s) that a Connector will be unavailable and never be available again | Mandatory | ConnectorUnavailableMessage | Multipart Request Message with only a Header<p> - Header contains the type of message, security token, Connector’s id, along with the date-time stamp in json format Expected response :<p> - MessageProcessedNotification (on success)<p> - RejectionMessage (on Failure) |

[sebbader]

I propose to change the line in the MetaDataBroker file to allow the reappearance of a Connector. Or are there any cases where a one-and-forever behaviour makes sense?