HistoryViewLinks to this page 2013 September 18 | 02:01 pm

OSLC Core Meeting September 18, 2013

Previous meeting

Meeting logistics

Included in Meetings

Agenda / Minutes

Review Minutes from August 28

Update on W3C LDP 1.0

Update on W3C RDF Validation Workshop

Core transition to OASIS TC Update

  • High-level updates
  • Call for comments on charter ended
  • Core TC to be first to transition
  • Need to determine exact date of kickoff of first TC meeting ~ November, will continue with this WG for at least 1 meeting past kickoff meeting. As-needed to handle V2 items.

Discussion:

  • In short time, current Core WG will become “Core V2 maintenance” and be an offline WG, vote on mailing list and raise issues on mailing list, etc.
  • Steve: to provide more details for the WG: lists to subscribe to, meetings to attend, where to look, etc

Annotation Vocabulary Proposal Arthur

Eclipse Lyo 2.0 Sam

  • Update on 2.0 release
  • Feedback on post-2.0 backlog of items
  • Sam: elaborated on what is available on the wiki page
  • SteveP: OSLC4Net and OSLC4J possibly adding a better way for a client to

TRS 2.0 Spec – Updates?

  • TRS-6 Rollback handling and defn

OSLC Core V2 Issues - Outstanding issues and proposed updates (review only, no outstanding updates)

Note, no new issues…including previous agenda content to help with viewing

Open Issues

  • TRS-6 Lack of needed exception handling: rollback is not clearly defined and needed error-free changlogs is not realistic

Resolved/Closed Issues

  • none

V3 Spec Drafting - Specifications

  • Delegated dialogs - Sam
    • Possibly remove windowName support, use only postMessage - almost all browsers support
      • need to investigate impact more, could point from 3.0 to 2.0
    • resource shapes for creation dialogs
    • guidance for mobile needed?
    • JohnA: template usecase for automation, doesn’t actually generate a resource but the representation.
    • NickC: configuration context picker (see below)
    • EdG: (see below)
    • SteveS: sharing styling hints
  • UI Preview - Sam
    • guidance for mobile needed?
    • sharing styling hints
    • consider using JSON for representation
    • editable preview?
  • SteveS: Delegated Editor?
    • Use cased from CM WG - embedding a CR editor within a QM tool, embedding a CR editor within Eclipse IDE (generic task viewing and editing), needs include receiving events on when content is modified and integration with general editor frameworks for save/dirty.

Next meeting:

  • Sept 25 - 3.0 development (Conflict for Steve, JavaOne), move to Oct 2nd
  • Oct 9 - 3.0 development

Attendees

Attendees: SteveSpeicher (chair), SteveP, SamP, JohnA, Nick, Tuan, JimC, MikeF

Regrets:

Possible Attendees: SteveSpeicher (chair), MichaelFiedler, EdGentry, StevePitschke, DevangParikh, PaulMcMahan, JohnArwe, PaulSlauenwhite, NickCrossley, SamPadgett, SheehanAnderson, SuzetteSamoojh, DonCronin, JimConallen, IanGreen, GrayBachelor, NicholasKruk, DavidHoney, ChristopherLazzaro, SofiaYeung, RainerErsch, AndyBerner, CharlesRankin, MikeLoeffler, ArthurRyman, JulianneBielski, RobertElves, TuanDang

Backlog topics

Open / future topics:

  • EdGentry suggested topic: Pickers: with preferred or restricted link types, limiting what can be selected or linked to resource type. SteveS suggests submitting the scenario + some details to either RM (or other appropriate WG) or Core to seed the discussion.

  • NickC suggested topic: need to extend the OSLC pickers (and other areas possibly like query) to allow a [configuration] context to be passed, so the provider can show the versions/variants of the resources in that context, and so the resulting link preserves that context. Category:Meetings


Categories