Skip to content

Commit ee23a95

Browse files
authored
Update agenda.md
1 parent 5eeb362 commit ee23a95

File tree

1 file changed

+47
-6
lines changed

1 file changed

+47
-6
lines changed

meetings/agenda.md

Lines changed: 47 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -45,19 +45,60 @@ To request that the chair add an agenda item, send email to the message-format-w
4545

4646
Discussion of the function registry. Two of the three models had sections on this.
4747

48-
**Topic:** Bidi
49-
* Requested by: EAO
48+
---
5049

51-
Discussion of bidirectional text handling. See:
52-
* https://github.com/unicode-org/message-format-wg/pull/315
50+
**Über-topic**: ABNF
5351

54-
**Topic:** (Discussion) Guidance needed for dealing with selector explosions
52+
_We need to decide if the ABNF changes are ready to commit. As suspected, writing the ABNF exposed a host of other issues for discussion. But let's start with deciding to commit this ABNF (or request more edits) and then proceed to discuss issues that might modify it._
53+
54+
* https://github.com/unicode-org/message-format-wg/pull/347
55+
56+
57+
**Topic:** First-match vs. best-match
58+
* Requested by: APP
59+
* https://github.com/unicode-org/message-format-wg/issues/351
60+
61+
**Topic:** whitespace in the EBNF
62+
* Requested by: APP, STA
63+
64+
_This topic appears to be done, but let's make sure we agree on the whitespace handling._
65+
66+
* https://github.com/unicode-org/message-format-wg/issues/340
67+
68+
**Topic:** Delimiter for literals
5569
* Requested by: STA
56-
* https://github.com/unicode-org/message-format-wg/discussions/323
70+
* https://github.com/unicode-org/message-format-wg/issues/263
71+
72+
_@stasm reopened this as part of our ABNF work. We need to close on whether to keep `(` and `)` for literals or switch to `|`_
73+
74+
**Topic:** Markup
75+
* Requested by: APP, MIH
76+
* https://github.com/unicode-org/message-format-wg/issues/356
77+
78+
_@mihnita has called out that our decisions about markup might be premature. Meanwhile, based solely on consistency and the ABNF work, @aphillips has a PR adding a markup error. Let's discuss markup._
5779

80+
@mihnita notes:
81+
82+
> Markup open issues:
83+
> * https://github.com/unicode-org/message-format-wg/issues/241
84+
> * https://github.com/unicode-org/message-format-wg/issues/262
85+
> * https://github.com/unicode-org/message-format-wg/issues/238
86+
>
87+
> And to show that it was not agreed on, see PR https://github.com/unicode-org/message-format-wg/pull/283 in Jun 21, 2022:
88+
>> I will approve it to move things forward and not have these many open PRs.
89+
>> It does not mean I agree with this syntax, so it should not be hold against me 1 month from now ("but you approved X")
90+
>> There are still at least 2 open issues arguing about how to best handle "markup elements"
5891
5992
---
6093

6194
## Proposed for Future (or if time permits)
6295

96+
**Topic:** Bidi
97+
* Requested by: EAO
6398

99+
Discussion of bidirectional text handling. See:
100+
* https://github.com/unicode-org/message-format-wg/pull/315
101+
102+
**Topic:** (Discussion) Guidance needed for dealing with selector explosions
103+
* Requested by: STA
104+
* https://github.com/unicode-org/message-format-wg/discussions/323

0 commit comments

Comments
 (0)