headers
Charles Lindsey | 2 Jun 2005 12:07
Picon
Picon

Re: [NNTP] News and nntp URIs


In <87psv63gd3.fsf <at> windlord.stanford.edu> Russ Allbery <rra <at> stanford.edu> writes:

>Charles Lindsey <chl <at> clerew.man.ac.uk> writes:

>> There are now two drafts for your consideration:
>> draft-lindsey-news-nntp-uri-00.txt
>> draft-ellermann-news-nntp-uri-00.txt

>> The first is exactly what I put before you a few months back, except
>> that the '!' has been removed as a possible newsgroup-name
>> character. You all seemed happy with that text last time.

>I personally would prefer to see the NNTP URI scheme wait on the
>publication of the new base document and then follow the approach that
>you're taking of picking up the new NNTP work.  I'm still not sure that
>the full wildmat support in the URI is really the best way to go, but I
>can't come up with any strong argument against it other than "it looks odd
>and I'm not sure how many people will bother using it," which doesn't seem
>strong enough.

Sure. The "lindsey" draft makes normative reference to the new base
document, so it would not escape from the RFC editor until that had been
published.

The real question is whether to have a 'wildcard' notation which is the
same as something that servers are likely to provide (i.e. wildmat), or
whether to invent yet another one. If you write

    news://some.server.example/*.test
(Continue reading)

Permalink | Reply | 0 comments |
headers
Charles Lindsey | 2 Jun 2005 12:07
Picon
Picon

Re: [NNTP] News and nntp URIs


In <87psv63gd3.fsf <at> windlord.stanford.edu> Russ Allbery <rra <at> stanford.edu> writes:

>Charles Lindsey <chl <at> clerew.man.ac.uk> writes:

>> There are now two drafts for your consideration:
>> draft-lindsey-news-nntp-uri-00.txt
>> draft-ellermann-news-nntp-uri-00.txt

>> The first is exactly what I put before you a few months back, except
>> that the '!' has been removed as a possible newsgroup-name
>> character. You all seemed happy with that text last time.

>I personally would prefer to see the NNTP URI scheme wait on the
>publication of the new base document and then follow the approach that
>you're taking of picking up the new NNTP work.  I'm still not sure that
>the full wildmat support in the URI is really the best way to go, but I
>can't come up with any strong argument against it other than "it looks odd
>and I'm not sure how many people will bother using it," which doesn't seem
>strong enough.

Sure. The "lindsey" draft makes normative reference to the new base
document, so it would not escape from the RFC editor until that had been
published.

The real question is whether to have a 'wildcard' notation which is the
same as something that servers are likely to provide (i.e. wildmat), or
whether to invent yet another one. If you write

    news://some.server.example/*.test
(Continue reading)

Permalink | Reply | 1 comment |
headers
Charles Lindsey | 2 Jun 2005 18:43
Picon
Picon

Re: [NNTP] News and nntp URIs


On Thu, 02 Jun 2005 11:07:52 +0100, Charles Lindsey <chl <at> clerew.man.ac.uk>
wrote:

> I will also post this message to the uri <at> w3.org list if I can figure out
> how to do it.

I figured it out so well, that I managed to post it twice. Apologies for
that.

FYI, and in case it was not clear, I was replying to a message by Russ on
the nntpext list (there is sufficient of my original post to that list
quoted for you to see the context).

--

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133   Web: http://www.cs.man.ac.uk/~chl
Email: chl <at> clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5
Permalink | Reply | 0 comments |
headers
noah_mendelsohn | 12 Jun 2005 17:35
Picon
Favicon

[schemeProtocols-49] Editor's draft of finding on schemeProtocols-49

I've been working on an initial draft of a finding for issue 
schemeProtocols-49 [1].  What I've got so far is work in progress, but 
there's probably enough to be the basis for useful discussion.  I'm 
sending this now in the hopes that something rough in time for the face to 
face will be more useful than a more complete draft a week or two later. 
Copies of the files are attached; the .png files should be put in the same 
directory as the .html.  I know this comes too late to be considered 
formal input to the F2F, but the issue is scheduled for discussion, so I'm 
hoping this will still be useful.  Presumbaly we can do more formal 
reviews on telcons later.

There was some discussion of this issue a few months ago in the thread at 
[2], and Larry Masinter raised a number of important concerns in his notes 
at [3,4].  For the most part I agree with those concerns, at least insofar 
as I've correctly understood them, and I hope this draft represents 
progress toward resolving them.   At Larry's request, I am cross posting 
this note to uri <at> w3.org.  We can continue to cross-post as long as people 
in both communities feel it's productive, and when not we can drop back to 
www-tag only. 

Again, I want to emphasize that this is more a snapshot of work in 
progress than a stable or complete editor's draft.  The only reason for 
pointing to it now is in anticipation of next week's F2F meeting.  I do 
think it's in good enough shape to be worth reading.  When I have 
something that I consider a bit more complete I will send another 
announcement. 

By the way:  I had some trouble getting this all checked in, so the copies 
in CVS are not yet being served cleanly (especially the images).  I'm on 
vacation with a very slow dial line and have decided to punt for the
(Continue reading)

Permalink | Reply | 0 comments |
headers
noah_mendelsohn | 12 Jun 2005 17:53
Picon
Favicon

Re: [schemeProtocols-49] Editor's draft of finding on schemeProtocols-49

Replying to my own mail.

