File metadata format draft-garcia-app-area-file-data-format-00.txt 70 th IETF Applications Area Open meeting WG December 2007 Miguel Garcia Marcin Matuszewski

Background Effort started as a next step in the SIP file transfer functionality We already have a file transfer mechanism with SIP/SDP draft-ietf-mmusic-file-transfer-mech- 05.txt draft-ietf-mmusic-file-transfer-mech- 05.txt It allows to do a exchange of SDP bodies describing a file to be exchanged. Unable to instantiate all use cases with a standard SIP protocol Remote file directory Subscription to a picture collection available in a mobile phone Sharing a folder in commercial instant messaging systems Why SIP? See the (expired) draft: draft-garcia-sipping-general-events- 00.txt draft-garcia-sipping-general-events- 00.txt Work is ongoing in solving these use cases: draft-garcia-sipping-file-sharing- framework-01.txt draft-garcia-sipping-file-sharing- framework-01.txt draft-garcia-sipping-file-event-package- 01.txt draft-garcia-sipping-file-event-package- 01.txt draft-garcia-sipping-file-desc-pidf-01.txt An XML data format to describe file metadata is required The data format is independent of SIP. Can be used for HTTP and other protocols Can be used for catalogs of files

Full file-metadata XML document A file XML document contains descriptions of one or more files Each file is modeled as an identity and one or more instances The identity describes the immutable properties of the file: MIME type Size Hash URN The instance describes metadata associated to the file and the endpoint that hosts the resource: URI Name Description Icon creation/modification/read date keywords file-metadata document File 1 Identity Instance 1 Instance 2 Instance n File 2 File n

Full file-metadata XML document image/jpeg FE8653DDAF371362F86D471913EE4A2CE2E coolpic.jpg This is my latest cool picture from my summer vacation T09:30:47+03: T10:24:34+03: T14:24:32+03:00 summer vacation

Partial in File-Metadata document The file-metadata document can also express partial changes with respect a previous version. Reuses the XML Patch Operations framework: draft-ietf-simple-xml-patch-ops-04.txt Useful with periodic notifications Example: nanotalk.3gp Nanotechnology speech T17:26:04+03: T18:02:02Z Three instances of the same file

The questions Do we (IETF) need to define a general format for describing files? If so, how to deal with other similar formats? Webdav properties METS (Metadata Encoding and Transmission Standard) MIME Perhaps others How to continue the work?