This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27388 - Use https://schema.org/ in examples if feasible
Summary: Use https://schema.org/ in examples if feasible
Status: RESOLVED INVALID
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: https://html.spec.whatwg.org/#article...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-21 11:19 UTC by contributor
Modified: 2014-11-22 06:58 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2014-11-21 11:19:52 UTC 
Specification: https://html.spec.whatwg.org/multipage/semantics.html
Multipage: https://html.spec.whatwg.org/multipage/#article-example
Complete: https://html.spec.whatwg.org/#article-example
Referrer: 

Comment:
Use https://schema.org/ in examples if feasible

Posted from: 78.21.122.251
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.65 Safari/537.36 OPR/26.0.1656.24
Comment 1 Mathias Bynens 2014-11-21 11:21:50 UTC 
schema.org now supports TLS, so it would be nice to use `itemtype="https://schema.org/…"` instead of the `http://` version in the spec examples, if that’s possible.

E.g. http://schema.org/BlogPosting and https://schema.org/BlogPosting return the same response/vocabulary, so I assume the URL change doesn’t change any semantics (but that may be wrong).
Comment 2 Ian 'Hixie' Hickson 2014-11-21 23:50:36 UTC 
Wait, what? That makes no sense. You can't just randomly change a vocabulary name. It's an opaque string. Those URLs could fail to resolve in DNS and it still wouldn't make any difference to anything. What gave you the idea that the resource at the end of the URL would be relevant to the meaning of the vocabulary?
Comment 3 Mathias Bynens 2014-11-22 06:58:20 UTC 
The whole strings-that-look-like-URLs-as-identifiers got me again.