Re: [regext] jCard fix/replacement discussion

2019-03-28 Thread Alexey Melnikov
Hi, On Tue, Mar 26, 2019, at 5:11 PM, Mario Loffredo wrote: > > > > 3. JSContact - based on the DISPATCH meeting on Monday, it is unclear > > if JSContact will be moving forward in the IETF. Speaking as an ART AD, I think I am happy to move quickly on this work if enough interest is expressed in

Re: [regext] jCard fix/replacement discussion

2019-03-26 Thread Mario Loffredo
I wrote “entityFn” instead of “entities?fn”. I apologize for the error. Maybe I’m thinking too much to the reverse search draft :-)) mario Inviato da iPhone > Il giorno 26 mar 2019, alle ore 18:11, Mario Loffredo > ha scritto: > > Hi Andy, > > I provide my comments below. > > > First of al

Re: [regext] jCard fix/replacement discussion

2019-03-26 Thread Mario Loffredo
Hi Andy, I provide my comments below. First of all, I would like to clarify that, as a Java developer, I found jCard more difficult to serialize/deserialize rather than other plain JSON objects but not impossible. Anyway, I would be happy to contribute to the definition of a more efficient

[regext] jCard fix/replacement discussion

2019-03-26 Thread Andrew Newton
All, During the meeting yesterday I stated that I would send my notes on jCard to this list to facilitate discussion. Your comments are encouraged. The following items are comments and observations I have heard from various people, etc. 1. Requirements for contact information a. There is a ne