Re: [VCARDDAV] [ietf-calsify] Call for feedback on HTML5 spec on "predefined vocabularies"

Eliot Lear <lear@cisco.com> Fri, 18 September 2009 15:36 UTC

Return-Path: <lear@cisco.com>
X-Original-To: vcarddav@core3.amsl.com
Delivered-To: vcarddav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31BFF28C1C0 for <vcarddav@core3.amsl.com>; Fri, 18 Sep 2009 08:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.272
X-Spam-Level:
X-Spam-Status: No, score=-10.272 tagged_above=-999 required=5 tests=[AWL=0.327, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eR2gP7ZPXuVJ for <vcarddav@core3.amsl.com>; Fri, 18 Sep 2009 08:36:49 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id B73233A67E4 for <vcarddav@ietf.org>; Fri, 18 Sep 2009 08:36:48 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlsAAABGs0qQ/uCKe2dsb2JhbACBUplRAQEWJAabDIhQAZAdBYQcgV2CdA
X-IronPort-AV: E=Sophos;i="4.44,410,1249257600"; d="scan'208";a="49724365"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 18 Sep 2009 15:37:41 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n8IFbfrI028672; Fri, 18 Sep 2009 17:37:41 +0200
Received: from elear-mac.local (dhcp-10-61-110-163.cisco.com [10.61.110.163]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n8IFbfcw004775; Fri, 18 Sep 2009 15:37:41 GMT
Message-ID: <4AB3A945.4060000@cisco.com>
Date: Fri, 18 Sep 2009 17:37:41 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <4A8010B3.1050100@gmx.de>
In-Reply-To: <4A8010B3.1050100@gmx.de>
X-Enigmail-Version: 0.97a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2833; t=1253288261; x=1254152261; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20Re=3A=20[ietf-calsify]=20Call=20for=20feedback= 20on=20HTML5=20spec=20on=20=22predefined=0A=20vocabularies=2 2 |Sender:=20; bh=/vBOqLUtbvvqxbxgef2gS6g1EZxfWjwZ0uXlc/O6F6A=; b=JJuicorrViNw83S2VoasBfBrGnDi4r70dHAyhRG4s2aY1aGF14ML+iOV46 BthyQ13bje7X4NtfjPucP2LatJlaCZ482mtN6s3/FhEqaXUOxM/RZoZbjEUC +6max4MgmH;
Authentication-Results: ams-dkim-1; header.From=lear@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; );
Cc: Apps Discuss <discuss@apps.ietf.org>, Calsify <ietf-calsify@osafoundation.org>, CardDAV <vcarddav@ietf.org>
Subject: Re: [VCARDDAV] [ietf-calsify] Call for feedback on HTML5 spec on "predefined vocabularies"
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vcarddav>
List-Post: <mailto:vcarddav@ietf.org>
List-Help: <mailto:vcarddav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Sep 2009 15:36:50 -0000

Dear all,

I recently had a thread with Julian in which he feels pretty strongly
about the below message regarding HTML5, and the vocabulary for
calendaring that is proposed.  I suggest that people who are interested
review the proposed specification below and comment either on one of
these lists or to Julian directly.

Eliot

On 8/10/09 2:21 PM, Julian Reschke wrote:
> Hi,
>
> (cross-posted to IETF apps-discuss, plus vcarddav and calsify mailing lists)
>
> the W3C HTML Working Group is currently preparing a new Working Draft 
> for HTML5. This will be based on the current Editor's Draft at 
> <http://dev.w3.org/html5/spec/Overview.html>).
>
> A significant change since the last Working Draft is the introduction of 
> "microdata", a way to augment the markup with semantics, similar to and 
> competing with RDFa and microformats in general (see 
> <http://dev.w3.org/html5/spec/Overview.html#microdata>).
>
> As part of introducing microdata, the spec also defines several 
> "predefined vocabularies". Some of them are based on IETF formats (and 
> this is why I'm writing this particular email).
>
> One of these vocabularies is "vcard" (see 
> <http://dev.w3.org/html5/spec/Overview.html#vcard>). As far as I can 
> tell, the HTML spec more or less duplicates information from RFC 2426, 
> and while doing so also introduces specific compliance criteria. It does 
> *not* refer to 
> <http://tools.ietf.org/html/draft-ietf-vcarddav-vcardrev-08>, so, as far 
> as I can tell, it would hardwire the vocabulary to a soon-to-be-outdated 
> version of the spec, and also removes the inherent extensibility model.
>
> Another predefined vocabulary is "vevent" (see 
> <http://dev.w3.org/html5/spec/Overview.html#vevent>), to which similar 
> observations apply.
>
> I have talked to this to many W3C and IETF people, and as far as I can 
> tell, almost all of them consider this to be a Bad Idea. In particular, 
> it seems that the author has not even tried to co-ordinate with the two 
> applicable IETF Working Groups (I just checked the mailing list 
> archives, and couldn't find anything, but maybe I'm missing something).
>
> I'm not sure whether the two working groups have considered this issue 
> yet. I encourage to look at the spec now 
> (<http://dev.w3.org/html5/spec/Overview.html>), or as soon as a new 
> Working Draft is published.
>
> In case the Calsify and/or Vcarddav Working Groups want to comment on 
> this, I encourage the chairs to send feedback directly to the W3C HTML 
> WG, so that the feedback gets the proper attention.
>
> Best regards, Julian
>
> _______________________________________________
> ietf-calsify mailing list
> ietf-calsify@osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>
>