OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cti-interoperability message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Modified: CTI TC Interoperabilty SC - Monthly Meeting


Submitter's message
Added details for the primary agenda item: Interoperability Certification Framework.
-- Patrick Maroney
Event Title: CTI TC Interoperabilty SC - Monthly Meeting

Date: Wednesday, 14 September 2016, 02:00pm to 02:30pm EDT
Location: GoToMeeting
Description

GoToMeeting Details sent via OOB Email.

Note:

  • I'm in the middle of switching from WebEx to GoToMeeting -
  • Please delete any WebEx based meetings from your Calendars.

 


RSVP

Agenda

Agenda:

  • Decision Process for Interoperability Framework (e.g., Formal, Self-Certification)
    • OASIS CTI TC IO SC Certification Framework WG Kickoff Meeting - Doodle Poll sent to Interoperability SC Members
    • Agenda for Certification Framework WG Kickoff Meeting is to review, formalize, and frame the set of Certification Framework options for decision by the CTI TC.
      • (1) Uncontrolled self-certification: each candidate defines or uses its own test framework and test suite, and executes its own testing, without oversight. The testing is based on minimal test material produced by the TC, typically a set of test assertions and test guidelines. The candidate posts its test results, and remains open for particular inquiries from 3rd parties (e.g. customers) about test details. This option does not provide much guarantee – it is “user beware” – But is easiest to support by OASIS and TCs.
      • (2) Resource-based local self-certification: In this option, the testing is entirely done on the user side, but the resources necessary to do so are provided by the TC. The user downloads test framework components and test suites and runs them locally. WS-I is an example of this style of certification. This option provides more guarantee, as the tools and test suites are same for all candidates and are developed and validated by a third party.
      • (3) Service-based self-certification: In this option, testing is provided as a remote automated service. In addition to the test tools and test suite being developed by a third party, the core of the testing operation takes place on or is controlled by the service site, which is where test results are collected. A variant would allow the user to upload its implementation or part of it on the service site. In (b) and (c) 
  • Interoperability SC Github Repositories
  • Interim Ad Hoc Interoperability Initiative
  • RSA Interoperability Demonstration WG Update
  • Note: We have some important decisons to make.  Please RSVP  to indicate if you are planning to Attend


Owner: Patrick Maroney
Group: CTI Interoperability Subcommittee
Sharing: This event is shared with the OASIS Open (General Membership), General Public, and OASIS Cyber Threat Intelligence (CTI) TC groups. Public Event Link
  • Learn more about subscribing here.
  • View the CTI Interoperability Subcommittee calendar here.
  • You may receive future notifications with updates to this event. Update the event on your calendar by accepting the changes.

Attachment: ical_43420.ics
Description: application/ics

BEGIN:VCALENDAR
CALSCALE:GREGORIAN
METHOD:REQUEST
VERSION:2.0
PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:STANDARD
DTSTART:20001029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T060000Z
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T070000Z
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
STATUS:CONFIRMED
TRANSP:OPAQUE
DTSTAMP:20160914T171403Z
DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20160914T140000
DTEND;VALUE=DATE-TIME;TZID=America/New_York:20160914T143000
SEQUENCE:2
SUMMARY:CTI TC Interoperabilty SC - Monthly Meeting
LOCATION:GoToMeeting
LAST-MODIFIED:20160914T171403Z
ORGANIZER:workgroup_mailer@lists.oasis-open.org
DESCRIPTION:GoToMeeting Details sent via OOB Email.\n\nNote:\n\n\n	I&#39
 \;m in the middle of switching from WebEx to GoToMeeting -\n
 	Please delete any WebEx based meetings from your Calendars.
 \n\n\n \n\nAgenda: Agenda:\n\n\n	Decision Process for Intero
 perability Framework (e.g.\, Formal\, Self-Certification)\n	
 \n		OASIS CTI TC IO SC Certification Framework WG Kickoff Me
 eting - Doodle Poll sent to Interoperability SC Members\n		A
 genda for Certification Framework WG Kickoff Meeting is to r
 eview\, formalize\, and frame the set of Certification Frame
 work options for decision by the CTI TC.\n		\n			(1) Uncontr
 olled self-certification: each candidate defines or uses its
  own test framework and test suite\, and executes its own te
 sting\, without oversight. The testing is based on minimal t
 est material produced by the TC\, typically a set of test as
 sertions and test guidelines. The candidate posts its test r
 esults\, and remains open for particular inquiries from 3rd 
 parties (e.g. customers) about test details. This option doe
 s not provide much guarantee &ndash\; it is &ldquo\;user bew
 are&rdquo\; &ndash\; But is easiest to support by OASIS and 
 TCs.\n			(2) Resource-based local self-certification: In thi
 s option\, the testing is entirely done on the user side\, b
 ut the resources necessary to do so are provided by the TC. 
 The user downloads test framework components and test suites
  and runs them locally. WS-I is an example of this style of 
 certification. This option provides more guarantee\, as the 
 tools and test suites are same for all candidates and are de
 veloped and validated by a third party.\n			(3) Service-base
 d self-certification: In this option\, testing is provided a
 s a remote automated service. In addition to the test tools 
 and test suite being developed by a third party\, the core o
 f the testing operation takes place on or is controlled by t
 he service site\, which is where test results are collected.
  A variant would allow the user to upload its implementation
  or part of it on the service site. In (b) and (c) \n		\n		\
 n	\n	\n	Interoperability SC Github Repositories\n	Interim Ad
  Hoc Interoperability Initiative\n	RSA Interoperability Demo
 nstration WG Update\n	Note: We have some important decisons 
 to make.  Please RSVP  to indicate if you are planning to At
 tend\n\nGroup: CTI Interoperability Subcommittee\nCreator: P
 atrick Maroney
URL:https://www.oasis-open.org/apps/org/workgroup/cti-interoperability/event.php?event_id=43420
UID:https://www.oasis-open.org/apps/org/workgroup/cti-interoperability/event.php?event_id=43420
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]