Technical Team/Minutes/2011-06-14 - Revision history

MartinMichlmayr: Convert to MediaWiki syntax

2013-03-06T13:12:25Z

Convert to MediaWiki syntax

Goneall at 05:59, 20 June 2011

2011-06-20T05:59:55Z

Goneall at 16:01, 14 June 2011

2011-06-14T16:01:41Z

New page

Minutes 6/14/2011
 
Attendees:
<ul>
<li>Bill Schineller</li>
<li>Kirsten Newcomer</li>
<li>Kate Stewart</li>
<li>Nicholas Loke</li>
<li>Peter Williams</li>
<li>Gary O’Neall</li></ul>
 
Agenda:
<ul>
<li> </li></ul>
Review of last week’s items:
<ul>
<li>Legal language updated from last week completed</li>
<li>Review of document – Kate received some comments</li>
<li>Spreadsheet example of the URI for artifactOf (Gary) – Still pending </li>
<li>Spec updated with change to hasFile</li>
<li>PackageVerificationCode – still pending</li>
<li>SimpleLicensingInfo – pending</li>
<li>Embedded Octect Stream - pending</li></ul>
 
Update on Kate’s conversation with Steve
<ul>
<li>Need to capture a “supply chain” for the origin of the packages<ul>
<li>Can capture this as a reviewer, but would require a company – proposal to have Reviewer be an Agent. Agree to change the spec to accommodate company. We can change the definition of the string or we can implement Agent. For Beta, we can change the definition of the string. We would like to implement an Agent structure, but that would require a more detailed proposal and incrementing the version number. Kate will work on a proposal.</li></ul></li>

<li>Proposal to have a package level ArtifactOf. Agree that this will be useful. This may require two different properties to represent A) if the package is part of a larger project and B) the package originates in a particular project. We need some use cases written – Peter will write one of the use cases in a bug.</li>
<li>Need to write-up usage of the spec<ul>
<li>Agree to create a Wiki page for usage guidelines. This would be structured around use cases and a description of the fields. The per-field would shadow the spec. Any contributed conversations to the per-field could be rolled into the spec itself at a later date. Would like to create a separate Beta web page which would include a link to the usage guidelines page. This could be added under participation. Kirsten will add after checking with Kim.</li></ul></li>

<li>Crypto flag request – need a proposal. </li>
<li>Suggest that we add bugs for the new proposal.</li>
<li>Open source or commercial package flag request – concern that different companies/organizations have different definitions of open source and commercial package</li>
<li>Package version – request to make the version parseable. Agree to add a field, but there was concern on making it parseable – Kate will add this in the next draft</li>
<li>Use of term package, raises questions about the hierarchy of packages. ArtifactOf at the package level will help.</li>
<li>A third delivery model – 1) SPDX is a sidecar to the package archive, 2) SPDX is embedded in the package, 3) a third proposal would be to have the SPDX document itself contains the archive.</li></ul>

