Skip to content

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

Closed
mihnita opened this issue May 11, 2022 · 6 comments
Closed

Comments: where do we put localization notes / metadata? #233

mihnita opened this issue May 11, 2022 · 6 comments
Labels
resolve-candidate This issue appears to have been answered or resolved, and may be closed soon. syntax Issues related with syntax or ABNF

Comments

@mihnita
Copy link
Collaborator

mihnita commented May 11, 2022

No description provided.

@mihnita mihnita added the syntax Issues related with syntax or ABNF label May 11, 2022
@markusicu
Copy link
Member

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

@zbraniecki
Copy link
Member

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
Copy link
Collaborator Author

mihnita commented Jun 6, 2022

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 eemeli added the resolve-candidate This issue appears to have been answered or resolved, and may be closed soon. label Jul 3, 2023
@eemeli
Copy link
Collaborator

eemeli commented Jul 3, 2023

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

@aphillips
Copy link
Member

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

@eemeli
Copy link
Collaborator

eemeli commented Dec 13, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolve-candidate This issue appears to have been answered or resolved, and may be closed soon. syntax Issues related with syntax or ABNF
Projects
None yet
Development

No branches or pull requests

5 participants