Looks like there's a bug in the Web interface to the TAG mailing list. The 
note I sent a few minutes ago had three attachments, and indeed the 
reflected copy sent back to me has all three.  As far as I can tell, the 
page on the web site at [1] only shows 2 of them.  Just so there will be 
an easy way to get all of them from the Web, here's a copy of the same 
files Zipped up together.  I've also included the .xml source here in case 
anyone wants to hack on it.  To view, just unzip all files into a 
directory and browse the HTML.  Thank you.

Noah

[1] http://lists.w3.org/Archives/Public/www-tag/2005Jun/0024.html

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------
Attachment (schemaProtocols.zip): application/zip, 21 KiB
Permalink | Reply | 0 comments |
headers
Frank Ellermann | 15 Jun 2005 23:25
Picon
Picon

draft-ietf-secsh-scp-sftp-ssh-uri-02


Hi, here's your stupid question of the month, what _is_ SCP ?

Also posted on uri <at> w3.org because it's about URIs.  Bye, Frank

<http://www.ietf.org/internet-drafts/draft-ietf-secsh-scp-sftp-ssh-uri-02>
Permalink | Reply | 0 comments |
headers
Larry Masinter | 16 Jun 2005 00:38
Picon
Favicon

FW: I-D ACTION:draft-hansen-2717bis-2718bis-uri-guidelines-04.txt


-----Original Message-----
From: Internet-Drafts <at> ietf.org [mailto:Internet-Drafts <at> ietf.org] 
Sent: Wednesday, June 15, 2005 1:13 PM
To: i-d-announce <at> ietf.org
Subject: I-D ACTION:draft-hansen-2717bis-2718bis-uri-guidelines-04.txt 

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title		: Guidelines and Registration Procedures for  new
URI Schemes
	Author(s)	: T. Hansen, et al.
	Filename	: draft-hansen-2717bis-2718bis-uri-guidelines-04.txt
	Pages		: 14
	Date		: 2005-6-15
	
This document provides guidelines and recommendations for the
   definition of Uniform Resource Identifier (URI) schemes.  It also
   updates the process and IANA registry for URI schemes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-hansen-2717bis-2718bis-uri-guideli
nes-04.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of the
message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Larry Masinter | 18 Jun 2005 01:21
Picon
Favicon

mailto URIs


I'm working on responding to Bruce Lilly's comments
on the 'mailto' URI specification (from April!)

I'm puzzled about whether the full 'address' or 'mailbox'
specification is actually implemented, or whether the
actual URI use is limited to RFC2822's  'addr-spec'.

>From RFC 2822:

mailbox         =       name-addr / addr-spec
name-addr       =       [display-name] angle-addr
angle-addr      =       [CFWS] "<" addr-spec ">" [CFWS] / obs-angle-addr
group           =       display-name ":" [mailbox-list / CFWS] ";"
                        [CFWS]
display-name    =       phrase
mailbox-list    =       (mailbox *("," mailbox)) / obs-mbox-list
address-list    =       (address *("," address)) / obs-addr-list
addr-spec       =       local-part " <at> " domain
local-part      =       dot-atom / quoted-string / obs-local-part
domain          =       dot-atom / domain-literal / obs-domain
domain-literal  =       [CFWS] "[" *([FWS] dcontent) [FWS] "]" [CFWS]
dcontent        =       dtext / quoted-pair
dtext           =       NO-WS-CTL /     ; Non white space controls
                        %d33-90 /       ; The rest of the US-ASCII
                        %d94-126        ;  characters not including "[",
                                        ;  "]", or "\"
atext           =       ALPHA / DIGIT / ; Any character except controls,
                        "!" / "#" /     ;  SP, and specials.
                        "$" / "%" /     ;  Used for atoms
(Continue reading)

Permalink | Reply | 687 comments |
headers
Bjoern Hoehrmann | 18 Jun 2005 01:41
Picon

Re: mailto URIs


* Larry Masinter wrote:
>Do mailto URIs actually work with:
>   *  Angle-bracket delimiters?
>   *  Comments?
>   *  folding white space?
>   *  non-whitespace controls?
>   *  Quoted strings... etc.

http://www.w3.org/mid/3e0db2b9.28612262 <at> smtp.bjoern.hoehrmann.de works
as expected in e.g. Forté Agent, the resulting mail will have "Björn
Höhrmann" in the To: and Subject: headers (properly encoded, of course.)
--

-- 
Björn Höhrmann · mailto:bjoern <at> hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Permalink | Reply | 0 comments |
headers
Frank Ellermann | 18 Jun 2005 03:11
Picon
Picon

Re: mailto URIs


Larry Masinter wrote:

> I'm working on responding to Bruce Lilly's comments
> on the 'mailto' URI specification (from April!)

There are two more comments from February:
http://mid.gmane.org/opsl85thzd6hl8nm <at> clerew.man.ac.uk
http://mid.gmane.org/4210A039.579E <at> xyzzy.claranet.de

My main concern or objection was to establish UTF-8 as
the default charset for mailto:?body= by a mere example.

For any UA supporting a body= parameter at all, if that
is guaranteed to be _zero_ UAs I've no problem with it.

> Do mailto URIs actually work with:
>    *  Angle-bracket delimiters?
>    *  Comments?
>    *  folding white space?
>    *  non-whitespace controls?
>    *  Quoted strings... etc.

My UA certainly doesn't, part of my second concern with
the mailto draft, it should encourage the support of at
least In-Reply-To=

For Bjoern's example I get his subject and a To: bjoern&
That's an oddity of my browser, it hates hex. character
references, &#64; instead of &#x40; might work, example:
(Continue reading)

Permalink | Reply | 0 comments |

Gmane