Technical Team/Minutes/2012-01-03 - Revision history

MartinMichlmayr: Convert to MediaWiki syntax

2013-03-06T13:20:48Z

Convert to MediaWiki syntax

Goneall at 20:47, 3 January 2012

2012-01-03T20:47:57Z

New page

Minutes 1/3/2012 Attendees:<ul><li>Gary O’Neall</li><li>Bill Schineller</li><li>Kirsten Newcomer</li><li>Kate Stewart</li><li>Rana Rahal</li><li>Peter Williams</li></ul> Agenda:<ul><li>Review of latest 1.1 spec draft</li></ul> Review of 1.1 spec draft<ul><li>·         Should the data license be a new tag?  Kate will discuss this with Jilayne</li><li>·         Fixed the bugs related to spelling/grammar</li><li>·         Added optional creator comment field – Peter will update RDF then assign to Gary to update tools</li><li>·         [action] Verify the verification code by comparing the python results with the java tools results (Bill)</li><li>·         Inconsistency in RDF examples related to “nodeid” and “resource=” license references.  Kate will make it consistent in the document.  Cannot easily make the tool generate consistent references, however, it is equivalent in RDF. </li><li>·         RDF site has missing SHA – Peter to add back the SHA for versioning</li><li>·         Update to the diagram – Currently no object model around Organization and Person.  Proposal to add object model for 1.1.  Will add to the list of features to be considered for 1.1.</li><li>·         Data license – change text from “only valid” to “current valid” to reflect the fact 1.0 version had a different “only valid” value.</li><li>·         Use of the word “database” in the data license section can be confusing.  The creative commons zero license only refers to “database” and not “data”.  Kate will update spec to add text connecting “database” to its use in the license (e.g. “database as used in the Creative Commons …”).</li><li>·         Supplier field – implementation of this field isn’t clear.  To be discussed in the 2.0 discussion for the supply chain use cases.</li><li>·         Would be nice to add the Creative Commons Zero license as an appendix to the spec.</li><li>·         Will add a changelog for future changes to spec</li></ul> Other discussions and updates:<ul><li>·         Timing on version 1.1– proposed target end of Q1</li><li>·         License matching – legal team is discussing if 2 license texts represent the same license.  Proposal to create a guidelines document (separate from the spec) and a tool reference implementation (being worked on by Kate)</li><li>·         Proposal to annotations in programming languages – will add a bug to track</li><li>·         Tools – haven’t heard from Martin on increasing upload size – Kate will check with Martin.  Other option is to update the new website.</li><li>·         Kate will be in Europe next week, but still plans to make the call.  The last 2 weeks Kate be in Australia and will not be able to make the call due to time zone differences.</li></ul>

← Older revision		Revision as of 13:20, 6 March 2013
Line 1:		Line 1:
−	~~<p><span style~~=~~"font-family: Times New Roman; font-size: medium;">Minutes 1/3/2012</span></p><p><span style~~=~~"font-family: Times New Roman; font-size: medium;"> </span></p><p><span style="font-family: Times New Roman; font-size: medium;">~~Attendees~~:</span></p><ul><li><span style~~=~~"font-family: Times New Roman; font-size: medium;">~~Gary O’Neall~~</span></li><li><span style="font-family: Times New Roman; font-size: medium;">~~Bill Schineller~~</span></li><li><span style="font-family: Times New Roman; font-size: medium;">~~Kirsten Newcomer~~</span></li><li><span style="font-family: Times New Roman; font-size: medium;">~~Kate Stewart~~</span></li><li><span style="font-family: Times New Roman; font-size: medium;">~~Rana Rahal~~</span></li><li><span style="font-family: Times New Roman; font-size: medium;">~~Peter Williams~~</span></li></ul><p><span style~~=~~"font-family: Times New Roman; font-size: medium;"> </span></p><p><span style~~=~~"font-family: Times New Roman; font-size: medium;">~~Agenda~~:</span></p><ul><li><span style~~=~~"font-family: Times New Roman; font-size: medium;">~~Review of latest 1.1 spec draft~~</span></li></ul><p><span style~~=~~"font-family: Times New Roman; font-size: medium;"> </span></p><p><span style~~=~~"font-family: Times New Roman; font-size: medium;">~~Review of 1.1 spec draft~~</span></p><ul><li><span style~~=~~"font-size: medium;">·</span>         <span style~~=~~"font-family: Times New Roman; font-size: medium;">~~Should the data license be a new tag?~~ ~~ Kate will discuss this with Jilayne~~</span></li><li><span style="font-size: medium;">·</span>         <span style="font-family: Times New Roman; font-size: medium;">~~Fixed the bugs related to spelling/grammar~~</span></li><li><span style="font-size: medium;">·</span>         <span style="font-family: Times New Roman; font-size: medium;">~~Added optional creator comment field – Peter will update RDF then assign to Gary to update tools~~</span></li><li><span style="font-size: medium;">·</span>         <span style="font-family: Times New Roman; font-size: medium;">~~[action] Verify the verification code by comparing the python results with the java tools results (Bill)~~</span></li><li><span style="font-size: medium;">·</span>         <span style="font-family: Times New Roman; font-size: medium;">~~Inconsistency in RDF examples related to “nodeid” and “resource=” license references.~~ ~~ Kate will make it consistent in the document.~~ ~~ Cannot easily make the tool generate consistent references, however, it is equivalent in RDF. ~~</span></li><li><span style="font-size: medium;">·</span>         <span style="font-family: Times New Roman; font-size: medium;">~~RDF site has missing SHA – Peter to add back the SHA for versioning~~</span></li><li><span style="font-size: medium;">·</span>         <span style="font-family: Times New Roman; font-size: medium;">~~Update to the diagram – Currently no object model around Organization and Person.~~ ~~ Proposal to add object model for 1.1.~~ ~~ Will add to the list of features to be considered for 1.1.~~</span></li><li><span style="font-size: medium;">·</span>         <span style="font-family: Times New Roman; font-size: medium;">~~Data license – change text from “only valid” to “current valid” to reflect the fact 1.0 version had a different “only valid” value.~~</span></li><li><span style="font-size: medium;">·</span>         <span style="font-family: Times New Roman; font-size: medium;">~~Use of the word “database” in the data license section can be confusing.~~ ~~ The creative commons zero license only refers to “database” and not “data”.~~ ~~ Kate will update spec to add text connecting “database” to its use in the license (e.g. “database as used in the Creative Commons …”).~~</span></li><li><span style="font-size: medium;">·</span>         <span style="font-family: Times New Roman; font-size: medium;">~~Supplier field – implementation of this field isn’t clear.~~ ~~ To be discussed in the 2.0 discussion for the supply chain use cases.~~</span></li><li><span style="font-size: medium;">·</span>         <span style="font-family: Times New Roman; font-size: medium;">~~Would be nice to add the Creative Commons Zero license as an appendix to the spec.~~</span></li><li><span style="font-size: medium;">·</span>         <span style="font-family: Times New Roman; font-size: medium;">~~Will add a changelog for future changes to spec~~</span></li></ul><p><span style~~=~~"font-family: Times New Roman; font-size: medium;"> </span></p><p><span style~~=~~"font-family: Times New Roman; font-size: medium;">~~Other discussions and updates~~:</span></p><ul><li><span style~~=~~"font-size: medium;">·</span>         <span style~~=~~"font-family: Times New Roman; font-size: medium;">~~Timing on version 1.1– proposed target end of Q1~~</span></li><li><span style="font-size: medium;">·</span>         <span style="font-family: Times New Roman; font-size: medium;">~~License matching – legal team is discussing if 2 license texts represent the same license.~~ ~~ Proposal to create a guidelines document (separate from the spec) and a tool reference implementation (being worked on by Kate)~~</span></li><li><span style="font-size: medium;">·</span>         <span style="font-family: Times New Roman; font-size: medium;">~~Proposal to annotations in programming languages – will add a bug to track~~</span></li><li><span style="font-size: medium;">·</span>         <span style="font-family: Times New Roman; font-size: medium;">~~Tools – haven’t heard from Martin on increasing upload size – Kate will check with Martin.~~ ~~ Other option is to update the new website.~~</span></li><li><span style="font-size: medium;">·</span>         <span style="font-family: Times New Roman; font-size: medium;">~~Kate will be in Europe next week, but still plans to make the call.~~ ~~ The last 2 weeks Kate be in Australia and will not be able to make the call due to time zone differences.~~</span></li></ul>~~	+	== Attendees ==
		+
		+	* Gary O’Neall
		+	* Bill Schineller
		+	* Kirsten Newcomer
		+	* Kate Stewart
		+	* Rana Rahal
		+	* Peter Williams
		+
		+	== Agenda ==
		+
		+	* Review of latest 1.1 spec draft
		+
		+	== Review of 1.1 spec draft ==
		+
		+	* Should the data license be a new tag? Kate will discuss this with Jilayne
		+	* Fixed the bugs related to spelling/grammar
		+	* Added optional creator comment field – Peter will update RDF then assign to Gary to update tools
		+	* [action] Verify the verification code by comparing the python results with the java tools results (Bill)
		+	* Inconsistency in RDF examples related to “nodeid” and “resource=” license references. Kate will make it consistent in the document. Cannot easily make the tool generate consistent references, however, it is equivalent in RDF.
		+	* RDF site has missing SHA – Peter to add back the SHA for versioning
		+	* Update to the diagram – Currently no object model around Organization and Person. Proposal to add object model for 1.1. Will add to the list of features to be considered for 1.1.
		+	* Data license – change text from “only valid” to “current valid” to reflect the fact 1.0 version had a different “only valid” value.
		+	* Use of the word “database” in the data license section can be confusing. The creative commons zero license only refers to “database” and not “data”. Kate will update spec to add text connecting “database” to its use in the license (e.g. “database as used in the Creative Commons …”).
		+	* Supplier field – implementation of this field isn’t clear. To be discussed in the 2.0 discussion for the supply chain use cases.
		+	* Would be nice to add the Creative Commons Zero license as an appendix to the spec.
		+	* Will add a changelog for future changes to spec
		+
		+	== Other discussions and updates ==
		+
		+	* Timing on version 1.1– proposed target end of Q1
		+	* License matching – legal team is discussing if 2 license texts represent the same license. Proposal to create a guidelines document (separate from the spec) and a tool reference implementation (being worked on by Kate)
		+	* Proposal to annotations in programming languages – will add a bug to track
		+	* Tools – haven’t heard from Martin on increasing upload size – Kate will check with Martin. Other option is to update the new website.
		+	* Kate will be in Europe next week, but still plans to make the call. The last 2 weeks Kate be in Australia and will not be able to make the call due to time zone differences.
		+
		+	[[Category:Technical\|Minutes]]
		+	[[Category:Minutes]]