Re: File metadata format draft
Cyrus Daboo <cyrus@daboo.name> Mon, 12 November 2007 20:09 UTC
Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Irfb6-0005kQ-MI; Mon, 12 Nov 2007 15:09:28 -0500
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1Irfb6-0005kB-48 for discuss-confirm+ok@megatron.ietf.org; Mon, 12 Nov 2007 15:09:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Irfb5-0005k3-Qm for discuss@apps.ietf.org; Mon, 12 Nov 2007 15:09:27 -0500
Received: from piper.mulberrymail.com ([151.201.22.177] helo=mulberrymail.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Irfb1-0002tF-4J for discuss@apps.ietf.org; Mon, 12 Nov 2007 15:09:27 -0500
Received: from caldav.corp.apple.com ([17.101.32.44]) (authenticated bits=0) by mulberrymail.com (8.13.6/8.13.6) with ESMTP id lACK9G34025607 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Nov 2007 15:09:19 -0500
Date: Mon, 12 Nov 2007 15:09:11 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Miguel Garcia <Miguel.Garcia@nsn.com>, discuss@apps.ietf.org
Subject: Re: File metadata format draft
Message-ID: <A446CE74E842E6564DEFDB55@caldav.corp.apple.com>
In-Reply-To: <4738B07A.3000407@nsn.com>
References: <4738B07A.3000407@nsn.com>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.1.1
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on piper.mulberrymail.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: "Matuszewski Marcin (Nokia-NRC/Helsinki)" <marcin.matuszewski@nokia.com>
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org
Hi Miguel, --On November 12, 2007 9:58:50 PM +0200 Miguel Garcia <Miguel.Garcia@nsn.com> wrote: > I have submitted a draft that defines an XML schema for describing files > and associated metadata. I am referring to this draft: > > http://www.ietf.org/internet-drafts/draft-garcia-app-area-file-data-forma > t-00.txt > > The background of this draft is as follows: We first submitted a SIP > event package for subscribing to changes in files stored in a remote > endpoint. The idea is to use SIP to emulate the "shared folder" > functionality that is available in common instant messaging and presence > clients. A part of the overall function is a format for describing files > and associated metadata. > > At the last IETF meeting, I got a few comments indicating that the data > format could be reused by other protocols, namely HTTP, and thus, it > should be split out from the draft and discussed in the Apss area. So > this is what I am doing. > > So, the authors would like to get comments and questions about the > document. Had a quick look. In the HTTP world, meta-data about files is already covered by WebDAV properties. So the question I have is what, if any, thought has been given to integration with WebDAV. e.g. a lot of elements in your schema have exact equivalents in WebDAV. It might be useful, at a minimum, to define a mapping between your schema and what WebDAV provides. -- Cyrus Daboo
- File metadata format draft Miguel Garcia
- Re: File metadata format draft Cyrus Daboo
- Re: File metadata format draft Miguel Garcia
- Re: File metadata format draft Trace Bond
- Re: File metadata format draft Miguel Garcia