FW: New Version Notification for draft-nottingham-site-meta-01

[Eran Hammer-Lahav]

FYI.

http://www.ietf.org/internet-drafts/draft-nottingham-site-meta-01.txt



Begin forwarded message:

> From: IETF I-D Submission Tool <idsubmission@...>
> Date: 10 February 2009 11:03:13 PM
> To: mnot@...
> Cc: eran@...
> Subject: New Version Notification for draft-nottingham-site-meta-01
>
>
> A new version of I-D, draft-nottingham-site-meta-01.txt has been
> successfuly submitted by Mark Nottingham and posted to the IETF
> repository.
>
> Filename:      draft-nottingham-site-meta
> Revision:      01
> Title:                 Host Metadata for the Web
> Creation_date:         2009-02-10
> WG ID:                 Independent Submission
> Number_of_pages: 12
>
> Abstract:
> This memo describes a method for locating host-specific metadata for
> the Web.
>
>
>
> The IETF Secretariat.
>
>

--
Mark Nottingham     http://www.mnot.net/

_______________________________________________
Apps-Discuss mailing list
Apps-Discuss@...
https://www.ietf.org/mailman/listinfo/apps-discuss

[Phil Archer-3]

I'm well aware of the discussion raging over the scope/origin issue but
here are a couple of minor comments on other matters in the I-D.

Nit:
End of section 3.1 http://example.com/me should be http://example.com/terms

More substantive point 1:

Given this URI:

http://example.com/~user/index.php

What is the WKL (and therefore host-meta scope) for this?

If it's http://example.com/~user/host-meta then agents have to recognise
the ~user convention.

If it's http://example.com/host-meta (more likely) then presumably any
linked resources will apply to all users unless otherwise stated?

Or am I missing something to do with template URIs here?

Point 2:

Should existing rel types be permissible? e.g. could one link to a
stylesheet using host-meta? I realise that this isn't the intention but
would it be permissible?

Maybe the reference to the HTTP Link: registry for rel types could be
made more explicit in this regard?

Section 3.1 says:

The "Link" host-meta field uses the syntax of the Link HTTP header-
field [I-D.nottingham-http-link-header] to convey links whose context
is the entire authority, rather than a single resource.

Could it say:

The "Link" host-meta field uses the syntax *and relationship types* of
the Link HTTP header-field [I-D.nottingham-http-link-header] to convey
links whose context is the entire authority, rather than a single resource.

And I'll leave the authority issue aside for now (POWDER makes its scope
explicit so the point is moot from that narrow perspective).

That's it for now.

Phil.

--
Phil Archer
http://philarcher.org/

Eran Hammer-Lahav wrote:

> FYI.
>
> http://www.ietf.org/internet-drafts/draft-nottingham-site-meta-01.txt
>
>
>
> Begin forwarded message:
>
>> From: IETF I-D Submission Tool <idsubmission@...>
>> Date: 10 February 2009 11:03:13 PM
>> To: mnot@...
>> Cc: eran@...
>> Subject: New Version Notification for draft-nottingham-site-meta-01
>>
>>
>> A new version of I-D, draft-nottingham-site-meta-01.txt has been
>> successfuly submitted by Mark Nottingham and posted to the IETF
>> repository.
>>
>> Filename:      draft-nottingham-site-meta
>> Revision:      01
>> Title:                 Host Metadata for the Web
>> Creation_date:         2009-02-10
>> WG ID:                 Independent Submission
>> Number_of_pages: 12
>>
>> Abstract:
>> This memo describes a method for locating host-specific metadata for
>> the Web.
>>
>>
>>
>> The IETF Secretariat.
>>
>>
>
>
> --
> Mark Nottingham     http://www.mnot.net/
>
> _______________________________________________
> Apps-Discuss mailing list
> Apps-Discuss@...
> https://www.ietf.org/mailman/listinfo/apps-discuss
>