W3C home > Mailing lists > Public > public-media-fragment@w3.org > October 2008

Re: minutes of 2008-10-08 telecon

From: Yves Lafon <ylafon@w3.org>
Date: Tue, 14 Oct 2008 10:50:10 -0400 (EDT)
To: RaphaŽl Troncy <Raphael.Troncy@cwi.nl>
cc: Media Fragment <public-media-fragment@w3.org>
Message-ID: <Pine.LNX.4.64.0810141041580.21954@ubzre.j3.bet>

On Wed, 8 Oct 2008, RaphaŽl Troncy wrote:

>   Yves will take care of the Wiki issue right after call
Done (I think I mentionned it already, but it's always better to double 
check)

>   <scribe> ACTION: Yves to check the status of ';' in a URI [recorded
>   in [17]http://www.w3.org/2008/10/08-mediafrag-minutes.html#action04]

From RFC3986:

<<<
    Aside from dot-segments in hierarchical paths, a path segment is
    considered opaque by the generic syntax.  URI producing applications
    often use the reserved characters allowed in a segment to delimit
    scheme-specific or dereference-handler-specific subcomponents.  For
    example, the semicolon (";") and equals ("=") reserved characters are
    often used to delimit parameters and parameter values applicable to
    that segment.  The comma (",") reserved character is often used for
    similar purposes.  For example, one URI producer might use a segment
    such as "name;v=1.1" to indicate a reference to version 1.1 of
    "name", whereas another might use a segment such as "name,1.1" to
    indicate the same.  Parameter types may be defined by scheme-specific
    semantics, but in most cases the syntax of a parameter is specific to
    the implementation of the URI's dereferencing algorithm.
>>>

So it means that http://example.com/what;date=1234/test is different from 
http://example.com/what;date=5678/test , pretty much like when using '?' 
as opposed to '#'.

-- 
Baroula que barouleras, au tiťu toujou t'entourneras.

         ~~Yves
Received on Tuesday, 14 October 2008 14:50:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 September 2011 12:13:31 GMT