W3C home > Mailing lists > Public > uri@w3.org > October 2005

Doubt in URI-REFERANCE

From: <oviaprasad.dharuman@flextronicssoftware.com>
Date: Wed, 19 Oct 2005 12:09:35 +0530
To: uri@w3.org
Cc: timbl@w3.org, fielding@ics.uci.edu, masinter@parc.xerox.com
Message-ID: <OF58204688.1D9DC736-ON6525709E.003533E7-6525709F.0024BB2E@flextronicssoftware.com>




Hi Authors

      RFC 2396 says in secs.

A. Collected BNF for URI

relativeURI   = ( net_path | abs_path | rel_path ) [ "?" query ]
net_path      = "//" authority [ abs_path ]
abs_path      = "/"  path_segments

3.3. Path Component

   The path component contains data, specific to the authority (or the
   scheme if there is no authority component), identifying the resource
   within the scope of that scheme and authority.

      path          = [ abs_path | opaque_part ]

      path_segments = segment *( "/" segment )
      segment       = *pchar *( ";" param )
      param         = *pchar

      pchar         = unreserved | escaped |
                      ":" | "@" | "&" | "=" | "+" | "$" | ","


      Since  you said segment ( *pchar) is zero or more occurance the
forward slash "/" come into picture, this grammar clash with
net_path grammer. could you please explain me how can i differentiate
net_path and abs_path in this case.

example:

u=STUVW://abcd?query

can u please tell me //abcd will take it as net_path or abs path.

regards
Ovia




***********************  FSS-Private   ***********************

***********************  FSS-Private   ***********************
"DISCLAIMER: This message is proprietary to Flextronics Software Systems
Limited (FSS) and is intended solely for the use of the
individual to whom it is addressed. It may contain  privileged or
confidential information and should not be circulated or used for
any purpose other than for what it is intended. If you have received this
message in  error, please notify the originator immediately.
If you are not the intended recipient, you are notified that you are
strictly  prohibited  from  using, copying, altering, or disclosing
the contents of this message.  FSS  accepts no  responsibility  for loss or
damage arising from the use of  the information transmitted
by this email including damage from virus."
Received on Wednesday, 19 October 2005 08:09:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 12:15:35 GMT