work on Use Cases and Requirements, changed pub date
authorMichael Hausenblas http://sw-app.org/mic.xhtml#i
Wed, 01 Feb 2012 10:09:19 +0000
changeset 63 a4450f08709a
parent 62 4268253af0bc
child 64 e652cadb212e
work on Use Cases and Requirements, changed pub date
people/index.html
people/respec-config.js
--- a/people/index.html	Wed Feb 01 10:03:38 2012 +0000
+++ b/people/index.html	Wed Feb 01 10:09:19 2012 +0000
@@ -44,6 +44,7 @@
 	<dt><dfn>consumer</dfn></dt>
 	<dd>A person or agent that uses Linked Data from the Web.</dd>
 </dl>
+<p class="editorsnote">@@TODO: point out definition of source data in the <a href="https://dvcs.w3.org/hg/gld/raw-file/default/bp/index.html">BP document</a> for further details.</p>
 </section>
 <section>
 <h3>Conventions</h3>
@@ -73,7 +74,6 @@
  invited 東海林賢蔵, a business contact and Open Data guru she recently met at a local event, to brief her and 
  the CoolCids team on the challenges and requirements in the domain.
 </pre>
-<p class="editorsnote">@@TODO: link to the definition of source data in the <a href="https://dvcs.w3.org/hg/gld/raw-file/default/bp/index.html">BP document</a></p>
 <p>Note: if you're not familiar with people's names throughout the world, you might want to read the <a href="http://www.w3.org/International/questions/qa-personal-names" title="Personal names around the world">personal names around the world</a> article provided by the W3C Internationalization (I18n) Activity.</p>
 <div class="fig"><a href="img/people-example-big.png"><img src="img/people-example.png" alt="GLD people example" /></a><div>A visual representation of the walkthrough example as a graph (<a href="img/people-example-big.png">big version</a>).</div></div>
 </section>
@@ -220,6 +220,8 @@
 		<tr><td>Conversation topic</td><td></td><td></td><td></td><td></td><td></td><td></td><td>&bull;</td></tr>
 	</tbody>
 </table>
+
+<p class="editorsnote">@@TODO: describe how we determine which requirements are common to all UC: for example, we could say that a requirement must at least show up in half of the UC, etc.</p>
 </section>
 </section>
 
--- a/people/respec-config.js	Wed Feb 01 10:03:38 2012 +0000
+++ b/people/respec-config.js	Wed Feb 01 10:09:19 2012 +0000
@@ -1,7 +1,7 @@
 var respecConfig = {
     // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
     specStatus:           "ED",
-    publishDate:          "2012-01-31",
+    publishDate:          "2012-02-01",
     //copyrightStart:       "2010",
 
     // the specification's short name, as in http://www.w3.org/TR/short-name/