W3C home > Mailing lists > Public > public-schemaorg@w3.org > September 2016

BlogPosting and Article - Helping Publshing Software perform better

From: Thad Guidry <thadguidry@gmail.com>
Date: Sat, 3 Sep 2016 12:01:04 -0500
Message-ID: <CAChbWaMVnZJNHJhT4pP1PNhc9sekAtxK3q7w2BjkQ2z5h08q2A@mail.gmail.com>
To: "schema.org Mailing List" <public-schemaorg@w3.org>
It has become increasingly hard to filter out true personal opinions from
regular news / media outlets when your just looking at the the Web as a
whole as search engines do, or with the Common Crawl.

I have opened this issue to address it, but also to encourage Publishers
and Publishing and Blogging Software developers to be aware of this issue
and how they can help resolve the problem with us.

Narrow the description for BlogPosting to be for 'personal'
https://github.com/schemaorg/schemaorg/issues/1343
----

There are numerous publishing platforms that all seem to use Article
instead of BlogPosting as their default content frame. Usage statistics
seem to indicate that they are using Article for both personal blogs and
news-y articles. This may stem from the confusing examples on BlogPosting
and where we already have issue #883
<https://github.com/schemaorg/schemaorg/issues/883> to address that.

I suggest that we narrow the BlogPosting definition to use the phrase

'A personal blog post.  For non-personal publishing such as news,
magazines, use Article instead.'

to help further clarify its intended usage and to help filter out true
personal opinions on topics from other news agencies, media houses,
publishers, etc that primarily use Article in their templates.

@scor <https://github.com/scor> @ErisDS <https://github.com/ErisDS> Further
the Publishing Software frameworks could help matters also by giving an
install option to choose the primary usecase, one of either a 'personal'
blog or for a 'news agency, media entity, or publisher' and informing the
user that template setup consequence between 'BlogPosting' or 'Article' as
the default content frame.


Thad
+ThadGuidry <https://www.google.com/+ThadGuidry>
Received on Saturday, 3 September 2016 17:01:34 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 3 September 2016 17:01:34 UTC