1 / 6

File metadata format draft-garcia-app-area-file-data-format-00.txt

File metadata format draft-garcia-app-area-file-data-format-00.txt. 70 th IETF Applications Area Open meeting WG December 2007 Miguel Garcia <miguel.garcia@nsn.com> Marcin Matuszewski <marcin.matuszewski@nokia.com>. Effort started as a next step in the SIP file transfer functionality

ellenab
Download Presentation

File metadata format draft-garcia-app-area-file-data-format-00.txt

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. File metadata formatdraft-garcia-app-area-file-data-format-00.txt 70th IETF Applications Area Open meeting WG December 2007 Miguel Garcia <miguel.garcia@nsn.com> Marcin Matuszewski <marcin.matuszewski@nokia.com>

  2. 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 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 Work is ongoing in solving these use cases: draft-garcia-sipping-file-sharing-framework-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 Background

  3. 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

  4. Full file-metadata XML document <?xml version="1.0" encoding="UTF-8"?> <file-set xmlns="urn:ietf:params:xml:ns:file" version="123"> <file id="id38sh12jd"> <identity id="id9d8c9"> <mime-type>image/jpeg</mime-type> <size>230432</size> <sha1>72245FE8653DDAF371362F86D471913EE4A2CE2E</sha1> <identity> <instance id="idc989c00"> <name>coolpic.jpg</name> <description>This is my latest cool picture from my summer vacation</description> <user-uri>sip:miguel.garcia@example.com</user-uri> <user-gruu>sip:miguel.garcia@example.com;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6</user-gruu> <icon-ptr>http://www.example.com/coolpic-icon.jpg</icon-ptr> <creation-date>2006-05-09T09:30:47+03:00</creation-date> <modification-date>2006-05-09T10:24:34+03:00</modification-date> <read-date>2006-05-10T14:24:32+03:00</read-date> <keywords> <keyword>summer</keyword> <keyword>vacation</keyword> </keywords> </instance> </file> </file-set>

  5. 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: <?xml version="1.0" encoding="UTF-8"?> <patchxmlns="urn:ietf:params:xml:ns:file"version="313"> <addsel="file-set/file[@id='nkcdn0']"> <instanceid="ak6v3d"> <name>nanotalk.3gp</name> <description>Nanotechnology speech</description> <user-gruu>sip:bob@example.com;gr=urn:uuid:f81d4fae-7dec-11d0-5d3a-bbc333431122</user-gruu> <user-uri>sip:bob@example.com</user-uri> </instance> </add> <replacesel="id('idea1dof')/read-date/text()">2006-06-07T17:26:04+03:00</replace> <replacesel="file-set/timestamp"> <timestamp>2007-11-12T18:02:02Z</timestamp> </replace> <replacesel="file-set/note"> <notexml:lang="en">Three instances of the same file</note> </replace> </patch>

  6. 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?

More Related