@@ Line 1: / Line 1: @@
-<p><span style="font-family: Times New Roman; font-size: small;">Minutes 6/14/2011</span></p>
+== Attendees ==
-<p><span style="font-family: Times New Roman; font-size: small;"> </span></p>
-<p><span style="font-family: Times New Roman; font-size: small;">Attendees:</span></p>
-<ul>
-<li><span style="font-family: Times New Roman; font-size: small;">Bill Schineller</span></li>
-<li><span style="font-family: Times New Roman; font-size: small;">Kirsten Newcomer</span></li>
-<li><span style="font-family: Times New Roman; font-size: small;">Kate Stewart</span></li>
-<li><span style="font-family: Times New Roman; font-size: small;">Nicholas Loke</span></li>
-<li><span style="font-family: Times New Roman; font-size: small;">Peter Williams</span></li>
-<li><span style="font-family: Times New Roman; font-size: small;">Gary O’Neall</span></li></ul>
-<p><span style="font-family: Times New Roman; font-size: small;"> </span></p>
-<p><span style="font-family: Times New Roman; font-size: small;">Agenda:</span></p>
-<ul>
-<li><span style="font-family: Times New Roman; font-size: small;"> </span></li></ul>
-<p><span style="font-family: Times New Roman; font-size: small;">Review of last week’s items:</span></p>
-<ul>
-<li><span style="font-family: Times New Roman; font-size: small;">Legal language updated from last week completed</span></li>
-<li><span style="font-family: Times New Roman; font-size: small;">Review of document – Kate received some comments</span></li>
-<li><span style="font-family: Times New Roman; font-size: small;">Spreadsheet example of the URI for artifactOf (Gary) – Still pending </span></li>
-<li><span style="font-family: Times New Roman; font-size: small;">Spec updated with change to hasFile</span></li>
-<li><span style="font-family: Times New Roman; font-size: small;">PackageVerificationCode – still pending</span></li>
-<li><span style="font-family: Times New Roman; font-size: small;">SimpleLicensingInfo – pending</span></li>
-<li><span style="font-family: Times New Roman; font-size: small;">Embedded Octect Stream  - pending</span></li></ul>
-<p><span style="font-family: Times New Roman; font-size: small;"> </span></p>
-<p><span style="font-family: Times New Roman; font-size: small;">Update on Kate’s conversation with Steve</span></p>
-<ul>
-<li><span style="font-family: Times New Roman; font-size: small;">Need to capture a “supply chain” for the origin of the packages</span><ul>
-<li><span style="font-family: Times New Roman; font-size: small;">Can capture this as a reviewer, but would require a company – proposal to have Reviewer be an Agent.  Agree to change the spec to accommodate company.  We can change the definition of the string or we can implement Agent.  For Beta, we can change the definition of the string.  We would like to implement an Agent structure, but that would require a more detailed proposal and incrementing the version number.  Kate will work on a proposal.</span></li></ul></li>
-<li><span style="font-family: Times New Roman; font-size: small;">Proposal to have a package level ArtifactOf.  Agree that this will be useful.  This may require two different properties to represent A) if the package is part of a larger project and B) the package originates in a particular project.  We need some use cases written – Peter will write one of the use cases in a bug.</span></li>
+* Bill Schineller
-<li><span style="font-family: Times New Roman; font-size: small;">Need to write-up usage of the spec</span><ul>
+* Kirsten Newcomer
-<li><span style="font-family: Times New Roman; font-size: small;">Agree to create a Wiki page for usage guidelines.  This would be structured around use cases and a description of the fields.  The per-field would shadow the spec.  Any contributed conversations to the per-field could be rolled into the spec itself at a later date.  Would like to create a separate Beta web page which would include a link to the usage guidelines page.  This could be added under participation.  Kirsten will add after checking with Kim.</span></li></ul></li>
+* Kate Stewart
-<li><span style="font-size: small;"><span style="font-family: Times New Roman;">Crypto flag request – need a proposal.  </span></span></li>
+== Review of last week’s items ==
-<li><span style="font-family: Times New Roman; font-size: small;">Suggest that we add bugs for the new proposal.</span></li>
-<li><span style="font-family: Times New Roman; font-size: small;">Open source or commercial package flag request – concern that different companies/organizations have different definitions of open source and commercial package</span></li>
+* Legal language updated from last week completed
-<li><span style="font-family: Times New Roman; font-size: small;">Package version – request to make the version parseable.  Agree to add a field, but there was concern on making it parseable – Kate will add this in the next draft</span></li>
+* Review of document – Kate received some comments
-<li><span style="font-family: Times New Roman; font-size: small;">Use of term package, raises questions about the hierarchy of packages.  ArtifactOf at the package level will help.</span></li>
+* Spreadsheet example of the URI for artifactOf (Gary) – Still pending
-<li><span style="font-family: Times New Roman; font-size: small;">A third delivery model – 1) SPDX is a sidecar to the package archive, 2) SPDX is embedded in the package, 3) a third proposal would be to have the SPDX document itself contains the archive.</span></li></ul>
+* Spec updated with change to hasFile

← Older revision	Revision as of 05:59, 20 June 2011
(No difference)