Re: Vocabularies for Technical Publishing

In response to Josh...


1.       Yes, your markup appears to be valid. Itemprop<See%20-%20http:/www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#names:-the-itemprop-attribute> supports multiple values for an item.

This will make a good addition to the proposal as an example.



In addition to overloading Product value; another benefit of using "about" is for technologies that have multiple applications with different context. For example, JavaScript content may apply to many different scenarios. Here a technical article about Javascript may apply to Metro style application development and well and Internet Explorer.



Example:


<div itemscope itemtype ="http://schema.org/TechArticle">
<h1 itemprop="headline">Fundamentals of JavaScript</h1>

<div itemprop="about">
                <a href="http://msdn.microsoft.com/en-us/library/windows/apps/6974wx4d(v=vs.94).aspx" itemprop="url">Metro style apps</a>
</div>

<div itemprop="about">
                <a href="http://msdn.microsoft.com/en-us/library/ie/6974wx4d(v=vs.94).aspx" itemprop="url">Internet Explorer</a>
</div>
</div>





2.       I see the benefit of using a URI reference for currentModel so that statically built pages could benefit from it.  I understand this as being a pointer to the value rather than emitting the actual value.  It seems that this puts the heavy lifting on search engines to follow the pointer and read-in the value.
I see many examples with URL data type; however, I haven't found a practical example of how an URI reference is currently being used in this specific way...  Please reply with an active example if you know of one.
There is strong merit in having the option to specify currentModel. The value would be fairly straight forward to maintain for dynamically built content (php, aspx, etc.).   If using a URI reference is a viable alternative and there are practical examples in use today, then I'll update the proposal with an included example.

-Kenley



Joshua Wulf <jwulf@redhat.com<mailto:jwulf@redhat.com?Subject=Re%3A%20Vocabularies%20for%20Technical%20Publishing&In-Reply-To=%253Cb3c509c0-1d16-4eae-8b6a-e9ffe67c34ac%40zmail16.collab.prod.int.phx2.redhat.com%253E&References=%253Cb3c509c0-1d16-4eae-8b6a-e9ffe67c34ac%40zmail16.collab.prod.int.phx2.redhat.com%253E>>
Date: Fri, 22 Jun 2012 18:24:53 -0400 (EDT)
To: public-vocabs@w3.org<mailto:public-vocabs@w3.org?Subject=Re%3A%20Vocabularies%20for%20Technical%20Publishing&In-Reply-To=%253Cb3c509c0-1d16-4eae-8b6a-e9ffe67c34ac%40zmail16.collab.prod.int.phx2.redhat.com%253E&References=%253Cb3c509c0-1d16-4eae-8b6a-e9ffe67c34ac%40zmail16.collab.prod.int.phx2.redhat.com%253E>
Message-ID: <b3c509c0-1d16-4eae-8b6a-e9ffe67c34ac@zmail16.collab.prod.int.phx2.redhat.com>

Great initiative, and I'm keenly interested in its development.



I have a couple of questions.



1. Can you put multiple product versions inside the same declaration? The same procedure might be valid for several different iterations of a product (and not valid for other specific iterations, obviously).



So, for example:



<div itemprop="about" itemscope itemtype="http://schema.org/Product">

      <p>

        <strong>Applies to:</strong>

        <span itemprop="name">Microsoft SQL Server 2008 R2</span>

        <span itemprop="name">Microsoft SQL Server 2008 R3</span>

        <span itemprop="name">Microsoft SQL Server 2008 R4</span>

      </p>

      <meta itemprop="model" content="2008 R2"/>

      <meta itemprop="model" content="2008 R3"/>

      <meta itemprop="model" content="2008 R4"/>

      <meta itemprop="currentModel" content="2012"/>

</div>





2. Is it possible to specify the currentModel as a URI reference? So then you only have to update it in one place and voila, all your htmlz are updated - without having to republish everything or implement dynamic injection.



It seems like the other metadata is data about the page or entities described on or involved in production of the page; but the currentModel item is metadata about another entity - albeit related - which doesn't necessarily exist when the page is produced, /and/ changes over time.



- Josh