anchor parameter, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard
Ian Hickson wrote: ... Unless there are really strong use cases, I think that the anchor= attribute should be dropped. In practice, implementations today ignore that attribute, which would mean that, e.g., a rel=stylesheet;anchor=a link would fail to have the right effect. If it is kept, then the right behaviour for how this should integrate with style sheet linking should be defined in great detail. ... Could you please elaborate what the right effect is, and how current implementations fail for that? It appears to me that anchor is not relevant for every single link relation, but that doesn't mean it's not useful at all. BR, Julian ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
Re: anchor parameter, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard
Ian Hickson wrote: ... Could you please elaborate what the right effect is, and how current implementations fail for that? Well unless I'm mistaken, if we have a resource A that has: Link: B; rel=stylesheet; anchor=C ...then that means we have a link: C - stylesheet - B ...which means that applying the style sheet to A would be wrong. Yet that is what UAs that support Link: would presumably do. Of the five UAs I checked, two seem to implement the Link header. Both fail to consider the anchor. To make Link headers useful in processing by HTML user agents, lots of additional implementation work is needed anyway; so I don't see this as a big problem. That being said, it probably would be good if the spec gave an example that anchor can be more than a fragment identifier, and thus recipients need to handle it -- it's not optional. It appears to me that anchor is not relevant for every single link relation, but that doesn't mean it's not useful at all. I don't see how it can't be relevant... if the link relation is between two resources, then acting as if it was a relationship between others seems wrong. Right; it *is* relevant if it's more than a fragment identifier, and it would be good if the spec stated that clearly. BR, Julian ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
Re: IETF74 T-Shirt Art Donated to IETF Trust
Marshall Eubanks wrote: If the IETF sold 100 shirts we would IMO be doing well. If we sold 1000, we would be doing spectacularly well IMHO. That would net $ 5000. That's less than ten registrations at a meeting. I am neutral about whether or not we do this, but please don't imagine that it will supplant registration fees or otherwise lead to sudden riches. I'd be suprised if we sold more than a 100 shirts. I see this primarily as a service to attendees, not as a way to generate money. You get a shirt for free, if you want a 2nd one for whatever reason, you can buy it. The IETF gets a few $$ for the trouble. Henk -- -- Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.xs4all.nl/~henku P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The NetherlandsThe NetherlandsMobile: +31.6.55861746 -- Belgium: an unsolvable problem, discussed in endless meetings, with no hope for a solution, where everybody still lives happily. ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
RE: IETF74 T-Shirt Art Donated to IETF Trust
Hi, Though, I think IETF has been always in the lavanguardia of fashion, I think Henk is absolutely right. Let people have their t-shirt if they want to. As long as there is no risk for the IETF. Who would that hurt? The money goes for a good cause - making the Internet work. Cheers, Jonne. -Original Message- From: ext Henk Uijterwaal Sent: 02/08/2009 12:53:02 Cc: ietf@ietf.org Subject: Re: IETF74 T-Shirt Art Donated to IETF Trust Marshall Eubanks wrote: If the IETF sold 100 shirts we would IMO be doing well. If we sold 1000, we would be doing spectacularly well IMHO. That would net $ 5000. That's less than ten registrations at a meeting. I am neutral about whether or not we do this, but please don't imagine that it will supplant registration fees or otherwise lead to sudden riches. I'd be suprised if we sold more than a 100 shirts. I see this primarily as a service to attendees, not as a way to generate money. You get a shirt for free, if you want a 2nd one for whatever reason, you can buy it. The IETF gets a few $$ for the trouble. Henk -- -- Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.xs4all.nl/~henku P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The NetherlandsThe NetherlandsMobile: +31.6.55861746 -- Belgium: an unsolvable problem, discussed in endless meetings, with no hope for a solution, where everybody still lives happily. ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
Re: IETF74 T-Shirt Art Donated to IETF Trust
And, maybe more importantly, the message of IETF's work spreads. In the case of IETF 74.shirt, it's the IPv6 transition message that spreads everytime someone wears their shirt. Gregory On 8/2/09, Henk Uijterwaal h...@ripe.net wrote: Marshall Eubanks wrote: If the IETF sold 100 shirts we would IMO be doing well. If we sold 1000, we would be doing spectacularly well IMHO. That would net $ 5000. That's less than ten registrations at a meeting. I am neutral about whether or not we do this, but please don't imagine that it will supplant registration fees or otherwise lead to sudden riches. I'd be suprised if we sold more than a 100 shirts. I see this primarily as a service to attendees, not as a way to generate money. You get a shirt for free, if you want a 2nd one for whatever reason, you can buy it. The IETF gets a few $$ for the trouble. Henk -- -- Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.xs4all.nl/~henku P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The NetherlandsThe NetherlandsMobile: +31.6.55861746 -- Belgium: an unsolvable problem, discussed in endless meetings, with no hope for a solution, where everybody still lives happily. ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf -- Sent from my mobile device IETF related email from Gregory M. Lebovitz Juniper Networks ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
Re: IETF74 T-Shirt Art Donated to IETF Trust
In the case of IETF 74.shirt, it's the IPv6 transition message that spreads everytime someone wears their shirt. Great! I'll get two, and wear them both every night in bed. Adrian ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
