Meeting minutes
Pending Issue Review
<addison> https://
addison: added review on one of VC specs
… bunch of cryptographic ones
<addison> i18n-activity#1807
<gb> Issue 1807 Handling/encoding of nonMandatory and bbsMessages (by aphillips) [pending] [needs-resolution] [t:char_choosing] [s:vc-di-bbs]
addison: basically says messages are byte arrays obtained from UTF-8
… here suggesting some cleanup
atsushi: seems some duplication to other specification
addison: in any case, they need to have some text to say what is the data
<addison> Initialize bbsMessages to an array of byte arrays containing the values in the nonMandatory array of strings encoded using the UTF-8 character encoding.
addison: made a wording suggestion around UTF-8
<addison> i18n-activity#1806
<gb> Issue 1806 Example could use I18N best practices for language (by aphillips) [pending] [needs-resolution] [t:loc_examples_x] [s:vc-di-bbs]
addison: example has text without any i18n labels
<addison> i18n-activity#1805
<gb> Issue 1805 Should `u` specify the byte value? (by aphillips) [pending] [needs-resolution] [t:char_ref] [s:vc-di-bbs]
addison: created bunch of fields with encoded, here starting with 'u' lower case
<addison> i18n-activity#1804
<gb> Issue 1804 "XML Schema formatted date string" not specific enough (by aphillips) [pending] [needs-resolution] [t:loc_time] [s:vc-di-bbs]
addison: field for formatted date, described as XML schema formatted
… there are bunch of formatted schema
… suggest to have some context and to be more specific
addison: will submit all of these
WHATWG+I18N
addison: we had issue with WHATWG, discussed on TPAC. and will have call in Feb
… will go through list of issues
<addison> https://
addison: need to bring developed list of issues to be brought there
addison: made a list via label, and tagged ones related
… if anyone find any issue, you can tag it, and I will go through list for presenting to them
addison: email issue should be here ;)
String-Meta changes
addison: want to call out string-meta text
<addison> https://
JcK: saw improovements
[comments on domain and email/user-part, for display and encoding]
addison: section 2.4 mentioned on legacy protocol, so we may put some more here?