Re: BPMLOD and string metadata

Sure.

I should mention, btw, that this is not a simple matter of open 
preference – the group should have a strong argument for using emails 
for technical discussions that takes into account the people outside the 
group who will interact with it. (Email is typically used for admin 
related topics, like this one, though.) The W3C actually discourages use 
of emails for technical discussions by Working Groups, and use of GH 
issues is the standard mode of operation.  Note also that, for example, 
this greatly facilitates the process of horizontal review (ie. reviews 
for i18n, accessibility, privacy, & security) which are essential parts 
of tech report devt at W3C, as well as wider public review, as the 
review process relies on labels associated with GH issues.  The 
difference in effectiveness of reviews since we moved away from email 
threads is like night and day. Use of GH issues make threads findable 
and much more easy to read, it also avoids splintering (in the way this 
thread has), and can be labelled for automatic processing, 
crossreferencing, etc.

hth
ri

Jorge Gracia del Río wrote on 06/02/2023 11:18:
> Dear Richard, Christian,
>
> Thanks for the interesting discussion, very relevant!
> I'll leave the decision to record things like that as "issues" or keep 
> them in the email archive to the new panel of chairs (voting will take 
> place on 15th Feb during our next meeting).
>
> Best regards,
> Jorge
>
> El jue, 2 feb 2023 a las 13:43, r12a (<ishida@w3.org 
> <mailto:ishida@w3.org>>) escribió:
>
>     This one first:
>
>     Christian Chiarcos wrote on 02/02/2023 11:54:
>>     I think it's a good idea to put the gist there, but to move the
>>     discussion there completely will very likely get it out of sync
>>     with the mailing list and the broader community, because then,
>>     you need to explicitly enable notifications. In particular, some
>>     of the issues above are actually issues in external vocabularies
>>     like BCP47 or ISO 639, and they may easily go unnoticed by people
>>     *just* on the list.
>
>     For W3C repositories, we normally send digests to the list that
>     people are subscribed to, once a day or once a week, whichever you
>     prefer.  The i18n WG can help you set that up.
>
>     Here's an example of what the email subscriber receives.
>
>
>
>     Clicking on the brown subject text takes you directly to the issue
>     in GitHub.
>
>     Would you folks like to set that up?
>
>     ri
>
>