Re: File metadata format draft
Miguel Garcia <Miguel.Garcia@nsn.com> Tue, 13 November 2007 10:17 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 1IrspP-0000uX-5v; Tue, 13 Nov 2007 05:17:07 -0500
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1IrspO-0000uS-GM for discuss-confirm+ok@megatron.ietf.org; Tue, 13 Nov 2007 05:17:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrspO-0000t5-5a for discuss@apps.ietf.org; Tue, 13 Nov 2007 05:17:06 -0500
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IrspK-00042J-GI for discuss@apps.ietf.org; Tue, 13 Nov 2007 05:17:06 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id lADAGEs6016679; Tue, 13 Nov 2007 12:16:59 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Nov 2007 12:16:57 +0200
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Nov 2007 12:16:56 +0200
Received: from [10.144.22.54] ([10.144.22.54]) by esebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Nov 2007 12:16:56 +0200
Message-ID: <47397998.10102@nsn.com>
Date: Tue, 13 Nov 2007 12:16:56 +0200
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Cyrus Daboo <cyrus@daboo.name>
Subject: Re: File metadata format draft
References: <4738B07A.3000407@nsn.com> <A446CE74E842E6564DEFDB55@caldav.corp.apple.com>
In-Reply-To: <A446CE74E842E6564DEFDB55@caldav.corp.apple.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Nov 2007 10:16:56.0865 (UTC) FILETIME=[51FE5910:01C825DE]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: "Matuszewski Marcin (Nokia-NRC/Helsinki)" <marcin.matuszewski@nokia.com>, discuss@apps.ietf.org
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
At the moment the integration with the WebDAV properties is not done. I believe this is a topic for discussion. I have here more questions than answers. For example: Do we want to propose a single data format for describing file metadata? The WebDAV properties is already standardized and deployed, whereas the file-data-format draft is not. However, the requirements of both applications are not totally the same. For example, the file data format does not care about the creator, but needs to signal different endpoints (instances) that host the same file. Or can we integrate the WebDAV properties into the file data format? This will effectively create a superset of the WebDAV properties, bt I am not sure it will have a footprint on the implementations, due to the advance state of deployment of WebDAV. Or do we want to continue with two separate paths, perhaps with this mapping that you mentioned? BR, Miguel Cyrus Daboo wrote: > 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. > -- Miguel A. Garcia tel:+358-50-4804586 Nokia Siemens Networks Espoo, Finland
- 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