--- a/schema.org/drafts/changes.html	Tue Apr 10 16:31:05 2012 +0200
+++ b/schema.org/drafts/changes.html	Tue Apr 10 16:46:39 2012 +0200
@@ -82,7 +82,6 @@
     <li>New property 'fileFormat', expected type Text, description 'MIME format of the binary (e.g. application/zip)'</li>
     <li>New property 'applicationCategory', expected type Text, description 'Type of software application. e.g. Game, Multimedia.'</li>
     <li>New property 'applicationSubCategory', expected type Text, description 'Subcategory of the application "e.g. Arcade Game".'</li>
-TODO fix caps *Url *URL
     <li>New property 'downloadUrl', expected type URL, description 'If the file can be downloaded, URL to download the binary.'</li>
     <li>New property 'softwareVersion', expected type Text, description 'Version of the software instance.'</li>
     <li>New property 'releaseNotes', expected type URL or Text, description "Description of what changed in this version." </li>
@@ -115,9 +114,16 @@
 </li>
 
 <li>TODO: If we are not adding the entire software categorisation enumeration, how exactly are these handled?
-	The example given in PDF has softwareApplicationSubCategory: Arcade and Action (i.e. text value), and yet softwareApplicationCategory as a link to http://schema.org/
-	GameApplication. These could be an example for external enumerations. For now we should type them as URL or Text for flexibility. 
-	</li>
+	The example given in PDF has softwareApplicationSubCategory: Arcade and Action (i.e. text value), and yet softwareApplicationCategory as a link to http://schema.org/GameApplication. These could be an example for external enumerations. For now we should type them as URL or Text for flexibility. 
+</li>
+	
+	
+<li>Converge *Url/*URL property spelling, per <a href="https://www.w3.org/2011/webschema/track/issues/9">mixed case</a> resolution:
+  <ul>
+	<li>For each of embedURL, contentURL, downloadURL, ensure there is an equivalent property named with mixed-case: 'embedUrl', 'contentUrl', 'downloadUrl'.</li>
+    <li>For each of embedURL, contentURL, downloadURL append text based on '(legacy spelling; mixed-case is preferred form, ie. xyzUrl rather than xyzURL)' (expanding xyz appropriately to the actual property name)</li>
+  </ul>
+</li>	
 	
 </ul>