Re: [dispatch] Requesting DISPATCH of JSContact

Brian Rosen <> Tue, 12 February 2019 16:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 08E851275F3 for <>; Tue, 12 Feb 2019 08:04:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tn78peIVIHA0 for <>; Tue, 12 Feb 2019 08:04:47 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::742]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F4006124C04 for <>; Tue, 12 Feb 2019 08:04:46 -0800 (PST)
Received: by with SMTP id m9so9005918qkl.4 for <>; Tue, 12 Feb 2019 08:04:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Azxc5X7HsdlqwqwZ4IQjPL8eYhafjtzTSoxYLVqztZo=; b=GwRv9U4cPg0YBRNR+/O6WHoSPoy/yWmAcGtmRlyZYLRoxbPpOISboje68l/XuiJZWj RS1BzXD8LVf7TdkuBFHIVqK5RU66DFMOCCnWfiNjmIeDzu/qDIQY7huv72MbNVW5Bw22 v1l+i4frwy2UiMC1oU/tU8iDSzziH8Ii3xiSt9li011OUlkiiE/RsItMcdfd23BsoZVy 0al+PiIkjoxxzR6FAPCvB0UkjUj/zyLb9K5s6XCkfepO5xEmfuDVVdbvstUUE21OTVYg 0690NNUhP0yNHXWaZEqlwhS4AvcSW/i87TtbVtTbTVVN3oyeHRhv6SKsrvLI8bpJ8pGC iPIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Azxc5X7HsdlqwqwZ4IQjPL8eYhafjtzTSoxYLVqztZo=; b=CQjXurM/zlEjFJUNVXg28xMfI8W0MJQ3BXk4pw9EpEHRa/otVdfNcqZgj3L3jRVP8s NbPsR84g5t/F4XBlFcdIr0Zf9n8hnr4UkVVfp4YWqhEedQ3Zb4oLKr726T8hd+wY7u1D rfl/G2ktUq2hu7uniBQxVMfaE10CV+8dpXfWYJmY82zRXbnCrvhSFgXjYQJG0P95cVP2 KB9vJo9G+3rj40mIFI1nsFGKk6xr20RtYSv8PQUn3VeAa81Rh9Fyanqgyr6s6aQWxhxU up0Qkq21IYUeOzO4dzfclwrMwrVpK5mg8/R/19mf82PLRDmW1oOJqgXCoJVl0SeJqnE6 vqHQ==
X-Gm-Message-State: AHQUAuY9DtVkHxL2ukF3v7CxZWYY2znTBaOZuD1HtftcwhQk330H0Rch UDcfYR6hv04BnY9+n+1StpZY2g==
X-Google-Smtp-Source: AHgI3IbJAmI4TffoA5qNC6mvPFLGTXPFNIOCqmMxcNKi4+VmGOFJMNyWlRStssPcC3r/h3g7ULovgg==
X-Received: by 2002:a37:d6d6:: with SMTP id p83mr690801qkl.172.1549987485769; Tue, 12 Feb 2019 08:04:45 -0800 (PST)
Received: from brians-mbp.lan ([]) by with ESMTPSA id e4sm10369873qkg.15.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Feb 2019 08:04:44 -0800 (PST)
From: Brian Rosen <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3F6F64F9-8EBB-46AC-886F-4CD21406FD24"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Tue, 12 Feb 2019 11:04:42 -0500
In-Reply-To: <>
To: Bron Gondwana <>
References: <>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <>
Subject: Re: [dispatch] Requesting DISPATCH of JSContact
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 12 Feb 2019 16:04:50 -0000

I am very much in favor of this work, I will participate, and have an immediate “customer”: in NENA, the North American Emergency Number Association (emergency call/9-1-1/1-1-2), we’re converting all our data structures to json.  We make extensive use of xCards and need a good json equivalent.


> On Feb 12, 2019, at 4:22 AM, Bron Gondwana <> wrote:
> Hi All,
> As work concludes on <> there is interest in doing the same thing with a format for contacts.
> The JSCalendar work grew out of the JMAP specification at <> - there was interest in producing a standalone format which was JSON-native rather the RFC7265's quite mechanical translation of iCalendar, which is confusing and unfamiliar to programmers used to working with JSON data.
> Likewise, JMAP Contacts contains an early attempt at translating VCARD into an easily understood JSON format.  The shape of it is defined at <> - though I expect it would undergo significant revision before submission for publication.   We are aware of both RFC6350 and RFC7095 and would both use them as a guideline and define mappings between them and a new JSON-first format.
> I have already spoken to the ART ADs about this, and they agree that dispatch is the correct venue to discuss this proposal.  The JMAP working group could take it on, but has been mostly focused on the protocols around the formats rather than that formats itself (other than mail).  The CALEXT working group has would be a potential place, if it was to recharter and increase scope to both contacts and calendars (since they seem to travel together in many places due to the use of DAV for both).  Or maybe something else.
> I'm also aware of work within ISO to define address formats and structured name formats which are less western-centric than the existing VCARD 'N' and 'ADR' structured fields.  This format would try to remain backwards compatible with those fields while having a defined way to express the new formats.
> I have asked that the existing JMAP work be put into an initial draft so we have a baseline in IETF style, knowing full well that it is likely to change significantly.
> Cheers,
> Bron.
> --
>   Bron Gondwana, CEO, FastMail Pty Ltd
> <>
> _______________________________________________
> dispatch mailing list
> <>
> <>