W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2010

RE: I-D Submission: draft-lee-httpext-metadata-00.txt

From: 이문상 <sang0627.lee@samsung.com>
Date: Sun, 04 Jul 2010 14:36:54 +0900
To: "'Hausenblas, Michael'" <michael.hausenblas@deri.org>, 'Eran Hammer-Lahav' <eran@hueniverse.com>
Cc: ietf-http-wg@w3.org
Message-id: <001401cb1b3a$e92face0$bb8f06a0$%lee@samsung.com>

Thanks for your comment, Michael.
In addition to your comments, it would greatly help web servers reduce
their maintenance cost for service infrastructure. It may reduce network
traffic to back-end servers, require less storage since it does not store
meta-data in another separate document, and simplify publishing and
maintaining of web resource. It relies on web resource itself for meta-
data, and dynamically extracts meta-data on demand. There is the
possibility that CPU load of web server would increase to process such meta-
data extraction, but memory cache could compensate the load.

Semantically, it's similar to range-unit and content-range header in HTTP/1.
1, which allows client to request that only a range of the response entity
be included within the response. In case of this proposal, request-meta
header allows client to request that only a meta-data of the target
resource be included within the response. 

I think the property (or meta-data) of an object (or web resource) is a
part of the object (or web resource). For example, an apple is laid down in
a showcase and I'd like to decide whether I'll buy it. I don't need to grab
the apple directly if I could know its color, smell, sweetness, and
freshness. Pick-out to grab and push-back to the showcase is more
inconvenient. An equipment which monitors the property of the apple can
tell me about the apple if I push a button, and I'm proposing such button
pushing protocol to operate web server to respond with resource meta-data.

Regards,
Moon-Sang Lee

---
Moon-Sang Lee, Senior Engineer, Ph.D.
Convergence Software Lab., Digital Media & Communication R&D Center,
Samsung Electronics Co., Ltd.,
TEL: +82-31-279-8082
Email: sang0627.lee@samsung.com
Wisdom begins in wonder. *Socrates*

-----Original Message-----
From: Hausenblas, Michael [mailto:michael.hausenblas@deri.org] 
Sent: Saturday, June 26, 2010 6:12 PM
To: Eran Hammer-Lahav
Cc: 이문상; ietf-http-wg@w3.org
Subject: Re: I-D Submission: draft-lee-httpext-metadata-00.txt

+1 to what Eran said, I couldn't have phrased it better.

Nevertheless, your use case sounds interesting, Moon-Sang, and I'd be more
than happy to follow-up off-list to investigate how it can be realised with
existing methods, such as Link: header.

Cheers,
             Michael
--
http://sw-app.org/mic.xhtml#i
Sent from my iPhone

On 26 Jun 2010, at 08:57, "Eran Hammer-Lahav" <eran@hueniverse.com>
wrote:

> Hi,
>
> You are entering an area with a lot of prior experience.
>
> There is little reason to extend HTTP with additional headers given 
> the recent work on the HTTP Link header [1] (and the 'describedby'
> relation type), as well as the POWDER [2] and XRD [3] descriptor 
> formats, and the host-meta proposal [4] which is currently in last 
> call. In addition, you might want to take a look at analysis included 
> in an early draft of LRDD [5] which covers existing methods for 
> obtaining resource metadata.
>
> Between using the HTTP Link header and host-meta, you should have full 
> coverage of what you are trying to do, without having to create any 
> new mechanism.
>
> EHL
>
> [1] http://tools.ietf.org/html/draft-nottingham-http-link-header
> [2] http://www.w3.org/TR/powder-dr/
> [3] 
> http://www.oasis-open.org/apps/org/workgroup/xri/download.php/38236/xr
> d-1.0-wd17.html [4] http://tools.ietf.org/html/draft-hammer-hostmeta
> [5] http://tools.ietf.org/html/draft-hammer-discovery-03#appendix-B
>
>
>
>> -----Original Message-----
>> From: ietf-http-wg-request@w3.org [mailto:ietf-http-wg- 
>> request@w3.org] On Behalf Of ???
>> Sent: Friday, June 25, 2010 7:48 PM
>> To: ietf-http-wg@w3.org
>> Subject: FW: I-D Submission: draft-lee-httpext-metadata-00.txt
>>
>>
>> FYI.
>>
>> ---
>> Moon-Sang Lee, Senior Engineer, Ph.D.
>> Convergence Software Lab., Digital Media & Communication R&D Center,
>> Samsung Electronics Co., Ltd.,
>> TEL: +82-31-279-8082
>> Email: sang0627.lee@samsung.com
>> Wisdom begins in wonder. *Socrates*
>>
>> -----Original Message-----
>> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
>> Sent: Friday, June 25, 2010 4:34 PM
>> To: internet-drafts@ietf.org
>> Cc: sang0627.lee@samsung.com; sang0627.lee@samsung.com
>> Subject:
>>
>> Message-Id: <20100625073403.CBA163A69A1@core3.amsl.com>
>> Date: Fri, 25 Jun 2010 00:33:55 -0700 (PDT)
>>
>> ,junglok.yu@samsung.com
>> Subject: Manual Post Requested for draft-lee-httpext-metadata
>> Content-Type: text/plain; charset="utf-8"
>> Mime-Version: 1.0
>>
>> Manual Posting Requested for following Internet-Draft:
>>
>> I-D Submission Tool URL:
>> https://datatracker.ietf.org/idst/status.cgi?submission_id=24392
>>
>>
>> Filename:       draft-lee-httpext-metadata
>> Version:       00
>> Staging URL:       http://www.ietf.org/staging/draft-lee-httpext-
metadata-
>> 00.txt
>> Title:           A New Header For Metadata Exchange
>> Creation_date:       2010-06-25
>> WG ID:           Individual Submission
>> Number_of_pages: 11
>> Abstract:
>> This document provides a mechanism by which web servers can provide
>> metadata of a web resource which is indicated by a URL.  The web  
>> client like
>> web browser can use this metadata to filter out unwanted web  
>> resource or
>> link to itself.  In addition, the web client can take advantage of  
>> such metadata
>> to provide high-level services like displaying additional  
>> information about the
>> web resource without downloading it.  We expect this mechanism to  
>> enable
>> quick access to metadata of any web resource from any web client  
>> reduces
>> overall web traffic remarkably.
>>
>> Submitter: Moon-Sang Lee (sang0627.lee@samsung.com)
>>
>> Author(s):
>> Moon-Sang Lee, sang0627.lee@samsung.com
>>
>> Jung-Lok Yu, junglok.yu@samsung.com
>>
>>
>> Comment:
>> Thank you!
>>
>
Received on Sunday, 4 July 2010 05:37:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:23 GMT