<kaz> scribenick: mkovatsc

guideline.md

preparation.md

Matsukura: Created two documents on GitHub (guideline.md and preparation.md)
... Prepartion doc and Guideline doc
... Preparation doc is similar to Burlingame Preparation doc, so initial data is copied from there -- please update!
... Table is HTML, so should be easy enough to edit
... Guideline.md is just a skeleton for items relevent for interoperability
... Need to describe concrete implementation

Matthias: Current Practices for Burlingame had a similar goal. Have you seen this?

Matsukura: Yes. One issue was that only a few people saw the document in time.
... Plan is to merge implementation aspects from Burlingame preparation.md and other missing specifications, e.g., security.
... For the Interface tests, we need to focus on Events
... Binding tests need to be defined by mjkoster
... Security and Semantic Integration are new sections
... Need to be specified as follow-up of this meeting

Matthias: Agree with sectioning and tasks. Security could go to Mccool, Semantics to Darko.

Matsukura: If you have goals for next PlugFest, please fit them into this document (guideline.md)

Burlingame document

Kaz: Have you finalized the Burlingame document?
... Does not have to be perfect, but should be announced to finish it.

Matsukura: Yes, in that sense it is finalized

Kaz: Possibly more content can be transferred to the Prague preparation.md

Matsukura: Yes, possible

Kaz: In particular Introduction and Use Case sections

Matsukura: Yes, there is the plan to update, only managed skeleton so far. Will update.

MLagally: What is the basis for the Servient operations in section 3.2? There are different understandings of the operations out there.

Matsukura: To test interoperability, we need to choice concrete Actions etc.

MLagally: To implement something for the PlugFest, which spec do I need to read? (Which spec defines the operations mentioned here?)

Matsukura: It depends on which aspect you want to test. Often deeper understanding of each spec also emerges during the PlugFest.

<inserted> scribenick: kaz

Matthias: you need to read specification for which you're implementing
... the central spec is TD
... that doesn't handle default values
... if you have implementation which handles Scripting API
... should refer to Scripting API as well
... but Scripting API is optional
... but servient must comply to TD

MLagally: can understand what you mean about TD
... but what about Binding?
... not normative. right?

Matthias: if you do have fancy stuff, then you might want to look into binding template to let TD describe different protocols
... we didn't have binding for previous plugfests
... for action, you need post
... for event, may be more complicated
... additional binding template vocabulary

MLagally: ok

<scribe> scribenick: mkovatsc

Kawaguchi: Which documents will exist now?

<inserted> scribenick: kaz

Matthias: there are 2 documents, guideline.md and preparation.md

Matsukura: preparation.md for logistics

<inserted> scribenick: mkovatsc

Matsukura: For implementation everyone MUST look at guideline.md
... For information about the PlugFest logistics etc. one MAY look at preparation.md
... AOB?
... End of Meeting