You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 30, 2019. It is now read-only.
If developers wish to provide more granular and specific semantics for the address element use of any of the various semantic web metadata schemas is suggested.
(By the way: I guess there should be a comma after "element")
I don’t think the spec should link to (and thereby endorse) a specific vocabulary inside the "spec part" (outside of examples) at all.
If the link must be there, I would suggest to move it to address example 7, which makes use of Schema.org.
If the link must be in that sentence, I would suggest to include it similar to the following way (because linking "schemas" to one specific vocabulary is rather unexpected, especially when the sentence speaks of "various" schemas):
use of any of the various semantic web metadata schemas (e.g., Schema.org) is suggested.
The text was updated successfully, but these errors were encountered:
https://www.w3.org/TR/2017/CR-html52-20170808/grouping-content.html#the-address-element
For
address
, it says:(By the way: I guess there should be a comma after "element")
Where "schemas" links to http://schema.org/.
I don’t think the spec should link to (and thereby endorse) a specific vocabulary inside the "spec part" (outside of examples) at all.
If the link must be there, I would suggest to move it to
address
example 7, which makes use of Schema.org.If the link must be in that sentence, I would suggest to include it similar to the following way (because linking "schemas" to one specific vocabulary is rather unexpected, especially when the sentence speaks of "various" schemas):
The text was updated successfully, but these errors were encountered: