added new vocab in 1.0 planning section
authorDan Brickley <danbri@danbri.org>
Fri, 15 Jun 2012 18:30:20 +0200
changeset 28 0430189a2180
parent 27 12e2dad3cd1b
child 29 5785c1c1397b
added new vocab in 1.0 planning section
schema.org/drafts/changes.html
--- a/schema.org/drafts/changes.html	Wed May 16 16:25:38 2012 +0200
+++ b/schema.org/drafts/changes.html	Fri Jun 15 18:30:20 2012 +0200
@@ -8,18 +8,21 @@
 
 <p>
 	This document describes changes to the schema.org schema. It serves as a summary of draft/pending changes, and later as a record of updates. For more detail of 
-	proposals and drafts see the <a href="http://www.w3.org/wiki/WebSchemas/SchemaDotOrgProposals">proposals</a> listing.
+	proposals and drafts see the <a href="http://www.w3.org/wiki/WebSchemas/SchemaDotOrgProposals">proposals</a> listing. Specific pending changes are <a href="#pending">listed below</a>.
 </p>	
+
+<h2>Recent Changes</h2>
+
+<p>A summary of major changes to the schema.org vocabulary. We may fix some smaller bugs and typos without noting here, but in general, this is the document where specific draft changes are queued and documented.</p>
+
+		
+	<h3>Edition 0.91</h3>
 	
