Vocabularies for Technical Publishing

Hi all,

I'm writing about the recently posted proposal for vocabularies for
technical publishing<http://blog.schema.org/2012/06/newvocabularies-for-technical.html>
.

First off, let me say how excited I am to see this proposal. I'm interested
in improving the discoverability of technical articles about Drupal and its
modules, and had already proposed using Schema.org markup to do this
in an article
for IBM developerWorks<https://www.ibm.com/developerworks/opensource/library/x-html5microdata2/>
.

I will be helping some of the more high profile Drupal blogs implement this
(with the idea of extending to all blogs once it's been tested) and I would
like to use the newly proposed terms if possible.

A couple of things I noticed:

1. The expected type for aboutProduct is Product, which is an item.
However, in the description it goes on to describe how a string should be
formatted. The description should be clarified, the string formatting
instructions apply to the "name" property of the Product item.

2. The example of the "about" property uses a convention that I believe has
been discussed before... it uses the "url" property as the identifier which
"informs where to get more information on the concept".

    <span itemprop="about" itemscope itemtype="
http://schema.org/CreativeWork">
      <meta itemprop="name" content="SharePoint - Development and
Programming"/>
      <meta itemprop="url" content="
http://msdn.microsoft.com/enus/sharepoint/aa905688.aspx"/>
    </span>

    To me, it would make sense to handle this with the same pattern that
has been proposed for External
Enumeration<http://www.w3.org/wiki/WebSchemas/ExternalEnumerations>
.

    <span itemprop="about" itemscope itemtype="
http://schema.org/CreativeWork" itemid="
http://msdn.microsoft.com/enus/sharepoint/aa905688.aspx">
      <meta itemprop="name" content="SharePoint - Development and
Programming"/>
    </span>

Cheers,
Lin




-- 
Lin Clark
Drupal Consultant

lin-clark.com
twitter.com/linclark