Re: [VCARDDAV] How to encode X-Properties in XML?

Joe Hildebrand <joe.hildebrand@webex.com> Tue, 30 March 2010 21:48 UTC

Return-Path: <Joe.Hildebrand@webex.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 506A23A6B62 for <vcarddav@core3.amsl.com>; Tue, 30 Mar 2010 14:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.402
X-Spam-Level:
X-Spam-Status: No, score=-103.402 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
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 FSIeoHhFRe8S for <vcarddav@core3.amsl.com>; Tue, 30 Mar 2010 14:48:04 -0700 (PDT)
Received: from gw1.webex.com (gw1.webex.com [64.68.122.208]) by core3.amsl.com (Postfix) with SMTP id A3A8B3A6975 for <vcarddav@ietf.org>; Tue, 30 Mar 2010 14:48:04 -0700 (PDT)
Received: from SRV-EXSC03.webex.local ([192.168.252.197]) by gw1.webex.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 30 Mar 2010 14:48:34 -0700
Received: from 171.69.125.115 ([171.69.125.115]) by SRV-EXSC03.webex.local ([192.168.252.200]) with Microsoft Exchange Server HTTP-DAV ; Tue, 30 Mar 2010 21:47:57 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Tue, 30 Mar 2010 14:47:56 -0700
From: Joe Hildebrand <joe.hildebrand@webex.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, vcarddav@ietf.org
Message-ID: <C7D7BF9C.20CFD%joe.hildebrand@webex.com>
Thread-Topic: [VCARDDAV] How to encode X-Properties in XML?
Thread-Index: AcrQUqgfLSodhFZlukaX+BByYtvKqg==
In-Reply-To: <4BB2694F.7060108@stpeter.im>
IM-ID: xmpp:jhildebr@cisco.com
Presence-ID: xmpp:jhildebr@cisco.com
Jabber-ID: jhildebr@cisco.com
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 30 Mar 2010 21:48:34.0696 (UTC) FILETIME=[BF2FD880:01CAD052]
Subject: Re: [VCARDDAV] How to encode X-Properties in XML?
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: Tue, 30 Mar 2010 21:48:05 -0000

On 3/30/10 2:12 PM, "Peter Saint-Andre" <stpeter@stpeter.im> wrote:

>>> - On input, the content of the XML: property MUST be interpreted as a
>>> single XML element.
> 
> Qualified by what namespace? My sense of the discussion so far is that
> the single XML element contained in the "XML:" property MUST have some
> namespace.

I'm just asking "or else what?"  What are the consequences of being
non-conformant, particularly when it can cause loss of information on
round-trip.

>> No.  I'm suggesting that we put these extensions in a new namespace,
> 
> "DAV:" perhaps? ;-)

Not funny in several directions at once.  Nicely done.

(Note to those who don't get the important one of the jokes, DAV: is a
prefix, not a namespace.)

>> preferably a new namespace per spec that adds 1+ properties.
> 
> Why are we defining this bucket in the first place? It seems to me that
> we want to be encouraging people to use the extensibility they have with
> XML, not redefine the "urn:ietf:params:xml:ns:vcard-4.0" namespace by
> creating new elements in that namespace outside the schema we've defined.

Agree that we should be using XML for extensibility, and agree that we don't
want those elements to go into urn:ietf:params:xml:ns:vcard-4.0.  For
example, draft-daboo-vcard-service-type might use
urn:ietf:params:xml:ns:vcard:service-type.  If that I-D defined multiple
properties, they could all use that namespace URI.  The
...vcard:service-type namespace then becomes the bucket.

-- 
Joe Hildebrand