schema.org/ext/events2.html
author scor <scorlosquet@gmail.com>
Fri, 14 Mar 2014 12:03:13 -0400
changeset 179 b4c3ad199322
parent 133 fc09e465d53f
permissions -rw-r--r--
Add example inspired from stackoverflow for QA proposal
<!DOCTYPE html>
<html>
  <head>
    <title>RDFa-RDFS config for Events (part 2) schema</title>
    <style type="text/css">
      span.h {
        padding-left: 0px;
        font-weight: bold;
      }
      span {
        display: block;
        padding-left: 10px;
      }
    </style>
  </head>
  <body>

   <h1>Events (part 2) schema</h1>

  <p>See <a href="www.w3.org/wiki/WebSchemas/EventSchemaUpdate">Wiki overview</a>.</p>


    <!-- make some new assertions about existing Event type -->
    <div typeof="rdfs:Class" resource="http://schema.org/Event">
    </div>

    <div typeof="rdfs:Class" resource="http://schema.org/EventStatusType">
      <span class="h" property="rdfs:label">EventStatusType</span>
      <span property="rdfs:comment">EventStatusType is an enumeration type whose instances represent several states that an Event may be in.</span>
      <span>Subclass of: <a property="rdfs:subClassOf" href="http://schema.org/Enumeration">Enumeration</a></span>
    </div>
  

    <!-- properties -->

    <div typeof="rdf:Property" resource="http://schema.org/eventStatus">
      <span class="h" property="rdfs:label">eventStatus</span>
      <span property="rdfs:comment">An eventStatus of an event represents its status; particularly useful when an event is cancelled or rescheduled.</span>
      <span>Domain: <a property="http://schema.org/domain" href="http://schema.org/Event">Event</a></span>
      <span>Range: <a property="http://schema.org/range" href="http://schema.org/EventStatusType">EventStatusType</a></span>
    </div>

    <div typeof="rdf:Property" resource="http://schema.org/previousStartDate">
      <span class="h" property="rdfs:label">previousStartDate</span>
      <span property="rdfs:comment">Used in conjunction with eventStatus for rescheduled or cancelled events. This property contains the previously scheduled start date. For rescheduled events, the startDate property should be used for the newly scheduled start date. In the (rare) case of an event that has been postponed and rescheduled multiple times, this field may be repeated.</span>
      <span>Domain: <a property="http://schema.org/domain" href="http://schema.org/Event">Event</a></span>
      <span>Range: <a property="http://schema.org/range" href="http://schema.org/Date">Date</a></span>
    </div>

    <!-- extending a property added for LRMI ... we should change 'content' to 'item' -->

    <div typeof="rdf:Property" resource="http://schema.org/typicalAgeRange">
      <span class="h" property="rdfs:label">typicalAgeRange</span>
      <span property="rdfs:comment">The typical expected age range, e.g. '7-9', '11-'.</span>
      <span>Domain: <a property="http://schema.org/domain" href="http://schema.org/Event">Event</a></span>
    </div>


    <!-- enumerated instances -->

    <div typeof="http://schema.org/EventStatusType" resource="http://schema.org/EventScheduled">
      <span class="h" property="rdfs:label">EventScheduled</span>
      <span property="rdfs:comment">The event is taking place or has taken place on the startDate as scheduled. Use of this value is optional, as it is assumed by default.</span>
      <span>type: <a href="http://schema.org/EventStatusType">EventStatusType</a></span>
    </div>

    <div typeof="http://schema.org/EventStatusType" resource="http://schema.org/EventCancelled">
      <span class="h" property="rdfs:label">EventCancelled</span>
      <span property="rdfs:comment">The event has been cancelled. If the event has multiple startDate values, all are assumed to be cancelled. Either startDate or previousStartDate may be used to specify the event’s cancelled date(s).</span>
      <span>type: <a href="http://schema.org/EventStatusType">EventStatusType</a></span>
    </div>


    <div typeof="http://schema.org/EventStatusType" resource="http://schema.org/EventPostponed">
      <span class="h" property="rdfs:label">EventPostponed</span>
      <span property="rdfs:comment">The event has been postponed and no new date has been set. The event’s previousStartDate should be set.</span>
      <span>type: <a href="http://schema.org/EventStatusType">EventStatusType</a></span>
    </div>


    <div typeof="http://schema.org/EventStatusType" resource="http://schema.org/EventRescheduled">
      <span class="h" property="rdfs:label">EventRescheduled</span>
      <span property="rdfs:comment">The event has been rescheduled. The event’s previousStartDate should be set to the old date and the startDate should be set to the event’s new date. (If the event has been rescheduled multiple times, the previousStartDate property may be repeated.)</span>
      <span>type: <a href="http://schema.org/EventStatusType">EventStatusType</a></span>
    </div>



    <!-- let's add in two more ItemAvailability enums, to support event availibility. -->
 
    <!-- actually, no, we'll do this in the original config file ... --> 

<!-- not needed, assuming other approach works:

    <div typeof="http://schema.org/ItemAvailability" resource="http://schema.org/SoldOut">
      <span class="h" property="rdfs:label">SoldOut</span>
      <span property="rdfs:comment">The event has sold out.</span>
      <span>type: <a href="http://schema.org/ItemAvailability">ItemAvailability</a></span>
    </div>

    <div typeof="http://schema.org/ItemAvailability" resource="http://schema.org/LimitedAvailability">
      <span class="h" property="rdfs:label">LimitedAvailability</span>
      <span property="rdfs:comment">The event has limited availability.</span>
      <span>type: <a href="http://schema.org/ItemAvailability">ItemAvailability</a></span>
    </div>
-->

  </body>
</html>