[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2025-02-07 Thread ENRICO FRANCESCONI via auth48archive
Dear Madison, Dear Eliot, thanks for your suggestions. As for the conversion Latin --> Hebrew of the example date, we have probably used a wrong converter, so we agree to use the conversion you suggest. As for the rest, please find in-line our replies. Thanks! Pierluigi and Enrico _

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2025-02-02 Thread ENRICO FRANCESCONI via auth48archive
Dear Madison, thanks for your additional remarks! Please find below (in-line) our comments and proposals. Best regards Pierluigi and Enrico From: Madison Church Sent: 29 January 2025 22:52 To: ENRICO FRANCESCONI ; pierluigi.spin...@gmail.com ; caterina.l.

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2024-12-10 Thread ENRICO FRANCESCONI via auth48archive
Dear Eliot, sorry for such a delay: there were several remarks in the last review, and we took a bit more time than expected to clarify and process them. We are basically ready to send our feedback. We'll do that in the next few hours. Thanks for your understanding Enrico

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2024-12-10 Thread ENRICO FRANCESCONI via auth48archive
Dear Colleagues, thanks a lot for your extensive review of the URN:LEX draft and sorry for our delay. We have reported in a new draft all your remarks accepting your proposals, except the ones still in doubts. Please find them, in-line, here below. Once clarified these last doubts, we can sub

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2024-12-16 Thread ENRICO FRANCESCONI via auth48archive
Dear Eliot, thanks for your feedback. Below in-line our remarks. If all is good, we will upload the next version (25), where all the remaining issues are fixed. Thanks! Pierluigi and Enrico From: Independent Submissions Editor (Eliot Lear) Sent: 12 Decemb

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2025-01-11 Thread ENRICO FRANCESCONI via auth48archive
Dear Madison, Eliot, thanks for your remarks, it is actually our interest to have the document finalised and sorry for this additional trouble. As for the previous submission, the instructions email reported what follows: > You may submit your changes in one of two ways: > > An update to the

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2025-01-25 Thread ENRICO FRANCESCONI via auth48archive
Dear Madison and Eliot, please find here below (in-line) our feedback. In case of additional remarks please let us know. Best Pierluigi and Enrico From: Independent Submissions Editor (Eliot Lear) Sent: 24 January 2025 18:06 To: Madison Church ; ENRICO FRANCESCONI ; pierluigi.spin...@gma

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2025-04-08 Thread ENRICO FRANCESCONI via auth48archive
Hi Eliot, yes, we are on it. Let us double check the document and will be back soon. We are obviously interested to have it finished very soon too. Best Enrico On 8 Apr 2025, at 17:38, Independent Submissions Editor (Eliot Lear) wrote: Enrico, authors, Could you please review? I'd li

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2025-04-20 Thread ENRICO FRANCESCONI via auth48archive
Hi Madison, we double checked the latest changes and everything seems ok. So for us we can proceed. Thanks again for your collaboration! Pierluigi and Enrico > On 15 Apr 2025, at 17:43, Madison Church wrote: > > Hi Enrico, > > Thank you for your reply! We have updated the document as

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2025-04-13 Thread ENRICO FRANCESCONI via auth48archive
Dear Madison, thanks a lot for your collaboration! We have double checked the latest version and we found the following issues: 1) At the end of section 3.4. "Unicode Characters Outside the ASCII Range" - at Munich circular, the UTF-8 code still includes %xC3%xBC instead of %C3%BC, - at Law of

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2025-03-09 Thread ENRICO FRANCESCONI via auth48archive
Dear Madison and Eliot, thanks for your feedback about dates and different conversion formats. In this respect, we noticed a potential issue in the fact that the Hebrew date is written using spaces. Now, the LEX specifications suggest to replace spaces with dots. On the other hand in the dates

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2025-03-06 Thread ENRICO FRANCESCONI via auth48archive
Dear Madison and Eliot, thanks for your feedback about dates and different conversion formats. In this respect, we noticed a potential issue in the fact that the Hebrew date is written using spaces. Now, the LEX specifications suggest to replace spaces with dots. On the other hand in the dates

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2025-02-20 Thread ENRICO FRANCESCONI via auth48archive
Dear Madison and Eliot, just an additional remark: as for the UTF-8 format, we think that in the RFC we should report the version without ‘x’, which is just meant to indicate that what follows are hex values. Basically something like: %xd7%x98… —> %d7%98… which is the encoding used in URLs

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2025-02-20 Thread ENRICO FRANCESCONI via auth48archive
Dear Madison and Eliot, we were preparing an answer to the previous message, when we received two new emails of yours. We report in the following our reply which partially addresses the issue on Hebrew characters you underline in your message. As for the alternatives you propose, we agree with

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2025-04-04 Thread ENRICO FRANCESCONI via auth48archive
Dear Eliot, the latest email of ours was on March 6th about spaces in Hebrew dates. In our opinion it was the last issue to fix. We are now waiting for feedback. Best Enrico On 31 Mar 2025, at 20:25, Independent Submissions Editor (Eliot Lear) wrote: Madison, Enrico, where are we? Eli

[auth48] Re: AUTH48: RFC-to-be 9676 for your review

2025-05-12 Thread ENRICO FRANCESCONI via auth48archive
Dear Sandy, thanks for your feedback! After a new double check, we found the following minor issue to fix at section 2.1: jurisdiction-unit The possible administrative hierarchical —> jurisdiction-unit: The possible administrative hierarchical As for the points you addressed > > a) Section