-
-
Notifications
You must be signed in to change notification settings - Fork 36
Comments: where do we put localization notes / metadata? #233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Outside the message syntax. |
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. |
+100 My thinking was that we should have a registry for the meta. An existing model is ITS (https://www.w3.org/TR/its20/) |
I believe we've settled on not including comments, notes or metadata within the message syntax, at least in the 2.0 spec. |
Closing resolve-candidates per discussion in 2023-07-24 call |
I've put together eemeli/message-resource-wg#19 as a place to continue this discussion. |
No description provided.
The text was updated successfully, but these errors were encountered: