Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Drop requirement to register meta[name] extensions #2229

Merged
merged 4 commits into from
Feb 8, 2017
Merged

Drop requirement to register meta[name] extensions #2229

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
de53c29
Drop requirement to register meta[name] extensions
sideshowbarker Jan 2, 2017
90faf75
Respond to remaining review comments
sideshowbarker Feb 5, 2017
4566e1f
Respond to review comments
sideshowbarker Feb 8, 2017
c21b0a1
nits
annevk Feb 8, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
59 changes: 26 additions & 33 deletions source
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -531,8 +531,7 @@
can then look for and process.</p></li>

<li><p>Authors can use the <code data-x="meta">&lt;meta name="" content=""></code> mechanism to
include page-wide metadata by registering <span data-x="concept-meta-extensions">extensions to
the predefined set of metadata names</span>.</p></li>
include page-wide metadata.</p></li>

<li><p>Authors can use the <code data-x="attr-hyperlink-rel">rel=""</code> mechanism to annotate
links with specific meanings by registering <span data-x="concept-rel-extensions">extensions to
Expand Down Expand Up @@ -13201,12 +13200,26 @@ interface <dfn>HTMLMetaElement</dfn> : <span>HTMLElement</span> {

<h5>Other metadata names</h5>

<p><dfn data-x="concept-meta-extensions">Extensions to the predefined set of metadata names</dfn>
may be registered in the <a href="https://wiki.whatwg.org/wiki/MetaExtensions">WHATWG Wiki
MetaExtensions page</a>. <ref spec=WHATWGWIKI></p>
<p>Anyone can create and use their own <dfn data-x="concept-meta-extensions">extensions to the
predefined set of metadata names</dfn>. There is no requirement to register such extensions.</p>
Copy link
Member

@zcorpan zcorpan Jan 3, 2017 •
edited by sideshowbarker
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more. 

+  <p>Anyone can create and use their own <dfn data-x="concept-meta-extensions">extensions to the
+  predefined set of metadata names</dfn>. There is no requirement to register such extensions.</p>

I think this should have some caveats:

  • When the intended value is a URL, encourage using <link rel> instead.
  • Names that have UA processing should be proposed to be added to the spec so it can become a standard metadata name if there is enough interest from other vendors.

Yes, agreed. Will update the PR to add those refinements.


<p>Anyone is free to edit the WHATWG Wiki MetaExtensions page at any time to add a type. These new
names must be specified with the following information:</p>
<p>However, if the anticipated metadata name is a <span>URL</span>, registering the value as an
<span data-x="concept-rel-extensions">extension to the predefined set of link types</span> instead
is encouraged.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You mean metadata value, right?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is basically the requirement that you remove below, but restated to be less of a requirement.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more. 

+  <p>However, if the anticipated metadata name is a <span>URL</span>, registering the value as an
+  <span data-x="concept-rel-extensions">extension to the predefined set of link types</span> instead
+  is encouraged.</p>

No, it’s a different requirement, right? The one I removed was about registering meta name values. But the language about registering link rel values (which the spec still requires)—it’s saying, “Since the value is a URL, then rather than using meta name for this thing at all, use link rel instead (and register the URL as a rel value).“

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if the meta name is not a URL, but the meta value is? Where do we encourage the link element then? It seems that went missing and it seems important to keep.


<p>Furthermore, if the anticipated metadata name is something expected to have processing
requirements in user agents, proposing it as a new <a href="#standard-metadata-names">standard
metadata name</a> instead is encouraged—to find out if there's enough interest among user-agent
implementors in actually implementing support for it.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We use spaces around "—" (added to https://wiki.whatwg.org/wiki/Style). "User-agent implementors" -> "user agents".


<p>Also, before creating and using a new metadata name, consulting the <a
href="https://wiki.whatwg.org/wiki/MetaExtensions">WHATWG Wiki MetaExtensions page</a> is
encouraged—to avoid choosing a metadata name that's actually already in use, and to avoid
unnecessarily duplicating the purpose of any metadata names that are already in use. <ref
spec=WHATWGWIKI></p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spaces again. s/actually// s/unnecessarily//

There's a third reason. To avoid new standardized names clashing with your chosen name.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a third reason. To avoid new standardized names clashing with your chosen name.

Added


<p>Anyone is free to edit the WHATWG Wiki MetaExtensions page at any time to add a metadata name.
New metadata names can be specified with the following information:</p>

<dl>

Expand All @@ -13231,8 +13244,8 @@ interface <dfn>HTMLMetaElement</dfn> : <span>HTMLElement</span> {
<dt>Synonyms</dt>

<dd><p>A list of other names that have exactly the same processing requirements. Authors should
not use the names defined to be synonyms, they are only intended to allow user agents to support
legacy content. Anyone may remove synonyms that are not used in practice; only names that need to
not use the names defined to be synonyms (they are only intended to allow user agents to support
legacy content). Anyone may remove synonyms that are not used in practice; only names that need to
be processed as synonyms for compatibility with legacy content are to be registered in this
way.</p></dd>

Expand Down Expand Up @@ -13267,8 +13280,8 @@ interface <dfn>HTMLMetaElement</dfn> : <span>HTMLElement</span> {
<p>If a metadata name is found to be redundant with existing values, it should be removed and
listed as a synonym for the existing value.</p>

<p>If a metadata name is registered in the "proposed" state for a period of a month or more
without being used or specified, then it may be removed from the registry.</p>
<p>If a metadata name is added in the "proposed" state for a period of a month or more without
being used or specified, then it may be removed from the WHATWG Wiki MetaExtensions page.</p>

<p>If a metadata name is added with the "proposed" status and found to be redundant with
existing values, it should be removed and listed as a synonym for the existing value. If a
Expand All @@ -13282,25 +13295,6 @@ interface <dfn>HTMLMetaElement</dfn> : <span>HTMLElement</span> {

</dl>

<div w-nodev>

<p>Conformance checkers must use the information given on the WHATWG Wiki MetaExtensions page to
establish if a value is allowed or not: values defined in this specification or marked as
"proposed" or "ratified" must be accepted, whereas values marked as "discontinued" or not listed
in either this specification or on the aforementioned page must be rejected as invalid.
Conformance checkers may cache this information (e.g. for performance reasons or to avoid the use
of unreliable network connectivity).</p>

<p>When an author uses a new metadata name not defined by either this specification or the Wiki
page, conformance checkers should offer to add the value to the Wiki, with the details described
above, with the "proposed" status.</p>

</div>

<p>Metadata names whose values are to be <span data-x="URL">URLs</span> must not be proposed or
accepted. Links must be represented using the <code>link</code> element, not the <code>meta</code>
element.</p>



<h5>Pragma directives</h5>
Expand Down Expand Up @@ -112117,9 +112111,8 @@ if (s = prompt('What is your name?')) {
unnecessary. Omit it altogether.</p></dd>

<dt><dfn><code data-x="attr-head-profile">profile</code></dfn> on <code>head</code> elements</dt>
<dd><p>When used for declaring which <code>meta</code> terms are
used in the document, unnecessary; omit it altogether, and <span
data-x="concept-meta-extensions">register the names</span>.</p></dd>
<dd><p>When used for declaring which <code>meta</code> terms are used in the document,
unnecessary; omit it altogether.</p></dd>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the other use again? Should this not basically just not be used?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[about the profile attribute for the html element]

What is the other use again? Should this not basically just not be used?

OK, I changed it to just an unqualified “Unnecessary. Omit it altogether.”

<dd><p>When used for triggering specific user agent behaviors: use
a <code>link</code> element instead.</p></dd>

Expand Down