> Le 7 juin 2023 à 14:26, Andrew Newton <a...@hxr.us> a écrit : > > Hi All, > > Very recently I have had the displeasure of implementing jCard for an > RDAP client, and in so doing have taken a closer look at JSContact and
... > > #3 JSContact Implementations and Scope > > I did a little hunting around for implementations of JSContact, and I > could only find one. While that is the same number of jCard > implementations I found, I would have hoped for many more in many > different programming languages. As it stands, any implementer of > JSContact for a server or a client will need to be intimate with the > complexities of JSContact just as they have had to do with jCard. > I’ve started implementing JSContact in Swift as part of the RDAPBrowser mobile client and haven’t found the need to implement a library as Swift JSON is well integrated into Swift types through the use of the Codable protocol, while Codable was not possible with JCard, so I had to do a lot of manual coding as everyone did. So YMMV, but I don’t see a strong need for a specific library for JSContact in Swift. It could be obviously be done for example by adding nice utility methods, but the fact that none exist does not mean much at least for Swift. I would like to add that we are in an ossification position. While vCard is no fun to implement, the domain industry did it _because_ ICANN required it as part of the RDAP profile. Without that mandate, I’m not sure we would have a lot of RDAP implementations... So similarly, until ICANN requires JSContact to be implemented by the domain industry, the pull to get it done, therefore open-source libraries to be available, is small. Regards, Marc. > > -andy > > _______________________________________________ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