-<h2>Changes Pending (drafts)</h2>
-
-<h3>For Edition 0.91</h3>
-	
-<p>Version 0.91 scheduled for mid-April 2012, to include resolution of <a href="http://www.w3.org/wiki/WebSchemas/Singularity">Singularity</a> issue (singular form of property names);
+<p>Version 0.91 was scheduled for mid-April 2012, to include resolution of <a href="http://www.w3.org/wiki/WebSchemas/Singularity">Singularity</a> issue (singular form of property names);
 	*URL/*Url property spelling conventions, the addition of <a href="http://www.w3.org/wiki/WebSchemas/Comment">Comment</a>, and <a href="http://www.w3.org/wiki/WebSchemas/SoftwareApplicationSchema">SoftwareApplication</a>.
 </p>	
 
-<p>Submitted for inclusion 2012-04-16</p>
+<p>These were submitted for inclusion 2012-04-16 went live during the following 7-10 days.</p>
 
 <h4>Singularity changes:</h4>
 <ul>
@@ -134,15 +137,122 @@
 
 <!-- notes for style guide: 'of a', 'of this', caps for classes? -->
 
-<h3>For Edition 0.92</h3>
-
-<p>Version 0.91 scheduled for late-April 2012, to include [...]TV and Radio amendments; others to be discussed.</p>
 
-<h3>For Edition 0.93</h3>
+<a name="pending" id="pending"></a>
 
-<p>Version 0.91 scheduled for early May 2012, to include [to be discussed].</p>
+<br/>
 
+<h2>Changes Pending (drafts)</h2>
+
+<p>A package of additions for a "1.0" release was <a href="http://blog.schema.org/2012/06/semtech-rdfa-microdata-and-more.html">announced</a> in early June 2012. The details will be
+	recorded here:</p>
+
+<blockquote>
+The schema.org 1.0 vocabulary is expected to include substantial additions including support for genealogy (via historical-data.org), e-commerce (through collaboration with Good Relations), Learning / Education (with LRMI), a Medical/health vocabulary, additions for describing technical/code and API documentation, and for improved modeling of TV/Radio content. 
+</blockquote>
+
+<h3>For Edition 0.95</h3>
+
+<p>Version 0.95 adds health/medical, and some smaller fixes.</p>
+
+<a name="medical" id="medical"></a>
+<h4>Health/Medical</h4>
+
+<p>The health/medical vocabulary is documented externally. It has been discussed and reviewed by the public-vocabs group, various professional groups, and by W3C's Semantic Web Lifesciences group.</p>
+
+<p>See <a href="http://www.w3.org/wiki/WebSchemas/MedicalHealthProposal">wiki</a> for background, and <a href="http://schemaorg-medicalext.appspot.com/">schemaorg-medicalext.appspot.com</a> for details.
+	  We don't list the entire vocabulary here.</p>
+
+
+<h3>For Edition 1.0</h3>
+
+From <a href="http://blog.schema.org/2012/06/semtech-rdfa-microdata-and-more.html">1.0 announcement</a>, "The schema.org 1.0 vocabulary is expected to include substantial additions including support for ..."
+<ul>
+<li><a href="http://www.w3.org/wiki/WebSchemas/HistoricalDataSchema">genealogy</a> (via historical-data.org)</li>
+<li><a href="http://www.w3.org/wiki/WebSchemas/GoodRelations">e-commerce</a> (through collaboration with Good Relations)</li>
+<li><a href="http://www.w3.org/wiki/WebSchemas/LearningResources">Learning / Education</a> (with LRMI)</li>
+<li><a href="http://www.w3.org/wiki/WebSchemas/MedicalHealthProposal">a Medical/health</a> vocabulary (scheduled already as 0.95)</li>
+<li>additions for describing <a href="http://www.w3.org/wiki/WebSchemas/TechArticleSchema">technical articles</a>/<a href="http://www.w3.org/wiki/WebSchemas/CodeSchema">code</a> 
+	and <a href="http://www.w3.org/wiki/WebSchemas/APIReferenceSchema">API documentation</a>.</li>
+<li>and for improved modeling of <a href="http://www.w3.org/wiki/WebSchemas/TVRadioSchema">TV/Radio</a> content.</li>
+</ul>
+
+<p>Details follow. Examples need to be collected elsewhere (wiki: TODO).</p>
+
+
+<a name="historicaldata" id="historicaldata"></a>
+<h4>historical-data changes:</h4>
+
+From <a href="http://historical-data.org/schemas.html">historical-data.org</a>...
+
+<ul>
+<li>Add a new type, 'HistoricalRecord', whose super-type is CreativeWork.</li>
+<li>HistoricalRecord description is 'A historical record, for example a document relating to family history.' TODO: check this; I don't see a draft text in <a href="http://historical-data.org/HistoricalRecord.html">schema</a>.</li>
+<li>Add properties for HistoricalRecord as described in <a href="http://historical-data.org/HistoricalRecord.html">HistoricalRecord.html</a>: content, date, event, family, historicalCollection, location, note, person, type. TODO: Are we sure of these? Some very general property names here.</li>
+<li>Add a new type, 'Family', whose super-type is Thing.</li>
+<li><a href="http://historical-data.org/Family.html">Family</a> description is 'A historical or genealogical nuclear family'.</li>
+<li>Add properties for Family as described in <a href="http://historical-data.org/Family.html">Family.html</a>: adoption (Event), child (Person), divorce (event), event (Event), marriage (Event), parent (Person), source (HistoricalRecord). TODO: double-check for similar constructs to 'source'. Check 'event'.</li> 
+<li>Add new properties to <a href="http://schema.org/Event">Event</a>, <a href="http://historical-data.org/Event.html">as listed</a>: media (MediaObject), source (HistoricalObject), type (text). TODO: 'type' is too general, as properties are in a global namespace for whole of schema.org, and we may add a general 'type' property.</li>
+<li>Add new properties to <a href="http://schema.org/Person">Person</a> per <a href="http://historical-data.org/Person.html">as listed</a>: birth (Event), death (Event), event (Event), gender (Text), marriage (Event), source (HistoricalRecord).</li>
+</ul>
+
+<a name="goodrelations" id="goodrelations"></a>
+<h4>Good Relations</h4>
+<p>Bulk details to be added or converted to suitable form by Dan Brickley + Martin Hepp. 
+	The <a href="http://www.w3.org/wiki/WebSchemas/GoodRelations">Wiki page</a> links to <a href="https://docs.google.com/document/pub?id=1Kx63gW9DBky1j97Jpwl3dU9k0pKPSgCT3EntTVvGjX4">master .doc</a></p>
+<ul>
+<li>Add prerequisites per .doc, transcribing most actions from there to here:
+	<ul>
+		<li><a href="https://www.w3.org/2011/webschema/track/issues/15">per issue-15</a> add Time and DateTime classes, both subtypes of DataType.</li>
+	    <li>We confirm that http://schema.org/Boolean works as required, per <a href="https://www.w3.org/2011/webschema/track/issues/14">issue-14</a>.</li>
+        <li>TODO: Address handling of known instances (e.g. InStock); - in progress / investigating (dan)</li>
+        <li>TODO: look into http://schema.org/QualitativeValue more carefully, as it is very general.</li>	
+        <li>Confirm that <a href="http://lists.w3.org/Archives/Public/public-vocabs/2012Jun/0005.html">premium video content use case</a> is addressed adequately.</li>
+     <li>	Action: Add additionalType property to http://schema.org/Thing.</li>
+	 <li>Action: Add additional properties to http://schema.org/Offer</li>
+	 <li>Action: Add additional properties to http://schema.org/Product.</li>
+	 <li>Action: Change range of brand to http://schema.org/Brand (a new type); TODO: Add definition text and super-type.</li> 
+	 <li>TODO: discuss Martin's proposed Action: "Tolerate additional properties from specializations of GoodRelations when using full URIs, e.g.
+	http://purl.org/vso/ns#engineDisplacement
+	http://purl.org/vvo/ns#torque " --- what does this mean? Who tolerates what?</li>
+ 	 <li>Action: Add additional properties to http://schema.org/Offer. </li>
+     <li>Action: Add additional properties to http://schema.org/Organization.</li>	
+ 	 <li>Action: Add additional properties to http://schema.org/Person.</li>
+     <li>Action: Add common superclass http://schema.org/Agent for Organization and Person (and for new Family from historical-data)</li>
+    </ul>
+	</li>
+<li>Add all new properties to existing types.</li>
+<li>Add all new types and associated properties, including textual definitions and location in hierarchy.</li>
+</ul>
+
+<a name="lrmi" id="lrmi"></a>
+<h4>LRMI</h4>
+<p>The proposal is summarised <a href="http://www.w3.org/wiki/WebSchemas/LearningResources#Vocabulary">in the Web Schemas wiki</a>:
+<ul>
+<li>Add a new AlignmentObject, whose super-type is Intangible, and whose description is *TODO*.</li>
+<li>Add 3 properties of AlignmentObject, as <a href="http://www.w3.org/wiki/WebSchemas/LearningResources#Vocabulary">listed</a>: alignmentType, targetDescription, targetName, targetUrl</li>
+<li>Add new properties, each on CreativeWork and with the listed expected types (note that these are possibly applicable elsewhere; TODO: do we put Thing too? Event? or edit later?): educationalAlignment, educationalUse, intendedEndUserRole, interactivityType, isBasedOnUrl, learningResourceType, timeRequired, typicalAgeRange.</li>
+</ul>
+
+
+<a name="techapicode" id="techapicode"></a>
+<h4>TechArticle, API Reference, Code</h4>
+<p>(to be added)</p>
+<ul>
+<li>Add a new type, <A href="http://www.w3.org/wiki/WebSchemas/TechArticleSchema">TechArticle</a>, whose super-type is <a href="http://schema.org/Article">Article</a> and whose description is 'A technical article - Example: How-to (task) topics, step-by-step, procedural troubleshooting, specifications, etc.'</li>
+<li>TODO: consider proficiencyLevel relationship to LRMI (and notions of 'audience', see Egor's notes)</li>
+<li>Add properties <a href="http://www.w3.org/wiki/images/b/bb/Schema.org_TechArticle_v2.5.pdf">as listed</a>: aboutProduct (Product); currentProduct (Product); dependencies (Text); proficiencyLevel (Text); 	technicalAudience (Text);</li>
+
+</ul>
 	
+<h4>TV/Radio improvements</h4>
+
+<p>Details are in wiki.</p>
+ 
+<ul>
+<li>Several <a href="http://www.w3.org/wiki/WebSchemas/TVRadioSchema#Modifications_to_the_existing_schema">modifications</a>, primarily to make room for Radio alongside broadcast TV.</li>
+<li>Several <a href="http://www.w3.org/wiki/WebSchemas/TVRadioSchema#Additions_to_the_existing_schema">additions</a>.</li>
+</ul>
 		
 <h3>Change Log</h3>