3 ms·
Obvious question: how does it relate to vCard, which is the standard way of describing contacts? The examples shown are too simplistic for real world use: how d
by zvr 2y ago
Obvious question: how does it relate to vCard, which is the standard way of describing contacts?
The examples shown are too simplistic for real world use: how do I specify multiple phones/emails, like work and personal?
And a nitpick: it cannot be both "open source and public domain" -- open source means it's licensed under an Open Source license, while public domain means that there are no IP rights.
- breck 2y agoLooking at vCard (https://pldb.io/concepts/vcard.html https://pldb.io/concepts/vcard.html) it would be straightforward to compile Contacts to vCard. I am not the one to do that due to time constraints, but a company in the space did reach out to me and they are interested in leading a new standard based on this. I offer to anyone the same I offer to them: I can create better documentation on how to write more advanced Parsers, so that it should be easy for someone who wants to make this compile to vCard do. We would just need to add a `buildVcard` parser to Scroll, and then the appropriate parsers to compile each field to vCard format. Multiple phones/emails/work/personal et cetera are trivial in this system. Check out PLDB which runs on the same system and has almost 400 fields of all types (nested, multiples, lists, blobs, maps, et cetera) Everything is public domain. It is also open source in that the source code is available as well. I added that because otherwise I could make the binaries public domain without publishing the source code.