Re: [apps-discuss] Working Group Last Call for draft-ietf-appsawg-file-scheme

All,

Apologies for my late response - I missed the original last call, and early 
follow-up.

I would be happy for this to go forward as-is, but I do have a couple of minor 
comments to offer (if only to prove I actually read it again!).

...

[Minor] In section 3, I'm finding the reference to "implementation" a bit vague 
(does this mean URI generators, parsers, or what?), though I suppose it's easy 
enough to figure from the context.

Suggest:

OLD:
3.  Operations on file URIs

    Implementations SHOULD, at a minimum, provide a read-like operation
    to return the contents of a file located by a file URI.  Additional
    operations MAY be provided, such as writing to, creating, and
    deleting files.  See the POSIX file and directory operations [POSIX]
    for examples of standardized operations that can be performed on
    files.

NEW:
3.  Operations on file URIs

    Implementations that provide dereferencing operations on file: URIs
    SHOULD, at a minimum, provide a read-like operation
    to return the contents of a file located by a file URI.  Additional
    operations MAY be provided, such as writing to, creating, and
    deleting files.  See the POSIX file and directory operations [POSIX]
    for examples of standardized operations that can be performed on
    files.

(I hope it's clear that "dereference" is used here in the sense of section 1.2.2 
of RFC3986 - https://tools.ietf.org/html/rfc3986#section-1.2.2)

...

[Minor] In section 3, the text "can only be dereferenced" seems a bit strong - 
in that it appears to prohibit dereferencing lon-local file URIs.

Suggest:

OLD:
    A file URI can only be dereferenced or translated to a local file
    path if it is local.  A file URI is considered "local" if it has a
    blank or no authority, or the authority is the special string
    "localhost".

NEW:
    A file URI can be dependably dereferenced or translated to a local file
    path only if it is local.  A file URI is considered "local" if it has a
    blank or no authority, or the authority is the special string
    "localhost".

...

(Section 6, aside: it's really strange for me to read "HP OpenVMS Systems 
Documentation" -- but of course, it's quite correct.)

...

Good work!

#g
--

On 02/11/2015 03:50, Murray S. Kucherawy wrote:
> Colleagues,
>
> This note starts a Working Group Last Call for draft-ietf-appsawg-file-scheme.
> This document has been with us for a while and feedback has fallen to a
> trickle.  We've gotten all the feedback from W3C that we expect, so we'd like to
> move it toward publication.
>
> Please provide review comments or expressions of support for the current version
> either on this list or privately to
> draft-ietf-appsawg-file-scheme.all@tools.ietf.org
> <mailto:draft-ietf-appsawg-file-scheme.all@tools.ietf.org> on or before November
> 20, 2015.  Be as detailed as possible.  The co-chairs need to determine if the
> document has working group consensus, which means we need to know people have
> read the latest version and agree with its content and with the idea that it is
> ready to proceed.  A simple “+1” doesn’t tell us anything.
>
> Also, if any participant has knowledge of IPR that needs to be declared on this
> work, please do so, as required by BCPs 78 and 79.
>
> Dave Crocker is fulfilling the duties of document shepherd.
>
> -MSK, APPSAWG co-chair
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>