Hi,
I am sorry, I will not be able to attend today’s meeting.
Didier
Cordialement / Best Regards,
Didier SIMONEAU
CATIA Systems Technologies R&D Technology Senior Manager
Office: +33 2 9805 8838
3DS.COM/CATIA
Dassault Systèmes |
120 rue René Descartes, ZI de la Pointe du Diable | 29280 Plouzané |
France
From: [mailto:]
On Behalf Of Arnaud Le Hors
Sent: Wednesday, December 10, 2014 7:22 PM
To: OASIS OSLC Core TC Discussion List
Subject: [oslc-core] Agenda for 11 December 2014
Hi all,
The agenda for tomorrow's call is now available:
http://wiki.oasis-open.org/oslc-core/Meetings/Telecon2014.12.11
Meetings/Telecon2014.11.13
Contents
1. Meetings/Telecon2014.11.13
1. Event details
2. Agenda
Event details
https://www.oasis-open.org/apps/org/workgroup/oslc-core/event.php?event_id=36391
New Call-in info:
https://www.oasis-open.org/apps/org/workgroup/oslc-core/members/action_item.php?action_item_id=3689 (access restricted to OASIS members) Chat room:
http://webconf.soaphub.org/conf/room/oslc
Agenda
Roll Call
Approval of
Minutes of 13 November 2014
Next call: 8 January 2015 (No call on 25 December!)
Specification authoring progress, better sections and auto processing of shapes & vocab files
Steve's email
Discovery in 3.0
Discovery proposal
Elaborate scenarios and requirements to help flush out: When to use a link header vs triple?
Need to put together common best practices and approaches, could be that both are needed some times (or one versus the other)
Common pattern for grouping similar containers? Need/desire for delegated config dialogs?
Compatibility with 2.0
Compatibility Draft
Review summary table
Core 3.0 (Overview) Review
Core 3 Draft
Attachments Review
Attachments Draft
Proposal to add oslc:archived to Core follow up
Steve's email
Status update (as time permits)
Actions spec
Resource Preview
Delegated UI Dialogs
Configuration Context Header
Linking Guidance
Any other business
Adjourn
Thanks go to Steve for his input!
--
Arnaud Le Hors - Senior Technical Staff Member, Open Web Standards - IBM Software Group
This email and any attachments are intended solely for the use of the individual or entity to whom it is addressed and may be confidential and/or privileged.
If you are not one of the named recipients or have received this email in error,
(i) you should not read, disclose, or copy it,
(ii) please notify sender of your receipt by reply email and delete this email and all attachments,
(iii) Dassault Systemes does not accept or assume any liability or responsibility for any use of or reliance on this email.
For other languages, go to http://www.3ds.com/terms/email-disclaimer
