Comments: where do we put localization notes / metadata?

[mihnita]

[markusicu]

Outside the message syntax. I am not sure how much of these need to be standardized by this group and its artifacts.

[zbraniecki]

I think there's a value in standardization of meta data. The question if this group should do it is a valid one, but I'm not sure who else would.

In particular, semantic information between developer and tooling is valuable, and between developer and CAT programs.

My concern about "outside of message syntax" is that I see some meta information applicable to particular part of the message, and if we place it outside we need to ensure ability to link that information to the part of the message and preserve consistency as the message morphs to avoid dangling pointers.

[mihnita]

In particular, semantic information between developer and tooling is valuable, and between developer and CAT programs.

+100

My thinking was that we should have a registry for the meta.

An existing model is ITS (https://www.w3.org/TR/its20/) Allows one to pass info like allowed characters, maximum message length, links to external resources, etc.

[eemeli]

I believe we've settled on not including comments, notes or metadata within the message syntax, at least in the 2.0 spec.

[aphillips]

Closing resolve-candidates per discussion in 2023-07-24 call

[eemeli]

I've put together eemeli/message-resource-wg#19 as a place to continue this discussion.