This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.

OSLC Core Meeting September 7, 2011

Previous meeting

Link to OSLC Core spec: OslcCoreSpecification

Meeting logistics

How to dial-in to our telecon and login to our screen-sharing session.

Telecon Info

USA Toll-Free: 888-426-6840 USA Caller Paid: 215-861-6239 Participant Code: 3292849

Other numbers: https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=3292849&accessNumber=2158616239

Online meeting

(when we need it)

For IBM employees, use the following link: http://w3.ibm.com/collaboration/meeting/join/?schedid=4440645 (IBM intranet authentication required)

For people outside IBM, use the following link: http://www.ibm.com/collaboration/meeting/join?id=4440645

Agenda

  • Workgroup news
    • Automation WG looking to revive in coming months, contact CharlesRankin if interested
    • Communications WG to kick off, contact AndyGurd
  • Meeting time change
  • 2.0 Issues (still open)
  • Usage of oslc:domain URIs when implementation supports pre-spec or non-domain (generic provider) email thread
  • 3.0 content and priorities discussion
    • We'll talk about various priorities for Core 3.0 and OSLC in general. This will mostly be a discussion to review feedback given so far and gather information on priorities.
    • Proposed timetable: convergence draft by 2H2012
    • OslcCoreV3Plan
  • Upcoming meetings:
    • Sept 21 - (tentative) PLM WG proposal for general versioning needs
    • Oct 5 - (tentative) Core 3.0 progress

Minutes

Workgroup news:

    • Automation WG looking to revive in coming months, contact CharlesRankin if interested
    • Communications WG to kick off, contact AndyGurd

2.0 Issues discussion:

encoding of UI preview labels

  • 4 choices:
    1. redefine its meaning completely in context of XML; con: could be confusing with usage in other specs
    2. say it is really RDF, invent new html data type; con: adds confusion to general
    3. change the name of predicate completely; con: need to migrate to it
    4. do nothing, fix example; con: implementation is harder
json representation ambiguities
  • ACTION: queue up for review at next meeting Sept 21
Usage of oslc:domain URIs when implementation supports pre-spec or non-domain (generic provider) email thread
  • general feedback
  • ACTION: follow up with direction towards new URIs on existing oslc:domain

Upcoming meetings:

Sept 21 - (tentative, most likely will push off to Oct 5th - Steve confirming) PLM WG proposal for general versioning needs

Oct 5 - (tentative) Core 3.0 progress

Attendees

SteveSpeicher (chair)

MikeLoeffler SheehanAnderson MichaelFiedler PaulSlauenwhite JimConallen ArthurRyman PaulMcMahan AndyBerner JohnArwe

probable CharlesRankin

Topic revision: r3 - 19 Oct 2011 - 16:27:50 - SteveSpeicher
 
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback