From owner-freebsd-chat Mon Jun 21 17:32:58 1999 Delivered-To: freebsd-chat@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id F29E414EB3 for ; Mon, 21 Jun 1999 17:32:54 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id RAA05272; Mon, 21 Jun 1999 17:32:53 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd005247; Mon Jun 21 17:32:48 1999 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id RAA18525; Mon, 21 Jun 1999 17:32:46 -0700 (MST) From: Terry Lambert Message-Id: <199906220032.RAA18525@usr01.primenet.com> Subject: Re: 32bitsOnline comparison of BSD v. GPL To: garbanzo@hooked.net (Alex Zepeda) Date: Tue, 22 Jun 1999 00:32:46 +0000 (GMT) Cc: des@flood.ping.uio.no, brian@CSUA.Berkeley.EDU, chat@freebsd.org In-Reply-To: from "Alex Zepeda" at Jun 21, 99 04:50:40 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Uh, stop trying to figure out what I'm thinking of, cause what I'm > thinking of is RFC2396: > Uniform Resource Identifiers (URI): Generic Syntax > [...] > Abstract > > A Uniform Resource Identifier (URI) is a compact string of characters > for identifying an abstract or physical resource. This document > defines the generic syntax of URI, including both absolute and > relative forms, and guidelines for their use; it revises and replaces > the generic definitions in RFC 1738 and RFC 1808. > [...] Read down to section 3.3: | 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 | | ":" | "@" | "&" | "=" | "+" | "$" | "," | | The path may consist of a sequence of path segments separated by a | single slash "/" character. Within a path segment, the characters | "/", ";", "=", and "?" are reserved. Each path segment may include a | sequence of parameters, indicated by the semicolon ";" character. | The parameters are not significant to the parsing of relative | references. You could argue for a %26 encoding for the Ampersand, but since it's US ASCII, and it's not part of a {Registry|Server}-based Naming Authority syntactic element, it's a pretty useless point of contention (the original "&" encoding is still broken for standards compliant browsers). It sounds more like you are defending a cut an paste from a "view source" window, rather than something cut from the "Location:" display field. 8-). > > BTW, it's spelled 'superseded'. > > Yes massah. Actually, it's spelled "Updates". 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message