Page Comparison

...

• link to the file

Presentation(s)

• link to the fileNone
  

Documents

• Proposed ToIP Tool specification

...

1. New members
2. Proposed solution for attribution of contributions
   1. In our internal data model, add two properties to the Definition of a Concept in a specific Scope
      1. URI identifying the Contributor for purposes of attribution
      2. URI identifying the License that applies to the Contribution
   2. This should allow us to cover all types of contributions under all forms of acceptable licenses that require attribution
   3. Michael Michaelsaid that this would not satisfy the requirements of the Creative Commons corpus.
   4. ACTION: Michael Michaelto propose a different set of properties that will fulfill the Creative Commons CC BY SA license requirements.
   5. ACTION: Drummond Reedto check with LF counsel about the use of a more restrictive CC BY SA license.
   6. ACTION: Drummond Reedto check with upstream providers, e.g., Sovrin Foundation, about using a less-restrictive license.
3. Discussion of any remaining issues with the proposed ToIP Tool specification
   1. Do we agree with the internal data model?
   2. Do we agree with the requirements for how we link to data (hyperlinking)?
   3. Do we agree with the form factor: a command-line tool that lets us pipe data through one or more stages of transformations?
   4. Are there any other open issues?
   DECISION:  Do we have consensus on the spec and to proceed with a bounty request?
   1. Yes, four have been lodged against Daniel Hardman's GitHub repo.
   2. https://github.com/dhh1128/ctwg/issues/3
      1. There is a question about the TT render operation. Daniel Hardmanadded support for that operation at the request of Dan Gisolfibut clarified that it would be primarily a convenience function as it would simply set up the necessary environment and then call another tool such as MkDocs that actually does the rendering.
      2. Scott Whitmireadvocated that the rendering function be kept separate from the TT export function as a general "Gang of Four" pattern.
      3. We discussed MkDocs as a rendering tool and what it needs to ingest. It will natively ingest Markdown files, however specific formatting information needs to be added to the Markdown in order to invoke certain features in Markdown.
      4. Michael Michaelasked if the TT export function could take different arguments for different rendering formats.
      5. Daniel Hardmanadvocated that our #1 priority is a tool that allows us to curate and produce high quality corpus data.
      6. DECISION: The initial version of the TT tool will not include a render operation but will stop with the export operation. The render operation can either he handled in a future version or by a separate tool.
   3. https://github.com/dhh1128/ctwg/issues/6
      1. Rieks explained his issue, but it was clear that it will require more time than we had left on this call.
      2. DECISION: We will have to postpone going to the Steering Committee for a bounty request until the spec can be finished.
4. Determining the amount of the proposed bounty request
   1. DECISION: We do not yet have enough information to size the bounty request yet. Drummond Reedwill give the ToIP Steering Committee a general heads up that the request will be forthcoming.
5. Review of Decisions and Action Items and planning for next meeting

   Slides

   #1 - 

   Decisions

   •  Sample Decision Item

   Action Items

   •  Sample Action Item
   1. 1. At the next regular meeting (same time on Monday April 12) we will again see if we can close on the ToIP Term tool specification.

   Decisions

   •  DECISION: The initial version of the TT tool will not include a render operation but will stop with the export operation. The render operation can either he handled in a future version or by a separate tool.
   •  DECISION: We will have to postpone going to the Steering Committee for a bounty request until the spec can be finished.
   •  DECISION: We do not yet have enough information to size the bounty request yet.

   Action Items

   •  ACTION: Michael Michaelto propose a different set of properties that will fulfill the Creative Commons CC BY SA license requirements.
   •  ACTION: Drummond Reedto check with LF counsel about the use of a more restrictive CC BY SA license.
   •  ACTION: Drummond Reedto check with upstream providers, e.g., Sovrin Foundation, about using a less-restrictive license.
   •  ACTION: Drummond Reedto "warm up" the ToIP Steering Committee