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

 


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-promcode message

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


Subject: minutes of TC call of October 22, 2020


Describe October 22 2020 

Agenda 

Scribe nomination 

Roll Call 

Next meeting: November 5, 2020 

Voting Rights Held by: 

  • Mikio Aoyama 
  • Kazuo Yabuta 
  • Masaki Wakao 
  • Tom Kamimura 
  • Shigeaki Matsumoto 
  • Hiroyuki Yoshida 

Chair: Tom Kamimura for Mikio Aoyama 

Scribe: Tom Kamimura 

Attendees: 

  • Tom Kamimura 
  • Masaki Wakao 
  • Kazuo Yabuta 
  • Shinji Matsuoka 
  • Hiroyuki Yoshida 
  • Shigeaki Matsumoto 

Discussions 

  1. Conformance clause 
    1. Kamimura explained the status of revising a working draft by adding the conformance clause as required by the OASIS for a working draft to move to CSD. The conformance guildeline is published at http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html#_Toc354926528 . To meet the guideline, Kammimura created a draft of the conformance clause in the current working draft (https://tools.oasis-open.org/version-control/browse/wsvn/oslc-promcode/shape/trunk/spec.html). The conformance clause of the draft describes only PROMCODE specific items. It does not explicitly include individual items on requirements from OSLC Core and it only says that PROMCODE servers and clients must be compliant with OSLC Core specification. 
    2. Other OSLC domain specifications such as CM and QM do specify each key item from OSLC Core explicitly, and therefore are easier to understand and validate the conformance of implementations. After discussions, it was agreed to follow these specifications and to modify our draft to explicitly include key items from OSLC Core into the specification. 
    3. To this end, it was agreed to look at key items from OSLC Core to see if existing implementations are compliant with all the MUST level requirements of OSCL Core. Also, there were discussions on authentication, partical resource representation, and resource paging in PROMCODE. Matsumoto-san felt that resource paging may be useful for PROMCODE. Currently resource paging is not mentioned in the specification. In the end, it was agreed to do the following. 
      1. Determine if the current implementations (Fujutsu, NEC, and Nanzan University) are compliant with MUST level requirements of OSLC Core. 
      2. Determine if there is a need to override key requirement items (e.g., Authentication, Paritial Resource Representation, Resource Paging..) of OSLC Core in PROMCODE. 
  2. Vocabulary and shape files 
    1. Wakao-san sent vocabulary and shape files to Andrew who created a work item http://%20https://github.com/oslc-op/website/issues/278 for them to be processed. Wako-san will continue the communication with Andrew. 

Actions 

  • Matsumoto-san, Matsuoka-san and Aoyama-san to do 1.3.1 and 1.3.2 as defined above. 


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