Difference between revisions of "Meetting: Web Components 2016-06-01"

From wiki.gpii
Jump to: navigation, search
(Important dates)
m (+ category: web components)
 
Line 5: Line 5:
 
== Discussion ==
 
== Discussion ==
 
* FHG wants to extend Media Queries to Context queries.
 
* FHG wants to extend Media Queries to Context queries.
* Precompailer to help developers is planned to be  implemented by Alechandro in his Bc. Theses.
+
* Precompiler to help developers is planned to be  implemented by Alechandro in his Bc. Theses.
  
Discussion about decission points:
+
Discussion about decision points:
 
* Id of a certain fintch in preference set is problematic: all fintches must be known in advance,
 
* Id of a certain fintch in preference set is problematic: all fintches must be known in advance,
 
* Solution: Web Component framework as solution, abstraction layer between match maker and  framework,
 
* Solution: Web Component framework as solution, abstraction layer between match maker and  framework,
 
* matchmaker as first decission point: preference set is transformed to framework specific terms,
 
* matchmaker as first decission point: preference set is transformed to framework specific terms,
* seccond decission point needed: Which Webcomponent/ which variant of a Web Component is needed? Either Web Component or Resource server could decide?  
+
* seccond decision point needed: Which Web component/ which variant of a Web Component is needed? Either Web Component or Resource server could decide?  
 
* Better: Resource server since it is the only component that knows all Web Components / variants.
 
* Better: Resource server since it is the only component that knows all Web Components / variants.
 
* Idea: Resource server sends information to the client,  In which parameter range the  current variant is optimal  
 
* Idea: Resource server sends information to the client,  In which parameter range the  current variant is optimal  
Line 27: Line 27:
  
 
== Todos ==
 
== Todos ==
* Alex: look for students which help with the implementation during summer time (Inovation project),
+
* Alex: look for students which help with the implementation during summer time (Innovation project),
 +
 
 +
 
 +
[[Category:Web Components]]

Latest revision as of 16:14, 15 March 2017

Time and date: 10.00 pm - 12:00 pm; June 1st, 2016 Location: Fraunhofer IAO, Nobelstraße 12, 70569 Stuttgart; Participants: Daniel Ziegler, Lukas Smirek, Alexander Henka (remote),

Discussion

  • FHG wants to extend Media Queries to Context queries.
  • Precompiler to help developers is planned to be implemented by Alechandro in his Bc. Theses.

Discussion about decision points:

  • Id of a certain fintch in preference set is problematic: all fintches must be known in advance,
  • Solution: Web Component framework as solution, abstraction layer between match maker and framework,
  • matchmaker as first decission point: preference set is transformed to framework specific terms,
  • seccond decision point needed: Which Web component/ which variant of a Web Component is needed? Either Web Component or Resource server could decide?
  • Better: Resource server since it is the only component that knows all Web Components / variants.
  • Idea: Resource server sends information to the client, In which parameter range the current variant is optimal
  • Daniel has implemented a local profile store to simplify development processes (profiles contain information usually send by the match maker).

Framework requirements

  • Register Fintches in browser,
  • implement all functions required by Web Components,
  • ...

Important dates

  • stable version in Dez. 2016, available in DSpace,
  • M36 next deliverable (SP2),

Todos

  • Alex: look for students which help with the implementation during summer time (Innovation project),