add terms PVR and RVR, to help address #147

[mcr]

clarify terms parboiled and raw.

[mcr]

also comment in #145

[EskoDijk]

I would be in favor of just using "Registrar's voucher request" and "Pledge's voucher request" in cases where needed.
In the current text we use also other formulations like "the Registrar includes X in its voucher request" so this is language-wise equivalent to "the Registrar's voucher request". If this is only to address #147 I would try to use the above terms simply for the #147 text. Any other opinions?

[petervanderstok]

IMO voucher_request to Registrar voucher_request to MASA no misunderstandings. Peter Esko Dijk schreef op 2021-08-17 16:55:

I would be in favor of just using "Registrar's voucher request" and "Pledge's voucher request" in cases where needed. In the current text we use also other formulations like "the Registrar includes X in its voucher request" so this is language-wise equivalent to "the Registrar's voucher request". If this is only to address #147 [1] I would try to use the above terms simply for the #147 [1] text. Any other opinions? -- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub [2], or unsubscribe [3]. Triage notifications on the go with GitHub Mobile for iOS [4] or Android [5].

Links: ------ [1] #147 [2] #148 (comment) [3] https://github.com/notifications/unsubscribe-auth/ADCZGQPBZLGUWJPDGEHLS6TT5JZ5RANCNFSM5CBVJ55Q [4] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [5] https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email

[EskoDijk]

@petervanderstok We are using other formulations at the moment in the draft like "Registrar sends its voucher request" etc so it names the source of the voucher request. I don't see value in now introducing the naming of the destination of the voucher request, if we use the source's name in current text - one style should be consistently used.

I'm okay with the draft's current formulations like "voucher request from registrar to masa" or "registrar uses X in its voucher request to masa" etc. So that names both source and destination for clarity.

[mcr]

peter van der stok ***@***.***> wrote: IMO voucher_request to Registrar voucher_request to MASA no misunderstandings. But, the voucher request to the Register, gets encapsulated into the voucher-request to the MASA. So, all voucher requests go to MASA. I see plenty of mis-understandings.

[petervanderstok]

Yeah, Michael, What ceasar's remains ceasar's, also encapsulated requests. Peter Michael Richardson schreef op 2021-08-17 18:38:

peter van der stok ***@***.***> wrote: > IMO voucher_request to Registrar voucher_request to MASA > no misunderstandings. But, the voucher request to the Register, gets encapsulated into the voucher-request to the MASA. So, all voucher requests go to MASA. I see plenty of mis-understandings. -- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links: ------ [1] #148 (comment) [2] https://github.com/notifications/unsubscribe-auth/ADCZGQK6U2BHHZJGLMRIFU3T5KGA3ANCNFSM5CBVJ55Q [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email

[petervanderstok]

that's fine with me Esko Dijk schreef op 2021-08-17 18:16:

@petervanderstok [1] We are using other formulations at the moment in the draft like "Registrar sends _its_ voucher request" etc so it names the source of the voucher request. I don't see value in now introducing the naming of the destination of the voucher request, if we use the source's name in current text - one style should be consistently used. I'm okay with the draft's current formulations like "voucher request from registrar to masa" or "registrar uses X in its voucher request to masa" etc. So that names both source and destination for clarity. -- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub [2], or unsubscribe [3]. Triage notifications on the go with GitHub Mobile for iOS [4] or Android [5].

Links: ------ [1] https://github.com/petervanderstok [2] #148 (comment) [3] https://github.com/notifications/unsubscribe-auth/ADCZGQNAKCWPNDFDORN7TVTT5KDMLANCNFSM5CBVJ55Q [4] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [5] https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email

[mcr]

PVR - Pledge Voucher Request
RVR - Registrar Voucher Request

RVR contains PVR embedded.

[mcr]

Suggested change

	The term "raw voucher request" is introduced to refer to the voucher request between the pledge and the Registrar.
	The term "parboiled voucher request" is introduced to refer to the voucher request between the Registrar and the MASA.
	The term Pledge Voucher Request, or acronym PVR, is introduced to refer to the voucher request between the pledge and the Registrar.
	The term Registrar Voucher Request, or acronym RVR, is introduced to refer to the voucher request between the Registrar and the MASA.

[EskoDijk]

@mcr your suggested changes to "PRVR" and "RVR" were not accepted, it seems. The master now contains still the terms "parboiled" and "raw".