W3C

- DRAFT -

Healthcare Schema Vocabulary CG Meeting, 11th December 2015

11 Dec 2015

See also: IRC log

Attendees

Present
Marc_Twagirumukiza, James_G_Rob, Cristian_Lazurean, Leeza, Lloyd_Fassett, Freidericks_M, Christophe_Lemoux, M._Van_der_Sande, Mark_Harrisson., D.P_(?)
Regrets
Michel_Dumontier, Dan_Brickley, Dave_F.D, Michel_Miller, David_Booth
Chair
Marc Twagirumukiza
Scribe
Marc Twagirumukiza

Contents


RESOLUTION: 1. Aggrement on the suggestions received: Keep the TCons for general driving ideas and unsolved issues on Github, or on-demand points.

<scribe> scribe: Marc Twagirumukiza

RSSAgent, meeting: Healthcare Schema Vocabulary CG Meeting, 11th December 2015

RSSAgent, chair: Marc Twagirumukiza

RESOLUTION: 1. Aggrement on the suggestions received: Keep the TCons for general driving ideas and unsolved issues on Github, or on-demand points.
... 2. Prefere Github repository discussions to deal with issues raised there (participants comments, suggestions and editions).
... 2. Invite all participant to submit their expectations for ScheMed CG agenda (probably beyond the extension work) but not overlaping with existing working groups.

<scribe> ACTION: @Marc: To ask schema.org if the current version of health.schema.org extension can be shipped for next release (with provision to keep receiving feedback). [recorded in http://www.w3.org/2015/12/11-schemed-minutes.html#action01]

<scribe> ACTION: Postpone all issues see resolution2 [recorded in http://www.w3.org/2015/12/11-schemed-minutes.html#action02]

<scribe> ACTION: To appoint a co-chair (if possible 2). Marc will sent out invitation for vulunteering. [recorded in http://www.w3.org/2015/12/11-schemed-minutes.html#action03]

RESOLUTION: Aggrement on the suggestions received: Keep the TCons for general driving ideas and unsolved issues on Github, or on-demand points.

RESOLUTION: 1. Aggrement on the suggestions received: Keep the TCons for general driving ideas and unsolved issues on Github, or on-demand points.

RESOLUTION: Prefer Github repository discussions to deal with issues raised there (participants comments, suggestions and editions).
... Invite all participant to submit their expectations for ScheMed CG agenda (probably beyond the extension work) but not overlaping with existing working groups.

<scribe> ACTION: Postpone all actions as the assignees are not available to report the status [recorded in http://www.w3.org/2015/12/11-schemed-minutes.html#action04]

<scribe> ACTION:To ask schema.org if the current version of health.schema.org extension can be shipped for next release (with provision to keep receiving feedback). [recorded in http://www.w3.org/2015/12/11-schemed-minutes.html#action05]

RESOLUTION: To appoint a co-chair (if possible 2). Marc will sent out invitation for vulunteering.

resolution?

resolution-

help

RSSAgent, DROPPED RESOLUTION 2

RSSAgent, [DROPPED] RESOLUTION 2

RSSAgent, Drop RESOLUTION 2

RSSAgent, Drop Resolution 3 2

RSSAgent, DROPPED RESOLUTION 3

Summary of Action Items

[NEW] ACTION: @Marc: To ask schema.org if the current version of health.schema.org extension can be shipped for next release (with provision to keep receiving feedback). [recorded in http://www.w3.org/2015/12/11-schemed-minutes.html#action01]
[NEW] ACTION: Postpone all actions as the assignees are not available to report the status [recorded in http://www.w3.org/2015/12/11-schemed-minutes.html#action04]
[NEW] ACTION: Postpone all issues see resolution2 [recorded in http://www.w3.org/2015/12/11-schemed-minutes.html#action02]
[NEW] ACTION: To appoint a co-chair (if possible 2). Marc will sent out invitation for vulunteering. [recorded in http://www.w3.org/2015/12/11-schemed-minutes.html#action03]
[NEW] ACTION: To ask schema.org if the current version of health.schema.org extension can be shipped for next release (with provision to keep receiving feedback). [recorded in http://www.w3.org/2015/12/11-schemed-minutes.html#action05]
 

Summary of Resolutions

  1. 1. Aggrement on the suggestions received: Keep the TCons for general driving ideas and unsolved issues on Github, or on-demand points.
  2. 1. Aggrement on the suggestions received: Keep the TCons for general driving ideas and unsolved issues on Github, or on-demand points.
  3. Aggrement on the suggestions received: Keep the TCons for general driving ideas and unsolved issues on Github, or on-demand points.
  4. 1. Aggrement on the suggestions received: Keep the TCons for general driving ideas and unsolved issues on Github, or on-demand points.
  5. Prefer Github repository discussions to deal with issues raised there (participants comments, suggestions and editions).
  6. To appoint a co-chair (if possible 2). Marc will sent out invitation for vulunteering.
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2015/12/11 17:56:29 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: Marc_Twagirumukiza
Found Scribe: Marc Twagirumukiza

WARNING: No "Topic:" lines found.

Present: Marc_Twagirumukiza James_G_Rob Cristian_Lazurean Leeza Lloyd_Fassett Freidericks_M Christophe_Lemoux M._Van_der_Sande Mark_Harrisson. D.P_(?)
Regrets: Michel_Dumontier Dan_Brickley Dave_F.D Michel_Miller David_Booth
Got date from IRC log name: 11 Dec 2015
Guessing minutes URL: http://www.w3.org/2015/12/11-schemed-minutes.html

WARNING: No person found for ACTION item: @marc: to ask schema.org if the current version of health.schema.org extension can be shipped for next release (with provision to keep receiving feedback). [recorded in http://www.w3.org/2015/12/11-schemed-minutes.html#action01]

People with action items: postpone to

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]