Google グループは Usenet の新規の投稿と購読のサポートを終了しました。過去のコンテンツは引き続き閲覧できます。
Dismiss

Re: Why does the W3C feed validator flag this?

閲覧: 6 回
最初の未読メッセージにスキップ

David E. Ross

未読、
2018/03/13 22:25:492018/03/13
To:
On 3/13/2018 1:42 PM, Luu wrote:
> Hi
>
> Can someone tell me why the W3C validator is giving me these kinds of errors?
>
> href must be a full URL: https://i1.sndcdn.com/artworks-000315700317-eyx9n5-large.jpg
>
> This looks like a perfectly valid URL as far as I can tell
>
> Full page here
>
> https://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fespresso.compassheart.com%2Fca
> phe.rss
>
> Thanks in advance
>

I see several problems with the "full page".

First of all, the URI was broken at a line-break; and only the part in
the first line was recognized. This was 404. I had to copy both lines
and piece the URI back together. Per RFC 3986, the URI should be
bracketed with < and >. This is especially important with long URIs.

Next, the use of escaped characters (e.g., %2F for /) is unnecessary and
might cause problems. The W3C validators work better with HTML markups
for characters that might otherwise require escaping (e.g., &amp; for &,
&lt; for <).

--
David E. Ross
<http://www.rossde.com/>

President Trump: Please stop using Twitter. We need
to hear your voice and see you talking. We need to know
when your message is really your own and not your attorney's.

Ed Mullen

未読、
2018/03/14 14:38:332018/03/14
To:
On 3/14/2018 at 1:47 PM, darius created this epitome of digital genius:
> "David E. Ross" <nob...@nowhere.invalid> wrote in
> news:p8a17c$bnb$1...@news.albasani.net...
>
>
>> I see several problems with the "full page".
>>
>> First of all, the URI was broken at a line-break; and only the part
>> in the first line was recognized. This was 404. I had to copy both
>> lines and piece the URI back together. Per RFC 3986, the URI should
>> be bracketed with < and >. This is especially important with long
>> URIs.
>>
>> Next, the use of escaped characters (e.g., %2F for /) is unnecessary
>> and might cause problems. The W3C validators work better with HTML
>> markups for characters that might otherwise require escaping (e.g.,
>> &amp; for &, &lt; for <).
>>
>
> Sorry, the newsreader line wrapped. The URL below is so you can see the result
> of the validation, it is not the problem
>
> https://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fespresso.compassheart.com%2Fcaphe.rss
>
> This is the line that the validator does not like
>
> <itunes:image href="https://i1.sndcdn.com/artworks-000315700317-eyx9n5-large.jpg"/>
>
> I don't understand why it does not like that.
>
I suspect the itunes:image part.

--
Ed Mullen
http://edmullen.net/
What's another word for thesaurus?

dorayme

未読、
2018/03/14 19:43:552018/03/14
To:
In article <b48foa....@news.alt.net>,
Above address on my Mac's Safari gets nothing; but my iTunes app
springs open! The iTunes app has big ears and heard itself mentioned.

itunes:image would be an unusual (proprietary) element.

Best to use very like:

<img
src="https://i1.sndcdn.com/artworks-000315700317-eyx9n5-large.jpg"
alt="">

--
dorayme

Osmo Saarikumpu

未読、
2018/03/15 5:55:292018/03/15
To:
On 14/03/2018 19:47, darius wrote:
> https://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fespresso.compassheart.com%2Fcaphe.rss
>
> This is the line that the validator does not like
>
> <itunes:image href="https://i1.sndcdn.com/artworks-000315700317-eyx9n5-large.jpg"/>
>
> I don't understand why it does not like that.

It's the 's' in the protocol (http_s_). See the discussion at:

https://github.com/rubys/feedvalidator/issues/16

--
Best wishes, Osmo

dorayme

未読、
2018/03/15 17:58:292018/03/15
To:
In article <p8dfuf$fp2$1...@dont-email.me>,
The latter gets a Safari can't open the page on my coputer. Whereas

<https://i1.sndcdn.com/artworks-000315700317-eyx9n5-large.jpg>

gets a cup of coffee.

What would you rather have first thing in the morning?

--
dorayme

Osmo Saarikumpu

未読、
2018/03/16 6:31:172018/03/16
To:
On 15/03/2018 23:58, dorayme wrote:
> The latter gets a Safari can't open the page on my coputer.

Well, even if it were true that Safari was written in CoffeeScript,¹ it
don't mean that she will open just any latte.

> Whereas
> <https://i1.sndcdn.com/artworks-000315700317-eyx9n5-large.jpg>
> gets a cup of coffee.

Can't prove it but, it's probably the difference betwixt latte and
espresso. Or a quirk in Safari, as I get with my FF as many cups as
there are hrefs pointing to them.

> What would you rather have first thing in the morning?

An early "can't open the page" is always refreshing, but nothing beats a
hot cup of Java :)

¹ http://coffeescript.org/
--
Best wishes, Osmo
新着メール 0 件