[D] Removing `StructuredDataMessage` and all other RFC 542 4 et al. [logging-log4j2]

GitHub user vy created a discussion: Removing `StructuredDataMessage` and all other RFC 5424 et al.

I propose removing

```
o.a.l.l.message.StructuredDataMessage
o.a.l.l.message.StructuredDataId
o.a.l.l.message.StructuredDataCollectionMessage
o.a.l.l.core/layout/SyslogLayout
o.a.l.l.core/appender/SyslogAppender
o.a.l.l.core/layout/Rfc5424Layout
```

because

- They're not used. (Corpus search revealed no programmatic access<sup>1</sup>.)
- They, if not incorrect, insufficiently model the RFCs they address.
- Associated layouts are not really structured. Their structure guarantee is amended with several exceptions.
- They have several bugs.
- They receive vulnerability reports.
- It has been the biggest maintenance burden of the last 6 months.

If you agree and/or disagree with this proposal, please share your thoughts with your reasoning.

<sup>1</sup> I've searched a corpus of 706,389 unique Maven coordinates, [amounting to 1,288,939 artifacts](https://svn.apache.org/repos/private/pmc/logging/20260602-log4j-rfc5424-artifacts.txt) (the link is only accessible by ASF and Logging Services PMC members!) and 238,544,576 classes in total, and spotted no usages.

GitHub link: https://github.com/apache/logging-log4j2/discussions/4140

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]