Meta Elements

Discussions and requests related to new CMSimple features, plugins, templates etc. and how to develop.
Please don't ask for support at this forums!
Post Reply
cmb
Posts: 14225
Joined: Tue Jun 21, 2011 11:04 am
Location: Bingen, RLP, DE
Contact:

Meta Elements

Post by cmb » Mon Jan 27, 2014 6:48 pm

Hello Community,

HTML5 is about to disallow arbitrary values for the name attribute of meta elements. In the Candidate Recommendation only a few such values are supported as standard: "application-name", "author", "description", "generator" and "keywords". Further values might be added in the future, however.

We should keep an eye on the development of HTML5 in this regard, as currently "publisher" and "robots" are not standardized (IOW: are not allowed). The latter has been already proposed, but it seems nobody cares about the former. For compliance we might consider to remove at least meta_publisher from the configuration.

Comments?

Christoph
Christoph M. Becker – Plugins for CMSimple_XH

svasti
Posts: 1660
Joined: Wed Dec 17, 2008 5:08 pm

Re: Meta Elements

Post by svasti » Tue Feb 18, 2014 11:19 pm

I have deleted "publisher" in cmsimple-xh.org, as it produces a validation error. I propose to kill it. Could be revived anytime again if necessary.

cmb
Posts: 14225
Joined: Tue Jun 21, 2011 11:04 am
Location: Bingen, RLP, DE
Contact:

Re: Meta Elements

Post by cmb » Sun May 04, 2014 4:06 pm

I have removed meta_publisher from the configuration (and the related entries from the language and meta language files) (r1263). That won't remove the setting for updates, but that shouldn't be a real problem.
Christoph M. Becker – Plugins for CMSimple_XH

Termin
Posts: 101
Joined: Thu Jan 27, 2011 8:55 am
Contact:

Re: Meta Elements

Post by Termin » Sat May 17, 2014 8:32 am

On each page should be something like this.

Code: Select all

<div span itemscope itemtype="http://schema.org/Article"></span>
<span itemprop="name" content="Net Neutrality - Senator Michael Bennet"></span>
 
<span itemprop="articleSection" content="News"></span>
<span itemprop="datePublished" content="2014-03-20"></span>
<span itemprop="person" content="Michael Bennet"></span>
<span itemprop="affiliation" content="US Senate"></span>
 
<span itemprop="audience" content="journalists, politicians, editors, writers, content providers, net neutrality, capital hill, fcc, tech, free speech"></span>
 
<span itemprop="genre" content="net neutrality, news, internet, politics, senate, fcc, tech, broadband"></span>
 
<span itemprop="keywords" content="net neutrality, senator, michael bennet, response, internet, fcc, on record, tech, broadband"></span>
 
<span itemprop="about" content="Senator Michael Bennet responds to letter about Net Neutrality"></span>
 
<span itemprop="image" content="net neutrality" img src="images/blog/Net_Neutrality_Bennet.png"></span>
 
<span itemprop="articleBody">AAAARRRRTTTTIIIIICCCCLLLLEEEE</span>
 
<span itemprop="publisher" itemscope itemtype="http://schema.org/Organization"> <meta itemprop="name" content="Harness Your Life">
<a rel="publisher" href="https://plus.google.com/+HarnessyourlifeHyL"></a></span>
 
<span itemprop="author" itemscope itemtype="http://schema.org/Person"> <meta itemprop="name" content="Sean Hammond">
<a rel="author" href="https://plus.google.com/+SeanHammondIsRad"></a></span>
 
</div>

cmb
Posts: 14225
Joined: Tue Jun 21, 2011 11:04 am
Location: Bingen, RLP, DE
Contact:

Re: Meta Elements

Post by cmb » Sat May 17, 2014 2:52 pm

I have some doubts regarding doing this in the core of CMSimple_XH.On one hand, there are several similar "standards" related to such semantic markup, such as Microformats, RDFa and Microdata. AFAIK the latter is the most recent one and is endorsed by the WHATWG, though not (yet) by the W3C. On the other hand, and this seems to be more important, it is not clear, which data should be supported, and where to take it from. Much of it has to be entered manually by the user, and I presume that not many users will make use of it, anyway.

So I'd like to suggest leaving this job to a plugin. Technically that shouldn't be a problem, as the somewhat similar meta_tags is also realized as a plugin. Handling such semantic markup with a plugin has furthermore the advantage, that there could be different plugins, and time might show which of these plugins/formats are really of interest to users (and search engines).

Is anybody interested in writing such a plugin?

BTW, there is a related thread about SEO: Google Rich Snippets.
Christoph M. Becker – Plugins for CMSimple_XH

Post Reply