OSLC CORE TC Minutes February 18, 2016

Attendees 

David Honey (IBM) 

Harish Krishnaswamy (Sofware AG) 

Jad El-khoury (KTH) 

Jim Amsden (IBM) 

Martin Sarabura (PTC) 

Jean-Luc Johnson (Airbus) 

Nick Crossley (IBM) 

Regrets 

Ian Green (IBM) 

Martin Pain (IBM) 

Resolutions 

·        
Accepted recommendation in 
issue 39 

·        
Defer 
issue 58 

Actions 

Jim to update description of oslc:range. Review range values. Email the result for review and further discussion.

·        
Jim to email Martin P to see if 
issue 44 can be closed. 

·        
Jim to contact Ian Green and Martin Pain re 
issue 40 to see if there are any changes required from their viewpoint. 

·        
David: To write proposed resolution to 
issue 60 

Chat transcript from room: oslc 

[07:06] David Honey (IBM): David volunteered as scribe

[07:06] David Honey (IBM): List of attendees: David Honey (IBM), Harish (Software AG), Jad El-khoury (KTH), Jean-Luc Johnson (Airbus), Jim Amsden (IBM), Martin Sarabura (PTC),
 Nick Crossley (IBM) 

[07:06] Martin Sarabura (PTC):
https://wiki.oasis-open.org/oslc-core/Meetings/Telecon2016.02.04

[07:07] David Honey (IBM): Approval of Feb 4 minutes, accepted.

[07:07] David Honey (IBM): Next meeting Mar 3rd.

[07:08] David Honey (IBM): Versioned types issue, David emailed Nick, Nick yet to review.

[07:09] Martin Sarabura (PTC):
https://issues.oasis-open.org/browse/OSLCCORE-43

[07:10] David Honey (IBM): Nick: Not yet done on issue 43. Won't have time to work on it over next 2 weeks.

[07:10] David Honey (IBM): Nick: Don't think it is critical for public review.

[07:12] David Honey (IBM): Nick: One column in shape table(s) is meaningless.

[07:12] David Honey (IBM): Needs work on Respec.

[07:15] David Honey (IBM): Nick: Changes to accomodate Jim's requirement are possible, but unlikely to be in next 2 weeks.

[07:16] David Honey (IBM):
https://issues.oasis-open.org/browse/OSLCCORE-39 ready for a vote

[07:17] David Honey (IBM): Old impact terms, do they need to be included as archaic?

[07:18] David Honey (IBM): Old terms were not in an obvious published vocabulary. So doesn't need to be included as archaic.

[07:20] David Honey (IBM): Vote to accept proposed resolution to
https://issues.oasis-open.org/browse/OSLCCORE-39

[07:20] David Honey (IBM): Martin seconded

[07:20] Nick Crossley (IBM): +1

[07:20] Jim Amsden (IBM)3: +1

[07:20] Martin Sarabura (PTC): +1

[07:20] Harish (Software AG): +1

[07:20] Jean-Luc Johnson (Airbus): +1

[07:20] David Honey (IBM): +1

[07:21] David Honey (IBM): Vote passed.

[07:21] Martin Sarabura (PTC):
https://issues.oasis-open.org/browse/OSLCCORE-45

[07:21] Martin Sarabura (PTC): Use of oslc:range, especially for enumerations, is unclear

[07:23] David Honey (IBM): Nick: There is an IBM tool requiring is oslc:range. There are cases where it is a valid, and useful to have range rather than allowed values (enumerations).

[07:25] David Honey (IBM): Nick: For enumerations, it is worth adding. For others, perhaps little value.

[07:32] David Honey (IBM): David: oslc:range is required for enumeration members to be expressed in terms meaningful to users.

[07:33] David Honey (IBM): Nick: Can we reword oslc:range to be less strict? Does that introduce compatibility concerns? Existing clients who are strict can continue to be
 strict. 

[07:33] David Honey (IBM): Jim: Update description of oslc:range. Review range values. Email the result for review and further discussion.

[07:34] David Honey (IBM): Jim: Agreed as action item.

[07:35] Jim Amsden (IBM)3: consider weakening the description of range. [ ] create an inventory of properties with proposed range values and [ ] email summary then decide next
 meeting 

[07:37] David Honey (IBM):
https://issues.oasis-open.org/browse/OSLCCORE-44

[07:37] David Honey (IBM): Jim will email Martin to see if issue 44 can be closed.

[07:38] David Honey (IBM):
https://issues.oasis-open.org/browse/OSLCCORE-60 still open.

[07:38] Jim Amsden (IBM)3:
https://issues.oasis-open.org/browse/OSLCCORE-16

[07:38] David Honey (IBM):
https://issues.oasis-open.org/browse/OSLCCORE-16 can be closed.

[07:39] David Honey (IBM):
https://issues.oasis-open.org/browse/OSLCCORE-47

[07:40] David Honey (IBM): Jim: ready to close?

[07:43] David Honey (IBM): Nick: Don't think it is an issue.

[07:45] David Honey (IBM):
https://issues.oasis-open.org/browse/OSLCCORE-58 needs discussion, proposal, and a VOTE

[07:47] David Honey (IBM): Nick: xsd:date versus xsd:dateTime is a weak case for adding data types.

[07:48] David Honey (IBM): Duration is a stronger case.

[07:48] David Honey (IBM): Nick: Needs more through review of data types with experts, and we don't have time to do that now.

[07:53] David Honey (IBM): David, Nick: Concerns about interoperability with OSLC 2 clients.

[07:54] David Honey (IBM): Proposal to defer.

[07:54] David Honey (IBM): Wait for comments in public review.

[07:54] Nick Crossley (IBM): +1

[07:54] David Honey (IBM): Nick: seconded

[07:54] Jim Amsden (IBM)3: +1

[07:54] David Honey (IBM): +1

[07:54] Jad El-khoury (KTH): +1

[07:54] Martin Sarabura (PTC): +1

[07:54] Jean-Luc Johnson (Airbus): +1

[07:55] Harish (Software AG): +1

[07:55] David Honey (IBM): Carried.

[07:57] David Honey (IBM): Jim: To work through Nick's reviews.

[07:57] David Honey (IBM): Jim Will update
https://wiki.oasis-open.org/oslc-core/FrontPage#Working_Documents

[07:57] David Honey (IBM): Can have an email vote

[07:58] David Honey (IBM): Nick: will complete resource shape review.

[08:00] David Honey (IBM): Review of core vocab.

[08:00] David Honey (IBM): oslc:archived still serves a purpose.

[08:00] David Honey (IBM): dcterms:creator - should the range be Agent or foaf:Person

[08:01] Nick Crossley (IBM): Had to drop

[08:01] David Honey (IBM): Keep foaf:Person for compatibility with existing implementations.

[08:02] David Honey (IBM):
https://issues.oasis-open.org/browse/OSLCCORE-40

[08:03] David Honey (IBM): Jim: Will contact Ian Green and Martin Pain to see if there are any changes required from their viewpoint.

[08:06] David Honey (IBM): Jim: Not OSLC's job to describe general web security. Click-jacking is specific to OSLC delegated dialogs.

[08:08] Harish (Software AG): Have to drop now.

[08:09] David Honey (IBM): Martin: Is worth mentioning as guidance. Should discuss with Martin Pain since he had input to discussion.

[08:09] David Honey (IBM): Jim: Proposal is to remove discussion of click-jacking, and need to address standard web security issues unless OSLC introduces specific ones.

[08:11] David Honey (IBM): Jim: Don't think vote is needed since text in spec was non-normative.