https://www.w3.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=GcalvaryW3C Wiki - User contributions [en]2024-03-28T14:31:37ZUser contributionsMediaWiki 1.41.0https://www.w3.org/wiki/index.php?title=MBUI_Telecon_2012_October_11&diff=61462MBUI Telecon 2012 October 112012-10-13T19:53:56Z<p>Gcalvary: /* Current status of the Working group note */</p>
<hr />
<div>Chaired by: Gerrit, scribed by Dave<br />
<br />
== Present ==<br />
<br />
* Gerrit Meixner, DFKI<br />
* Dave Raggett, W3C<br />
* Cristina Cachon, CTIC<br />
* Javier Rodriguez, CTIC<br />
* Ignacio Marin, CTIC<br />
* Heiko Braun, Red Hat<br />
* Jean Vanderdonckt<br />
* Vivian Motti, UCL<br />
* Pascal Beaujeant, UCL<br />
* Nesrine (UCL)<br />
* Gaelle Calvary, LIG<br />
* Sebastian Feuerstack, USC<br />
* Javoslav Pullman, Fraunhofer<br />
* Fabio Paterno, ISTI<br />
* Carmen Santoro, ISTI<br />
* Davide Spano, ISTI<br />
* Paolo Bottini, University of Rome<br />
<br />
<!--<br />
<br />
* Nikolas Kaklanis, ITI<br />
* Paolo Bottini, University of Rome<br />
* Javoslav Pullman, Fraunhofer<br />
* Jean Vanderdonckt<br />
* Vivian Motti, UCL<br />
* Pascal Beaujeant, UCL<br />
* Sebastian Feuerstack, USC<br />
* Marius Orfgen, DFKI<br />
* Nikolas Kaklanis, ITI<br />
* Jaroslav Pullman, Fraunhofer<br />
* Sebastian Feuerstack, USC<br />
* Cristina Cachon, CTIC<br />
* Javier Rodriguez, CTIC<br />
* Ignacio Marin, CTIC<br />
* Vivian Motti, UCL<br />
* Francois Beuvens<br />
* Fabio Paterno, ISTI<br />
* Carmen Santoro, ISTI<br />
* Davide Spano, ISTI<br />
* Joelle Coutaz, LIG<br />
* Jean Vanderdonckt<br />
* Paolo Bottini, University of Rome<br />
--><br />
<br />
== Regrets ==<br />
<br />
* Joëlle Coutaz, LIG<br />
<br />
<!--<br />
* Gaelle Calvary, LIG<br />
--><br />
<br />
<br />
== Planned Agenda ==<br />
<br />
* Current status of the Abstract UI document / recent email by Heiko Braun /<br />
Paolo's introduction<br />
* Current status of the Working group note / Use Case refinement<br />
* Current efforts of the OMG concerning the Interaction Flow Modeling<br />
Language (IFML) / cooperation?<br />
<br />
== Current status of the Abstract UI document ==<br />
<br />
Jean: new definition of the generic requirement just before the section on the definition of the user. Completeness, consistency, extension of concerns, and extensibility<br />
<br />
* [https://docs.google.com/document/d/1UGZz_xaPuSbMtRb4a-14tM9CM8tHmbEWuLVuNNnx25o/edit#heading=h.cdg7frhj8dlu AUI draft spec]<br />
<br />
Thanks to Sebastian for providing new section on modelling. The consolidation is ongoing. Any questions?<br />
<br />
''none raised''<br />
<br />
Thanks also to Sebastian for the list of questions at the end of the document which we can discuss in detail in Lyon.<br />
<br />
Gerrit: sounds very good, and if there are no objections we can proceed as you suggest.<br />
<br />
Jean: if you have any further open questions please add them to the end of the document, or to make other proposals in the document.<br />
<br />
Sebastian: could we try to prepare a stable version prior to the Lyon F2F?<br />
<br />
Jean: perhaps on Thursday 25 October?<br />
<br />
''several voices of approval''<br />
<br />
Jean: please feel free to comment on the requirements as there is a completely new section there.<br />
<br />
== Current status of the Working group note ==<br />
<br />
Gerrit: any questions concerning the introductory document?<br />
<br />
Jaroslav: there was a discussion on new graphics for the simplified Cameleon reference framework. <br />
<br />
Gaelle: in favour of simplified version, but want to keep the notion of "context".<br />
<br />
Jean: if might be interesting to have separate sections for users, context, etc. as these are mixed in the current version.<br />
<br />
Gaelle: if it helps I can provide a proposal.<br />
<br />
Paolo: are we adopting the Cameleon reference framework in this document or is it just one approach?<br />
<br />
Jaroslav: we have a section on user models<br />
<br />
Gaelle: what about the context?<br />
<br />
Jaroslav: that is harder as it is application domain specific. That favours a black box approach as you suggest, where we leave the modelling of the context to other work.<br />
<br />
Fabio: that isn't a particularly important aspect of this document. We should focus on the benefits of the model based approach.<br />
<br />
Jaroslav: this could be useful for other working groups, e.g. for accessibility<br />
<br />
Jean: we could create a minimal model for the user and reference the literature for richer models.<br />
<br />
Jaroslav: we should explain why run-time adapation is important, but we don't need to provide a detailed model beyond what Jean suggests. <br />
<br />
Fabio: a brief explanation is sufficient. <br />
<br />
Jaroslav: we should be more concrete in respect to our examples/use cases.<br />
<br />
Fabio: yes, that is important.<br />
<br />
We need to know who is responsible to do what, otherwise, we won't progress.<br />
<br />
Gerrit: in my opinion, the people who provided the use cases should refine the description.<br />
<br />
Jean: overlap between some use cases<br />
<br />
Gaelle: each use case needs characterising in the table, so that we can decide what we need.<br />
<br />
Jean: I see that the table is really relevant<br />
<br />
Fabio: the table focuses on adaptation rather than the model-based approach, do we need another table?<br />
<br />
Gaelle: either we focus on the state of the art or we envision interactive systems for which model-based approaches is key<br />
<br />
Jean: the table should have 2 sets of criteria separating the goals and the means<br />
<br />
Fabio: that's a good idea. This document is aimed at people who are unfamiliar with model-based approaches, and we need to cover the features and the results.<br />
<br />
Fabio: how should we proceed. Extending the table would be a good start<br />
<br />
Jaroslav: we extracted a list of benefits from the Kaiserslautern F2f, but I need to compare with what we have now.<br />
<br />
Jean: the goal is to start with high level goals and a more extensive structured list.<br />
<br />
Gerrit: you can send me the document you wrote with Vivian, perhaps you could send it to me, and I will attempt to harmonize and extend it.<br />
<br />
== Task Model document ==<br />
<br />
Jean sent a reference to a taxonomy of tasks.<br />
<br />
Fabio reviews. The main question is whether a task is automatic, interactive or something internal to the user.<br />
<br />
We need to understand why we want a classification of different task types. We also need to allow for extensibility to allow people to add further task types as needed.<br />
<br />
Jean: the goal is to provide guidance and as much precision as possible.<br />
<br />
Fabio: we can of course evaluate your reference to how effective the types are<br />
<br />
It is easy to find new task types, but it is a challenge to have a good set that isn't too long<br />
<br />
Jean: there may be some useful new types for us to consider. We have 2 criteria: precision and scalability.<br />
<br />
Fabio: they are in conflict<br />
<br />
Jean: for the moment, we don't force people to use task types, right?<br />
<br />
Fabio: they can choose whether to use the predefined types or to come up with their own.<br />
<br />
Jean: but the task type itself is optional<br />
<br />
Fabio: yes<br />
<br />
Paolo: for interoperability we want to encourage the use of a common set of task types<br />
<br />
Fabio: if we find a good reason to add/refine types we can do so<br />
<br />
== Current efforts of the OMG concerning IFML ==<br />
<br />
''deferred to next week's call''<br />
<br />
''end of meeting''</div>Gcalvaryhttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2012_May_10&diff=58826MBUI Telecon 2012 May 102012-05-10T16:18:23Z<p>Gcalvary: /* Present */</p>
<hr />
<div>== Agenda ==<br />
<br />
see: [http://lists.w3.org/Archives/Public/public-mbui/2012May/0004.html email]<br />
<br />
* Current status of the working group note (use cases, glossary)<br />
* Current status in the two task forces (Task model, Abstract UI)<br />
* Next F2F meetings (June in Pisa, October/November at the Tech Plenary in Lyon?)<br />
<br />
== Present ==<br />
* Dave (W3C)<br />
* Javier, Cristina (CTIC)<br />
* Marc (DFKI)<br />
* Nikos<br />
* Jaroslav (Fraunhofer)<br />
* Carmen, Davide (ISTI)<br />
* Gaelle (Grenoble Institute of Technology, Grenoble)<br />
* Joelle (University Joseph Fourier, Grenoble)<br />
<br />
== Regrets ==<br />
* None<br />
<br />
== Chair ==<br />
* Marc on behalf of Gerrit who couldn't make it today<br />
<br />
== Scribe ==<br />
* Dave<br />
<br />
== Minutes ==<br />
<br />
=== Current status in the two task forces (Task model, Abstract UI) ===<br />
<br />
No one present to represent UCL.<br />
<br />
Carmen: regarding task model spec, we have made some modifications, in particular how to make the meta model accessible. We added a link to the XMI version of the meta model, which is a bit verbose. We need to decide if that is sufficient, or whether to use another approach. We also improved the legibility of the labels. We have included an example of CTT from Serenoa, along with a diagram and a matching text description as a nested list.<br />
<br />
Gaelle: why did you use subclasses rather than actors?<br />
<br />
Carmen: it gives us better control the categories of tasks.<br />
<br />
Gaelle: what about refactoring?<br />
<br />
Carmen: you can still do this, if you use an actor attribute you might lose some control.<br />
<br />
Gaelle: what about an association between a new class and the task class, so the instance can be changed dynamically and more easily than using sub-classes.<br />
<br />
Carmen: we can consider this<br />
<br />
Gaelle: I want to enable every aspect of a task to be dynamically changed.<br />
<br />
Jaroslav: The distinction between human and computer mediated tasks is an important feature.<br />
<br />
Gaelle: in a PC you can allow for flexible interleaving of tasks, but for a more constrained device, this is likely to be replaced by sequences of tasks.<br />
<br />
Jaroslav: ...<br />
<br />
Joelle: the task of saving a file from a word processor can be done by the user or automatically by the application. So the actor can change from a human to the computer. Using an attribute for the actor makes this easy to deal with.<br />
<br />
Davide: saving a file is a system task, it is only the trigger that can be assigned, either to the user or to the system. <br />
<br />
Gaelle: how would you model this in CTT?<br />
<br />
Davide: with tasks for the triggers and a task for the file save operation.<br />
<br />
Gaelle: what happens if you have multiple users?<br />
<br />
Davide: the question is who performs what action. The action of writing the file is always performed by the system. <br />
<br />
Gaelle: the key is who is the actor.<br />
<br />
Carmen: this can be considered as different locations, one for the user and the other for the application.<br />
<br />
Gaelle: how do you deal with multiple users? We agree with the value of sub-classes, but also want to capture the idea of actor including for one or more users.<br />
<br />
Carmen: we have approached multiple users via a means for describing cooperative tasks.<br />
<br />
Dave: what about using simple tables as per the discussion on the list as an easier to read alternative to XMI?<br />
<br />
Carmen: yes, we plan to look at this as for us it would be a better option.<br />
<br />
Davide: we could also introduce hyperlinks between concepts.<br />
<br />
Marc: perhaps we ought to approach the discussion on actors/users by considering a set of use cases.<br />
<br />
Carmen: we can do that, but in parallel with progressing the spec.<br />
<br />
Gaelle: we would support looking at use cases for the task models.<br />
<br />
Carmen: we have associative operators (in regards to Gaelle's comment in the spec on operators). If you have further comments please add them to the document.<br />
<br />
Marc: shall we proceed to the AUI spec?<br />
<br />
Marc asks Javier to explain his comments.<br />
<br />
Dave asks if Javier means to reference concept definitions in the glossary on the Note?<br />
<br />
Javier: yes<br />
<br />
Dave: for normative concepts we need normative definitions, and these will have to be in this spec or a normatively referenced spec.<br />
<br />
Jaroslav: ...<br />
<br />
Marc: we need some examples to drive the discussion on the detailed design.<br />
<br />
Vivian is unable to reach a regular phone and sends an update via email:<br />
<br />
Regarding the AUI document, we are currently working on the meta-model for the AUI, a consolidated version will be send soon. And regarding the requirements that Javier (CTIC) sent, we agree in integrating them in the document, and we invite all to collaborate with more requirements too.<br />
Concerning the question raised by Gaelle last meeting, we believe that completeness is still valid in this context, and maybe one approach to complement this information could be classifying the selected requirements according to their relevance given an application scenario.<br />
<br />
The meta-model and a more consolidated version of the AUI model document will be provided in 3 weeks, before the face-to-face meeting, in which we will have the opportunity to discuss them in more details.<br />
<br />
=== June F2F meeting in Pisa ===<br />
<br />
People would prefer to avoid travelling on Sunday.<br />
<br />
Carmen: we had been planning for starting the MBUI meeting at 9am on Monday June 11, and ending middday on Tuesday June 12.<br />
<br />
Joelle: what about the second half of the week, e.g. Thursday and Friday, as we have a meeting in Metz, France on Monday and Tuesday, and only one of us could make the MBUI meeting in that case.<br />
<br />
Carmen: I will ask Fabio and report back next week.<br />
<br />
Is this okay for everyone else? [Yes]<br />
<br />
Jaroslav: we need to fix the dates and times in order to arrange our travel.<br />
<br />
Carmen: we will let you know as soon as possible.<br />
<br />
Meeting at the W3C Tech Plenary<br />
<br />
Dave: I have made a provisional reservation for an MBUI WG F2F at the W3C Tech Plenary in Lyon, this November. I don't yet know the exact day we would meet just yet.<br />
<br />
=== Current status of the working group note (use cases, glossary) ===<br />
<br />
==== Glossary ====<br />
<br />
Jaroslav: I have been working on the glossary. The Cameleon glossary makes heavy use of acronyms, and think this could be a problem for wider understanding. I would prefer us to avoid acronyms where possible.<br />
<br />
Dave: Yes, I prefer plain language as it is easier to understand.<br />
<br />
Jaroslav: what about synonyms?<br />
<br />
Dave: it would be helpful to list synonyms for each definition where applicable.<br />
<br />
Jaroslav: I also plan to use cross references.<br />
<br />
Dave: yes, that is in the spirit of the Web.<br />
<br />
Gaelle provides some historical background to the origins of the Cameleon glossary in previous work on HCI. There have been many projects hence the synonyms as different projects used different names.<br />
<br />
We need to clarify our preferred terminology for the W3C work.<br />
<br />
Some discussion on the URIs to use for existing glossaries.<br />
<br />
Carmen will try to find a more up to date version of the Cameleon glossary.</div>Gcalvaryhttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2012_May_3&diff=58797MBUI Telecon 2012 May 32012-05-10T11:03:37Z<p>Gcalvary: /* Present */</p>
<hr />
<div>== Agenda ==<br />
<br />
* Current status of the working group note (Use Cases should be finalized<br />
** Benefits, when to use MBUID, tutorial (Dave)<br />
** Current state of the glossary (Jaroslav)<br />
now)<br />
* Current status in the two task forces (Task model, Abstract UI)<br />
* Meeting at W3C Tech plenary (Dave)<br />
* Dave to provide information on becoming an Invited Expert on the wiki and to the mailing list.<br />
* Conversion of the google documents into the W3C technical report format<br />
<br />
== Present ==<br />
<br />
*Present: Dave, Fabio, Joelle, Gaelle, Sebastian, Javier, Nikos<br />
<br />
Please correct the names<br />
<br />
== Regrets ==<br />
<br />
Gerrit due to clashing meetings.<br />
<br />
== Chair ==<br />
<br />
* Dave<br />
<br />
== Scribe ==<br />
<br />
* Dave<br />
<br />
== Minutes ==<br />
<br />
Jaroslav: I have to go early, so can I give my report first?<br />
<br />
Dave: sure.<br />
<br />
== Glossary ==<br />
<br />
Jaroslav: working on the glossary, starting with the glossary from the cameleon project. Sometimes that is a bit limited, as we could provide more generic definitions. <br />
<br />
Joelle: I cannot see the URL for the glossary document.<br />
<br />
Jaroslav: I put it into a new document, linked from the terminology section of the working group note.<br />
<br />
Dave: why a separate document rather than in the note?<br />
<br />
Jaroslav: because I wanted to create a working copy<br />
<br />
Dave: this is an editors' draft so it is very much work in progress, you should consider merging it back into the draft working group note.<br />
<br />
Jaroslav: I would prefer to keep it a separate document for now if that is okay.<br />
<br />
Joelle: we were wondering how to do the editing and would like to contribute.<br />
<br />
Fabio: for each of documents, we have a main editor.<br />
<br />
Joelle: so we can just start editing, right?<br />
<br />
Fabio: we have the three documents and plan to publish something in a fairly short time<br />
<br />
Dave: You can add content to the documents, but please coordinate with the main editors. You can add comments/questions in each document, but please prefix this with your name and use italics and/or a different colour to differentiate from the main text.<br />
<br />
=== Task Models ===<br />
<br />
Dave asks for an update for the task models document<br />
<br />
Fabio: we have put some material into the document, but have a question about how the document is written. The SCXML specification is written with a different approach, should we aim for something closer to that? They don't give a meta model, and instead focus on the XML format.<br />
<br />
Dave: in our case the meta model is central, and the XML serialization is secondary. However, I think we will need to provide a textual equivalent of the UML diagrams to ensure that our specification is accessible to people who can't see the diagram.<br />
<br />
Dave: the WG Note will explain the concepts and provide use cases and examples, so we can be relatively concise in the AUI and Task Models specifications, which will just need to provide brief explanations of the terms, the definition of the meta model, and an XML schema as a possible serialization format.<br />
<br />
Dave how long you think you need to complete the document?<br />
<br />
Fabio: about a couple of weeks (next week is the Chi conference)<br />
<br />
Joelle: how can we deal with comments?<br />
<br />
Fabio: put them into the document and we can discuss them via email or the teleconference.<br />
<br />
Joelle asks about the scope of the document<br />
<br />
Fabio: this is aimed at a standard and hence we are taking a pragmatic approach. We don't need to compare the meta model with other approaches as you would in an academic paper.<br />
<br />
=== Abstract User Interface Models ===<br />
<br />
Javier: I have made some contributions in red and am waiting for comments.<br />
<br />
Dave: the primary editors aren't present on this call, unfortunately, I will email them for a progress report.<br />
<br />
Dave: can we help with Javier's comments/questions today?<br />
<br />
Javier: we need to take into account the mapping between the AUI and CUI, this needs to be unambiguous.<br />
<br />
Joelle: I don't think this is something we should take as a requirement.<br />
<br />
Javier: when we have an AUI model, we need to be able to map it to the CUI for the target platforms and modalities.<br />
<br />
Joelle: maybe we need both forward and backward transformations?<br />
<br />
Fabio: perhaps we could cover this in the working group note?<br />
<br />
Dave: yes, and if appropriate we could create a Working Draft for formal requirements<br />
<br />
Joelle: that could be worthwhile, and would allow us to check that the standards we are designing are fully general.<br />
<br />
Dave: our AUI and Task Models aren't claimed to be fully general, but rather are designed to be fit for purpose for the range of use cases we describe in the working group note.<br />
<br />
???: Agreed.<br />
<br />
== Next Call - May 11 ==<br />
<br />
Dave to follow up via email on:<br />
<br />
* Invited Expert process<br />
* Meeting at Tech Plenary<br />
* Reminder to send regrets if you can't attend a given telecon</div>Gcalvaryhttps://www.w3.org/wiki/index.php?title=MBUI_WG_Face_to_Face,_KaisersLautern_2012&diff=56172MBUI WG Face to Face, KaisersLautern 20122012-01-24T12:11:59Z<p>Gcalvary: /* Hotels */</p>
<hr />
<div>* [[Model-Based User Interfaces|MBUI Wiki Home Page]]<br />
<br />
[[File:DFKI-Kaiserslautern-130001.jpg]]<br />
<br />
== Introduction ==<br />
<br />
<br />
* Dates: February 9th to 10th<br />
* Location: DFKI, Kaiserslautern, Germany<br />
<br />
'''Please remember to add yourself to the list of participants at the bottom of this page.'''<br />
<br />
With our charter calling for first public working drafts in March, we would like to invite you to our first face to face meeting which will take place in Kaiserslautern in Germany, and will be hosted by DFKI. Our<br />
local organizer is Moritz Kümmerling <moritz dot kuemmerling at dfki dot de>.<br />
<br />
The proposed date of the meeting is February 9th to 10th. We realize that this is quite soon, but it is important for us to get stuck in as it will take some time and effort to go from initial submissions to<br />
first public working drafts. We are working hard to get the submissions in time! If you plan to make a submission please get in contact with the MBUI WG staff contact Dave Raggett <dsr at w3 dot org> as soon as possible!<br />
<br />
We are expecting to provide a means for people to call in remotely if they can't be present in person. If you can't make the 9th and 10th, and would like to move the dates please let Moritz and I know and we will do<br />
our best to accommodate your request, but note that the previous week and the following two weeks are unavailable.<br />
<br />
== Getting to DFKI ==<br />
<br />
* Address:<br />
DFKI GmbH,<br />
Trippstadter Strasse 122,<br />
67663 Kaiserslautern,<br />
Germany<br />
<br />
* [[Media:Kaiserslautern-dfki-map.pdf | map of DFKI location in Kaiserslautern]]<br />
<br />
=== By Plane ===<br />
<br />
It is most convenient to fly to either Frankfurt or Stuttgart. Kaiserslautern can be reached by train from both airports. Travel time from Frankfurt (M) Flughafen to Kaiserslauten Hbf is around 2 hours with a change of train at Mannheim. For schedules try<br />
<br />
* http://reiseauskunft.bahn.de/bin/query.exe/en<br />
<br />
You can then take a bus or taxi to DKFI as described below:<br />
<br />
=== By Bus ===<br />
<br />
Leave the Central station „Kaiserslautern Hauptbahnhof“ through the main entrance. From there several Busses (115, 106) leave regularly to the station “Fraunhofer Zentrum”. For any questions an information desk is located at the main entrance of the central station.<br />
<br />
=== By Taxi ===<br />
<br />
Leave the Central station “Kaiserslautern Hauptbahnhof” through the main entrance and turn left. Several Taxis should be waiting there for passengers. If not you can call a taxi via the number: 0049/631/366777<br />
<br />
=== By car from Mannheim ===<br />
<br />
Leave the freeway at the exit towards "Kaiserslautern Centrum". At the intersection turn left into Donnersbergstraße. At the next intersection, continue straight on to the intersection Entersweilerstraße. Now turn right and follow the Entersweilerstraße into the Barbarossastraße and Logenstraße. Past the head postal service and go further straight ahead. Then turn left into the Trippstadter Straße, pass through the train underpass and turn right again. At the next traffic light go straight on. The DFKI building appears after about 800 meters on the right side.<br />
<br />
=== By car from Saarbrücken ===<br />
<br />
Leave the freeway A6 at the exit towards "Kaiserslautern West". Continue along B270 by following the sign „Universität“ and turn right directly after crossing the bridge. Follow the B40 for about 2 km (you pass 2 traffic lights). Then turn right into Brandenburger Straße towards Stadtmitte/ Universität. Continue along Brandenburger Straße until you turn right into Trippstadter Straße. The DFKI building appears after about 800 meters on the right side.<br />
<br />
Moritz will provide a list of hotels for your consideration along with details of how to get to the DFKI site itself. The agenda will also be put onto the wiki. Here is some initial information about DFKI:<br />
<br />
* http://www.dfki.de/web/kontakt/dfki-kaiserslautern<br />
<br />
== Hotels ==<br />
<br />
For booking and reservations it is likely to be cheaper using booking portals for your reservation than contacting the hotel of your choice directly. Such booking portals are e.g. www.booking.com or www.hotels.de or www.trivago.de<br />
<br />
'''ALCATRAZ Hotel at Japanese Garden'''<br/><br />
Price: ca. 62 € per night including breakfastn<br/><br />
Distance to DFKI: ca. 3.6 kmn<br/><br />
Website: http://www.hotel-alcatraz.de/<br />
<br />
'''Novotel Kaiserslautern'''<br/><br />
Price: ca. 64 € per night including breakfast<br/><br />
Distance to DFKI: ca. 3.7 km<br/><br />
Website: http://www.novotel.com/de/hotel-5399-novotel-kaiserslautern/index.shtml<br />
<br />
'''Hotel Bremerhof'''<br/><br />
Price: ca. 64 € per night including breakfast<br/><br />
Distance to DFKI: ca. 4.7 km<br/><br />
Website: http://bremerhof-kl.de/modx/<br />
<br />
'''City Hotel Kaiserslautern'''<br/><br />
Price: ca. 65 € per night including breakfast<br/><br />
Distance to DFKI: ca. 2.5 km<br/><br />
Website: http://www.city-hotel-kaiserslautern.de/<br />
<br />
'''Design Hotel Zollamt'''<br/><br />
Price: ca. 98 € per night including breakfast<br/><br />
Distance to DFKI: 1.3 km<br/><br />
Website: http://www.hotel-zollamt.de/rooms.html<br />
<br />
'''SAKS Urban Design Hotel'''<br/><br />
Price: ca. 99 € per night including breakfast<br/><br />
Distance to DFKI: 3.1 km<br/><br />
Website: http://sakshotels.com/<br />
<br />
<h2 id="registered">Registered Participants</h2><br />
<br />
Please add your name and affiliation here. If you have special dietary requirements, please remember to contact Moritz Kümmerling (see email address above).<br />
<br />
* Dave Raggett, W3C<br />
* Gerrit Meixner, DFKI<br />
* Marc Seissler, DFKI<br />
* Moritz Kuemmerling, DFKI<br />
* Marius Orfgen, DFKI<br />
* Nikolaos Kaklanis, CERTH/ITI<br />
<br />
Remote participation:<br />
* Gaelle Calvary, Grenoble INP<br />
* Joelle Coutaz, UJF</div>Gcalvary