Skip to content

Commit

Permalink
Meta: minor references cleanup
Browse files Browse the repository at this point in the history 
Use more HTTPS and drop obsolete HTML Differences reference.
  • Loading branch information
@annevk
annevk committed Jan 20, 2021
1 parent 8192944 commit 88de068
Show file tree
Hide file tree
Showing 2 changed files with 20 additions and 32 deletions.
5 changes: 2 additions & 3 deletions FAQ.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,6 @@ There are a number of ways to track changes to the standard:
* The Twitter feed: [@htmlstandard](https://twitter.com/htmlstandard)
* The [GitHub commits log](https://github.com/whatwg/html/commits)
* The standard is available in the [Git repository](https://github.com/whatwg/html/). You may use any Git client to check out the latest version and use your client's diff tools to compare revisions and see what has been changed.
* At a broader level, Anne and Simon once wrote a document that gave a high-level overview of changes to HTML over the last decade or so: https://html-differences.whatwg.org/

### What are the various versions of the HTML Standard?

Expand Down Expand Up @@ -395,7 +394,7 @@ Some people argue that in such cases, the `<span>` element should be used with a

In essence, the `<i>` and `<b>` elements convey distinct, though non-specific, semantics, which are to be determined by the reader in the context of their use. In other words, although they don't convey specific semantics by themselves, but instead they indicate that the content is somehow semantically distinct from its surroundings — leaving the interpretation of the semantics up to the reader.

This is further explained in the article [The `<b>` and `<i>` Elements](http://lachy.id.au/log/2007/05/b-and-i).
This is further explained in the article [The `<b>` and `<i>` Elements](https://lachy.id.au/log/2007/05/b-and-i).

Similarly, the `<small>` element is defined for content that is commonly typographically rendered in small print, and which is often referred to as "fine print"; that could include copyright statements, disclaimers and other legal text commonly found at the end of a document.

Expand All @@ -411,7 +410,7 @@ So, we can't really decide what the element should be based on past practice, li

This leaves the question of what is the most useful use we can put the element to, if we keep it. The conclusion so far has been that the most useful use for `<cite>` is as an element to allow typographic control over titles, since those are often made italics, and that semantic is roughly close to what it meant in previous versions, and happens to match at least one of the common uses for the element. Generally, however, names and titles aren't typeset the same way, so making the element apply to both would lead to confusing typography.

There are already many ways of marking up names already (e.g. the [hCard microformat](http://microformats.org/wiki/hcard), the microdata vCard vocabulary, `<span>` and class names, etc), if you really need it.
There are already many ways of marking up names already (e.g. the [hCard microformat](https://microformats.org/wiki/hcard), the microdata vCard vocabulary, `<span>` and class names, etc), if you really need it.

### Do you have any hints on how to use `<section>` and `<article>` and so on?

Expand Down
47 changes: 18 additions & 29 deletions source
View file
Original file line number Diff line number Diff line change
Expand Up @@ -15480,7 +15480,7 @@ interface <dfn>HTMLBodyElement</dfn> : <span>HTMLElement</span> {
newspaper article, a blog entry, a user-submitted comment, an interactive widget or gadget, or any
other independent item of content.</p>

<!-- for context regarding "site", see http://krijnhoetmer.nl/irc-logs/whatwg/20130306#l-152 -->
<!-- for context regarding "site", see https://krijnhoetmer.nl/irc-logs/whatwg/20130306#l-152 -->

<p>When <code>article</code> elements are nested, the inner <code>article</code> elements
represent articles that are in principle related to the contents of the outer article. For
Expand Down Expand Up @@ -25430,9 +25430,9 @@ document.body.appendChild(wbr);</code></pre>

<h5>Other link types</h5>

<p><dfn data-x="concept-rel-extensions">Extensions to the predefined set of link types</dfn> may be
registered in the <a
href="http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions">microformats
<p><dfn data-x="concept-rel-extensions">Extensions to the predefined set of link types</dfn> may
be registered in the <a
href="https://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions">microformats
wiki existing-rel-values page</a>. <ref spec=MFREL></p>

<p>Anyone is free to edit the <span data-x="">microformats wiki existing-rel-values page</span> at
Expand Down Expand Up @@ -25603,7 +25603,7 @@ document.body.appendChild(wbr);</code></pre>
</div>

<p>Types defined as extensions in the <a
href="http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions">microformats
href="https://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions">microformats
wiki existing-rel-values page</a> with the status "proposed" or "ratified" may be used with the
<code data-x="">rel</code> attribute on <code>link</code>, <code>a</code>, and <code>area</code>
elements in accordance to the "Effect on..." field. <ref spec=MFREL></p>
Expand Down Expand Up @@ -63599,7 +63599,7 @@ try {
When the filtering algorithm requires a pixel value from outside the source rectangle but inside
the original image data, then the value from the original image data must be used.</p>
<!-- see CORE-32111 and:
http://krijnhoetmer.nl/irc-logs/whatwg/20100818#l-737
https://krijnhoetmer.nl/irc-logs/whatwg/20100818#l-737
https://www.w3.org/Bugs/Public/show_bug.cgi?id=10799#c11
-->
<!-- createPattern() has a similar paragraph with different rules -->
Expand Down Expand Up @@ -68612,34 +68612,34 @@ Demos:
<!-- USE CASES

Getting data out of poorly written web pages
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-May/019595.html
https://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-May/019595.html

Allowing authors to keep track of where content originates
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-May/019620.html
https://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-May/019620.html

Helping people searching for content filtered by license
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-May/019668.html
https://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-May/019668.html

Allowing authors to annotate their documents to explain things for readers
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-May/019672.html
https://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-May/019672.html

Annotating structured data that HTML has no semantics for
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-May/019681.html
https://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-May/019681.html

Exposing known data types in a reusable way
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-May/019833.html
https://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-May/019833.html

Providing enhanced search results
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-May/019834.html
https://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-May/019834.html

Dragging or copying data between sites
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-May/019835.html
https://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-May/019835.html

Writing authoring tools and validators for custom microdata vocabularies
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-May/019839.html
https://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-May/019839.html

Removing the need for separate feeds
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-May/019884.html
https://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-May/019884.html

Use cases for which I haven't been able to find solutions
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-May/019886.html
Expand Down Expand Up @@ -78784,33 +78784,22 @@ dictionary <dfn>WindowPostMessageOptions</dfn> : <span>PostMessageOptions</span>
USVString <dfn data-x="dom-WindowPostMessageOptions-targetOrigin">targetOrigin</dfn> = "/";
};</code></pre>

<!-- for more features to add here, look here:
http://msdn.microsoft.com/workshop/author/dhtml/reference/objects/obj_window.asp
http://www.mozilla.org/docs/dom/domref/dom_window_ref.html
http://lxr.mozilla.org/mozilla/source/dom/public/idl/base/nsIDOMWindow.idl - scrollBy, etc
http://lxr.mozilla.org/mozilla/source/dom/public/idl/base/nsIDOMWindowInternal.idl - DOM level 0
-->

<dl class="domintro">

<dt><var>window</var> . <code subdfn data-x="dom-window">window</code></dt>
<dt><var>window</var> . <code subdfn data-x="dom-frames">frames</code></dt>
<dt><var>window</var> . <code subdfn data-x="dom-self">self</code></dt>

<dd>
<p>These attributes all return <var>window</var>.</p>
</dd>


<dt><var>window</var> . <code subdfn data-x="dom-document">document</code></dt>

<dd>
<p>Returns the <code>Document</code> associated with <var>window</var>.</p>
</dd>


<dt><var>document</var> . <code subdfn data-x="dom-document-defaultView">defaultView</code></dt>

<dd>
<p>Returns the <code>Window</code> object of the <span>active document</span>.</p>
</dd>
Expand Down Expand Up @@ -122652,7 +122641,7 @@ INSERT INTERFACES HERE
<dd><cite><a href="https://w3c.github.io/DOM-Parsing/">DOM Parsing and Serialization</a></cite>, T. Leithead. W3C.</dd>

<dt id="refsDOT">[DOT]</dt>
<dd>(Non-normative) <cite><a href="http://www.graphviz.org/content/dot-language">The DOT Language</a></cite>. Graphviz.</dd>
<dd>(Non-normative) <cite><a href="https://graphviz.org/doc/info/lang.html">The DOT Language</a></cite>. Graphviz.</dd>

<dt id="refsE163">[E163]</dt>
<dd><cite>Recommendation E.163 &mdash; Numbering Plan for The International Telephone Service</cite>, CCITT Blue Book, Fascicle II.2, pp. 128-134, November 1988.</dd>
Expand Down Expand Up @@ -122777,7 +122766,7 @@ INSERT INTERFACES HERE
<dd><cite><a href="https://w3c.github.io/reporting/">Reporting</a></cite>, D. Creager, I. Clelland, M. West. W3C.</dd>

<dt id="refsMFREL">[MFREL]</dt>
<dd><cite><a href="http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions">Microformats Wiki: existing rel values</a></cite>. Microformats.</dd>
<dd><cite><a href="https://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions">Microformats Wiki: existing rel values</a></cite>. Microformats.</dd>

<dt id="refsMIMESNIFF">[MIMESNIFF]</dt>
<dd><cite><a href="https://mimesniff.spec.whatwg.org/">MIME Sniffing</a></cite>, G. Hemsley. WHATWG.</dd>
Expand Down

0 comments on commit 88de068

Please sign in to comment.