Meeting transcript:
speaker: G
text: Time .
speaker: C
text: Thanks .
speaker: G
text: Are you Fey ?
speaker: D
text: I am Fey ,
speaker: G
text: Oh .
speaker: D
text: yeah .
speaker: G
text: Hi .
speaker: G
text: I think we 've met before ,
speaker: D
text: Hi .
speaker: B
text: What day is today ?
speaker: G
text: like , I remember talking to you about Aspect or something like that at some point or other .
speaker: D
text: A couple times yeah .
speaker: F
text: It 's the uh twenty <disfmarker> nineteenth .
speaker: B
text: Nineteenth ?
speaker: D
text: That 's right ,
speaker: D
text: yeah .
speaker: G
text: So .
speaker: D
text: And you were my GSI briefly , until I dropped the class .
speaker: B
text: Right , right .
speaker: G
text: Oh that 's right .
speaker: D
text: But .
speaker: G
text: Well .
speaker: G
text: No offense .
speaker: C
text: OK , wh wh
speaker: G
text: Like .
speaker: C
text: Yeah .
speaker: C
text: OK .
speaker: C
text: Some in some introductions are in order .
speaker: G
text: Oh , OK
speaker: G
text: sorry .
speaker: C
text: OK .
speaker: G
text: Getting ahead of myself .
speaker: C
text: So .
speaker: C
text: Um . For those who don't know <disfmarker>
speaker: C
text: Everyone knows me ,
speaker: C
text: this is great .
speaker: G
text: Yay !
speaker: C
text: Um , apart from that , sort of the old gang , Johno and Bhaskara have been with us from <disfmarker> from day one
speaker: E
text: Hi .
speaker: C
text: and um they 're engaged in <disfmarker> in various activities , some of which you will hear about today .
speaker: C
text: Ami is um our counselor and spiritual guidance
speaker: C
text: and um also interested in problems concerning reference of the more complex type ,
speaker: E
text: Oh wow .
speaker: A
text: Well .
speaker: C
text: and um he sits in as a interested participant and helper .
speaker: C
text: Is that a good characterization ?
speaker: A
text: u That 's pretty good , I think .
speaker: C
text: I don't know .
speaker: A
text: Yeah .
speaker: A
text: Thanks .
speaker: C
text: OK .
speaker: C
text: Keith is not technically one of us yet ,
speaker: E
text: Not yet .
speaker: C
text: ha - ha .
speaker: G
text: " One of us . "
speaker: C
text: but um it 's too late for him now .
speaker: E
text: Yeah right .
speaker: C
text: So .
speaker: E
text: I 've got the headset on after all .
speaker: C
text: Um .
speaker: C
text: Officially I guess he will be joining us in the summer .
speaker: E
text: yes .
speaker: C
text: And um hopefully it is by <disfmarker> by means of Keith that we will be able to get a b a better formal and a better semantic um idea of what a construction is
speaker: C
text: and um how we can make it work for us .
speaker: C
text: Additionally his interest um surpasses um English
speaker: C
text: because it also entails German ,
speaker: C
text: an extra capability of speaking and writing and understanding and reading that language .
speaker: C
text: And um , is there anyone who doesn't know Nancy ?
speaker: C
text: Do you <disfmarker> do you know Nancy ?
speaker: G
text: Me ?
speaker: G
text: Mm - hmm .
speaker: E
text: I know Nancy .
speaker: C
text: OK .
speaker: B
text: I made that joke already , Nancy , sadly .
speaker: G
text: What ?
speaker: B
text: The " I don't know myself " joke .
speaker: G
text: You did ?
speaker: G
text: When ?
speaker: B
text: Uh before you came in .
speaker: G
text: Oh .
speaker: G
text: About me or you ?
speaker: E
text: Man !
speaker: B
text: About me .
speaker: G
text: OK . <vocalsound> OK .
speaker: A
text: You could do it about you .
speaker: G
text: Well I didn't know .
speaker: B
text: Yeah .
speaker: G
text: I didn't mean to be humor copying ,
speaker: G
text: but OK ,
speaker: G
text: sorry .
speaker: G
text: Yes , I know myself .
speaker: G
text: It 's OK .
speaker: G
text: It 's a <disfmarker>
speaker: C
text: OK .
speaker: C
text: And um Fey is with us as of six days ago officially ?
speaker: D
text: Officially ,
speaker: D
text: yeah .
speaker: C
text: Officially ,
speaker: C
text: but in reality already um much much longer
speaker: C
text: and um um next to some <disfmarker> some more or less bureaucratic uh stuff with the <disfmarker> the data collection she 's also the wizard in the data collection
speaker: G
text: Of Oz .
speaker: C
text: Um ,
speaker: D
text: It 's very exciting .
speaker: C
text: we 're sticking with the term " wizard " ,
speaker: D
text: Yes .
speaker: D
text: Yes .
speaker: C
text: OK .
speaker: C
text: and um
speaker: G
text: Not witch - like .
speaker: B
text: Wizardette .
speaker: E
text: Wizard .
speaker: F
text: Wizardess .
speaker: C
text: Sorceress , I think .
speaker: G
text: OK .
speaker: D
text: Wizard .
speaker: C
text: wizard
speaker: G
text: OK .
speaker: C
text: uh by by popular vote
speaker: C
text: um
speaker: G
text: Didn't take a vote ?
speaker: G
text: OK .
speaker: C
text: OK , um , why don't we get started on that subject anyways .
speaker: C
text: Um , so we 're about to collect data
speaker: C
text: and um the uh s the following things have happened since we last met .
speaker: C
text: When will we three meet again ?
speaker: C
text: And um
speaker: G
text: More than three of us .
speaker: C
text: what happened is that um , " A " , <comment> there was some confusion between you and Jerry with the <disfmarker> that leading to your talking to Catherine Snow ,
speaker: C
text: and he was uh he <disfmarker> he agreed completely that some something confusing happened .
speaker: C
text: Um his idea was to get sort of the l the lists of mayors of the department ,
speaker: C
text: the students .
speaker: C
text: It <disfmarker> it 's exactly how you interpreted it ,
speaker: E
text: The list of majors in the department ?
speaker: C
text: sort of s
speaker: D
text: M m Majors ?
speaker: C
text: Ma - majors , majors .
speaker: D
text: Majors ?
speaker: D
text: OK , mayor <disfmarker>
speaker: C
text: " Mayors " .
speaker: D
text: Something I don't know about these
speaker: C
text: Majors .
speaker: G
text: The department has many mayors .
speaker: C
text: Majors
speaker: D
text: OK .
speaker: C
text: and um just sending the <disfmarker> the little write - up that we did on to those email lists
speaker: D
text: OK .
speaker: D
text: Yeah , yeah , yeah .
speaker: D
text: But <disfmarker>
speaker: D
text: Yeah .
speaker: C
text: uh <disfmarker>
speaker: D
text: So it was really Carol Snow who was confused , not me and not Jerry .
speaker: C
text: Yep , yep , yep .
speaker: C
text: OK .
speaker: C
text: So .
speaker: D
text: That 's good .
speaker: C
text: So , that is uh <disfmarker>
speaker: D
text: So I should still do that .
speaker: C
text: Yep .
speaker: D
text: OK .
speaker: D
text: And using the thing that you wrote up .
speaker: C
text: And <disfmarker>
speaker: C
text: Yep .
speaker: D
text: OK .
speaker: C
text: Wonderful .
speaker: C
text: And um we have a little description of asking peop subjects to contact Fey for you know recruiting them for our thing
speaker: C
text: and um there was some confusion as to the consent form , which is basically that <disfmarker> that what what you just signed
speaker: G
text: Right .
speaker: C
text: and since we have one already um <disfmarker>
speaker: G
text: Did Jerry talk to you about maybe using our class ?
speaker: G
text: the students in the undergrad class that he 's teaching ?
speaker: C
text: Um well he said um we <disfmarker> definitely " yes " ,
speaker: G
text: e
speaker: C
text: however there is always more people in a <disfmarker> in a facul uh in a department than are just taking his class or anybody else 's class at the moment
speaker: G
text: Yeah .
speaker: C
text: and one should sort of reach out and try and get them all .
speaker: G
text: OK , but th I guess it 's that um people in his class cover a different set
speaker: G
text: so <disfmarker>
speaker: G
text: than the c
speaker: G
text: is the CogSci department that you were talking about ?
speaker: D
text: I guess .
speaker: G
text: uh reaching out to ?
speaker: D
text: See
speaker: G
text: Cuz we have you know people from other areas
speaker: D
text: that 's what I suggested to him , that people like <disfmarker> like Jerry and George and et cetera just <disfmarker>
speaker: C
text: Yeah .
speaker: G
text: advertise in their classes as well .
speaker: D
text: Yeah
speaker: D
text: or even I could <disfmarker> you know I could do the actual <disfmarker>
speaker: G
text: Cuz I mean I <disfmarker> I know how to contact our students ,
speaker: C
text: Mm - hmm .
speaker: D
text: That 's generally the way it 's done .
speaker: G
text: so if there 's something that you 're sending out you can also s um send me a copy ,
speaker: C
text: Yeah .
speaker: G
text: me or Bhaskara could <disfmarker> either of us could post it to
speaker: G
text: uh
speaker: G
text: is it <disfmarker>
speaker: G
text: if it 's a general solicitation that you know is just contact you then we can totally pro post it to the news group
speaker: D
text: A mailing list .
speaker: C
text: Mm - hmm .
speaker: D
text: Yeah .
speaker: C
text: Yeah .
speaker: G
text: so .
speaker: C
text: Do it .
speaker: D
text: That 's <disfmarker>
speaker: C
text: Yeah .
speaker: G
text: OK ,
speaker: G
text: so you 'll send it
speaker: G
text: or something
speaker: G
text: so .
speaker: C
text: As a matter of fact , if you <disfmarker>
speaker: D
text: I can send it .
speaker: D
text: I 'll send it ,
speaker: G
text: You can send it to me .
speaker: C
text: if <disfmarker>
speaker: G
text: OK .
speaker: D
text: yeah .
speaker: C
text: Now , i
speaker: G
text: Don't worry ,
speaker: G
text: we <disfmarker> this doesn't concern you anymore , Robert .
speaker: G
text: It 's fine .
speaker: C
text: How <disfmarker> however I suggest that if you <disfmarker> if you look at your email carefully you may think <disfmarker> you may find that you already have it .
speaker: G
text: Oops .
speaker: G
text: Already ?
speaker: G
text: Really ?
speaker: G
text: Oops .
speaker: D
text: Probab
speaker: C
text: Maybe .
speaker: C
text: OK .
speaker: G
text: I don't remember getting anything .
speaker: C
text: W we 'll see .
speaker: C
text: Anyhow ,
speaker: C
text: um the uh
speaker: C
text: Yeah , not only
speaker: C
text: Also we will talk about Linguistics and of course Computer Science .
speaker: G
text: Mm - hmm .
speaker: C
text: Um and then , secondly , we had , you may remember , um the problem with the re - phrasing ,
speaker: C
text: that subject always re - phrase sort of the task that uh we gave them ,
speaker: B
text: Right .
speaker: C
text: and so we had a meeting on Friday talking about how to avoid that ,
speaker: C
text: and it proved finally fruitful in the sense that we came up with a new scenario for how to get the <disfmarker> the subject m to really have intentions
speaker: C
text: and sort of to act upon those ,
speaker: C
text: and um
speaker: C
text: there the idea is now that next actually we <disfmarker> we need to hire one more person to actually do that job
speaker: C
text: because it <disfmarker> it 's getting more complicated .
speaker: C
text: So if you know anyone interested in <disfmarker> in what i 'm about to describe , tell that person to <disfmarker> to write a mail to me or Jerry soon ,
speaker: C
text: fast .
speaker: C
text: Um <vocalsound> the idea now is to sort of come up with a high level of sort of abstract tasks
speaker: C
text: " go shopping "
speaker: C
text: um " take in uh a batch of art "
speaker: C
text: um
speaker: C
text: " visit <disfmarker>
speaker: C
text: do some sightseeing "
speaker: C
text: blah - blah - blah - blah - blah ,
speaker: C
text: sort of analogous to what Fey has started in <disfmarker> in <disfmarker> in compiling <disfmarker> compiling here
speaker: C
text: and already <disfmarker> she has already gone to the trouble of <disfmarker> of anchoring it with specific um o <comment> um entities and real world places you will find in Heidelberg .
speaker: C
text: And um .
speaker: C
text: So out of these f s these high level categories the subject can pick a couple ,
speaker: C
text: such as if <disfmarker> if there is a cop uh a category in emptying your roll of film , the person can then decide " OK , I wanna do that at this place " ,
speaker: C
text: sort of make up their own itinerary a and <disfmarker> and tasks
speaker: C
text: and the person is not allowed to take sort of this h high level category list with them ,
speaker: C
text: but uh
speaker: C
text: the person is able to take notes on a map that we will give him and the map will be a tourist 's sort of schematic representation with <disfmarker> with symbols for the objects .
speaker: C
text: And so , the person can maybe make a mental note that " ah yeah I wanted to go shopping here "
speaker: C
text: and " I wanted to maybe take a picture of that "
speaker: C
text: and " maybe um eat here "
speaker: C
text: and then goes in and solves the task with the system ,
speaker: C
text: IE <comment> Fey ,
speaker: C
text: and um
speaker: C
text: and we 're gonna try out that <disfmarker>
speaker: C
text: Any questions ?
speaker: G
text: so um y you 'll have those say somewhere what their intention was <disfmarker>
speaker: G
text: so you still have the <disfmarker> the nice thing about having data where you know what the actual intention was ?
speaker: C
text: Mm - hmm . Yeah .
speaker: G
text: But they will um <disfmarker>
speaker: G
text: There 's nothing that says you know " these are the things you want to do "
speaker: G
text: so they 'll say " well these are the things I want to do "
speaker: G
text: and <disfmarker>
speaker: G
text: Right ,
speaker: G
text: so they 'll have a little bit more natural interaction ?
speaker: G
text: OK .
speaker: C
text: Hopefully .
speaker: G
text: Mm - hmm .
speaker: F
text: So they 'll be given this map , which means that they won't have to like ask the system for in for like high level information about where things are ?
speaker: C
text: Yeah it 's a schematic tourist map .
speaker: C
text: So it 'll be uh i it 'll still require the <disfmarker> that information
speaker: C
text: and An
speaker: G
text: It w it doesn't have like streets on it that would allow them to figure out their way <disfmarker>
speaker: C
text: N not <disfmarker> not <disfmarker> not really the street network .
speaker: G
text: OK .
speaker: C
text: Nuh .
speaker: E
text: So you 're just saying like what part of town the things are in or whatever ?
speaker: C
text: Yeah a
speaker: C
text: and um
speaker: C
text: the map is more a means for them to have the buildings and their names
speaker: C
text: and maybe some ma ma major streets and their names
speaker: G
text: Mm - hmm .
speaker: C
text: and we want to maybe ask them , if you have <disfmarker> get it sort of isolated street
speaker: C
text: the <disfmarker> the , whatever ,
speaker: C
text: " River Street " ,
speaker: C
text: and they know that <disfmarker> they have decided that , yes , that 's where they want to do this kind of action um that they have it with them and they can actually read them
speaker: C
text: or sort of have the label for the object
speaker: C
text: because it 's too hard to memorize all these st strange German names .
speaker: C
text: And then we 're going to have another <disfmarker> we 're gonna have w another trial run
speaker: C
text: IE the first with that new setup tomorrow at two
speaker: C
text: and we have a real interesting subject which is Ron Kay
speaker: C
text: for who <disfmarker> those who know him , he 's the founder of ICI .
speaker: C
text: So he 'll <disfmarker> he 's around seven seventy years old , or something .
speaker: G
text: I didn't know he was the founder .
speaker: G
text: That 's <disfmarker>
speaker: G
text: OK .
speaker: C
text: And he also approached me and he offered to help <vocalsound> um our project
speaker: C
text: and he was more thinking about some high level thinking tasks
speaker: C
text: and <vocalsound> I said " sure we need help
speaker: C
text: you can come in as a subject "
speaker: C
text: and he said " OK " .
speaker: C
text: So that 's what 's gonna happen , tomorrow ,
speaker: G
text: Using this new <disfmarker> new um plan ,
speaker: C
text: data .
speaker: C
text: New <disfmarker> new set up .
speaker: G
text: OK .
speaker: C
text: Yeah .
speaker: C
text: Which I 'll hopefully sort of scrape together t
speaker: C
text: But , thanks to Fey , we already have sort of a nice blueprint and I can work with that .
speaker: C
text: Questions ?
speaker: C
text: Comments on that ?
speaker: C
text: If not , we can move on .
speaker: C
text: No ?
speaker: C
text: No more questions ?
speaker: G
text: So what 's the s this is what you made , Fey ?
speaker: E
text: I 'm not sure I totally understand this
speaker: E
text: but <disfmarker>
speaker: C
text: Hmm ?
speaker: E
text: I 'm not sure I totally understand everything that 's being talked about
speaker: G
text: Like so <disfmarker> So it 's just based on like the materials you had about Heidelberg .
speaker: E
text: but I <disfmarker> I imagine I 'll c just catch on .
speaker: C
text: Um are you familiar with <disfmarker> with the <disfmarker> with the very rough setup of the data ?
speaker: D
text: Based on the web site ,
speaker: D
text: yeah , at the <disfmarker>
speaker: G
text: Oh OK
speaker: G
text: there 's a web site
speaker: G
text: and then you could like um figure out what the cate
speaker: C
text: experiment ?
speaker: D
text: Right .
speaker: E
text: Uh , this is where they 're supposed to <disfmarker>
speaker: D
text: It 's a tourist information web site ,
speaker: G
text: OK .
speaker: D
text: so .
speaker: G
text: OK .
speaker: C
text: Talk to a machine and it breaks down and then the human comes on .
speaker: E
text: Yeah .
speaker: E
text: Yeah .
speaker: C
text: The question is just sort of how do we get the tasks in their head that they have an intention of doing something and have a need to ask the system for something without giving them sort of a clear wording or phrasing of the task .
speaker: E
text: OK .
speaker: E
text: OK .
speaker: E
text: OK .
speaker: E
text: OK .
speaker: C
text: Because what will happen then is that people repeat <disfmarker> repeat , <comment> or as much as they can , of that phrasing .
speaker: G
text: Hmm .
speaker: G
text: Um , are you worried about being able to identify <disfmarker>
speaker: E
text: OK .
speaker: G
text: Um .
speaker: G
text: The <disfmarker> The goals that we 've d you guys have been talking about are this <disfmarker> these you know identifying which of three modes um their question uh concerns .
speaker: C
text: Mm - hmm .
speaker: G
text: So it 's like the Enter versus View <disfmarker>
speaker: C
text: Yeah , we <disfmarker> we <disfmarker> we will sort of get a protocol of the prior interaction ,
speaker: G
text: Uh - huh .
speaker: C
text: right ?
speaker: C
text: That 's where the instructor , the person we are going to hire , um and the subjects sit down together with these high level things
speaker: G
text: Uh - huh .
speaker: G
text: Mm - hmm .
speaker: C
text: and so
speaker: C
text: th the q first question for the subject is , " so these are things , you know , we thought a tourist can do .
speaker: C
text: Is there anything that interests you ? "
speaker: G
text: Mm - hmm .
speaker: C
text: And the person can say " yeah , sure sh
speaker: C
text: this is something I would do .
speaker: C
text: I would go shopping " .
speaker: C
text: Yeah ?
speaker: G
text: Mm - hmm .
speaker: C
text: and then we can sort of <disfmarker> this s instructor can say " well , uh then you <disfmarker> you may want to find out how to get over here
speaker: C
text: because this is where the shopping district is " .
speaker: G
text: So the interaction beforehand will give them hints about how specific or how whatever though the kinds of questions that are going to ask during the actual session ?
speaker: C
text: No .
speaker: C
text: Just sort of <disfmarker> OK , what <disfmarker> what <disfmarker> what would you like to buy
speaker: C
text: and then um OK there you wanna buy a whatever cuckoos clocks
speaker: G
text: Yeah .
speaker: C
text: OK and the there is a store there .
speaker: E
text: Mm - hmm .
speaker: C
text: So the task then for that person is t finding out how to get there ,
speaker: G
text: Mm - hmm .
speaker: C
text: right ?
speaker: C
text: That 's sort of what 's left .
speaker: G
text: Mm - hmm .
speaker: C
text: And we know that the intention is to enter because we know that the person wants to buy a cuckoos clock .
speaker: G
text: OK , that 's what I mean
speaker: G
text: so like those tasks are all gonna be um unambiguous about which of the three modes .
speaker: C
text: Hopefully .
speaker: G
text: Right . OK .
speaker: G
text: So .
speaker: A
text: Well , so the idea is to try to get the actual phrasing that they might use and try to interfere as little as possible with their choice of words .
speaker: C
text: Hopefully .
speaker: G
text: t <vocalsound> <vocalsound> <vocalsound> <vocalsound> <vocalsound> <vocalsound> <vocalsound> <vocalsound> <vocalsound> <vocalsound> <vocalsound> <vocalsound> That they 'll be here ?
speaker: C
text: Yes . In a sense that 's exactly the <disfmarker> the <disfmarker> the idea ,
speaker: A
text: uh uh
speaker: C
text: which is never possible in a <disfmarker> in a s in a lab situation ,
speaker: A
text: Well , u u the one experiment th that <disfmarker> that <disfmarker> that I 've read somewhere , it was <disfmarker> they u used pictures .
speaker: C
text: nuh ?
speaker: C
text: Yep .
speaker: E
text: Mm - hmm .
speaker: A
text: So to <disfmarker> to uh actually um uh specify the <disfmarker> the tasks .
speaker: A
text: Uh , but you know i i
speaker: C
text: Yeah .
speaker: C
text: We had exactly that on our list of possible way things
speaker: C
text: so we <disfmarker> uh I even made a sort of a silly thing how that could work , how you control you are here
speaker: C
text: you <disfmarker> you want to know how to get someplace ,
speaker: C
text: and this is the place
speaker: C
text: and it 's a museum
speaker: C
text: and you want to do some
speaker: C
text: and <disfmarker> and <disfmarker> and there 's a person looking at pictures .
speaker: C
text: So , you know , this is exactly getting someplace with the intention of entering and looking at pictures .
speaker: A
text: Right .
speaker: C
text: However , not only was <disfmarker> the common census were <disfmarker> among all participants of Friday 's meeting was it 's gonna be very laborious to <disfmarker> to make these drawings for each different things ,
speaker: C
text: all the different actions , if at all possible ,
speaker: A
text: Right .
speaker: C
text: and also people will get caught up in the pictures .
speaker: C
text: So all of a sudden we 'll get descriptions of pictures in there .
speaker: A
text: Right .
speaker: C
text: And people talking about pictures and pictorial representations
speaker: E
text: Hmm .
speaker: C
text: and <disfmarker> um
speaker: A
text: Right .
speaker: C
text: I would s I would still be willing to try it .
speaker: A
text: I mean , I I 'm <disfmarker> I 'm not saying it 's necessary
speaker: A
text: but <disfmarker> but uh i uh uh i <vocalsound> you might be able to combine you know text uh and <disfmarker> and some sort of picture
speaker: A
text: and also uh I think it <disfmarker> it will be a good idea to show them the text and kind of chew the task
speaker: A
text: and then take the test away <disfmarker> the <disfmarker> the <disfmarker> the <disfmarker> the <disfmarker> the text away
speaker: C
text: Mm - hmm .
speaker: C
text: Yeah .
speaker: A
text: so that they are not uh guided by <disfmarker> by by what you wrote ,
speaker: C
text: We will <disfmarker>
speaker: A
text: but can come up with their <disfmarker> with their own <disfmarker>
speaker: C
text: Yeah ,
speaker: C
text: they will have no more linguistic matter in front of them when they enter this room .
speaker: A
text: Right .
speaker: C
text: OK .
speaker: C
text: Then I suggest we move on to the <disfmarker> to
speaker: C
text: we have um uh the EDU Project ,
speaker: C
text: let me make one more general remark , has sort of two <disfmarker> two side uh um actions , its um action items that we 're do dealing with ,
speaker: C
text: one is modifying the SmartKom parser and the other one is modifying the SmartKom natural language generation module .
speaker: C
text: And um this is not too complicated
speaker: C
text: but I 'm just mentioning it <disfmarker>
speaker: C
text: put it in the framework
speaker: C
text: because this is something we will talk about now .
speaker: C
text: Um , I have some news from the generation ,
speaker: C
text: do you have news from the parser ?
speaker: F
text: Um , not <disfmarker>
speaker: C
text: By that look I <disfmarker>
speaker: F
text: Yes , uh , I would really p It would be better if I talked about it on Friday .
speaker: C
text: OK .
speaker: F
text: If that 's OK .
speaker: C
text: Yeah ,
speaker: C
text: wonderful .
speaker: C
text: Um , did you run into problems or did you run into not h having time ?
speaker: F
text: Yeah .
speaker: F
text: But not <disfmarker> not any time part .
speaker: C
text: OK , so that 's good .
speaker: C
text: That 's better than running into problems .
speaker: F
text: OK .
speaker: C
text: And um I <disfmarker> I do have some good news for the natural language generation however .
speaker: C
text: And the good news is I guess it 's done .
speaker: C
text: Uh , meaning that Tilman Becker , who does the German one , actually took out some time and already did it in English for us .
speaker: C
text: And so the version he 's sending us is already producing the English that 's needed to get by in version one point one .
speaker: F
text: So I take it that was similar to the <disfmarker> what <disfmarker> what we did for the parsing ?
speaker: C
text: Yeah .
speaker: C
text: I <disfmarker> I <disfmarker> it <disfmarker> even though the generator is a little bit more complex
speaker: C
text: and it would have been , not changing one hundred words but maybe four hundred words ,
speaker: F
text: OK .
speaker: C
text: but it would have been
speaker: F
text: OK .
speaker: C
text: but this <disfmarker> this is I guess good news ,
speaker: C
text: and the uh <disfmarker> the time
speaker: C
text: and especially Bhaskara
speaker: C
text: and uh <disfmarker> and um <disfmarker>
speaker: C
text: Oh do I have it here ?
speaker: C
text: No .
speaker: C
text: The time is now pretty much fixed .
speaker: C
text: It 's the last week of April until the fourth of May
speaker: C
text: so it 's twenty - sixth through fourth . That they 'll be here .
speaker: C
text: So it 's <disfmarker> it 's extremely important that the two of you are also present in this town during that time .
speaker: B
text: Wait , what <disfmarker> what are the days ?
speaker: B
text: April twenty - sixth to the <disfmarker> May fourth ?
speaker: C
text: Yeah , something like that .
speaker: B
text: I 'll probably be here .
speaker: F
text: Yeah .
speaker: C
text: It 's <disfmarker>
speaker: E
text: You will be here .
speaker: C
text: There is a d
speaker: C
text: Isn't finals coming up then pretty much after that ?
speaker: F
text: Finals was that .
speaker: G
text: Yeah w it doesn't really have much meaning to grad students
speaker: G
text: but final projects might .
speaker: C
text: OK .
speaker: F
text: Yeah actually , that 's true .
speaker: G
text: That <disfmarker>
speaker: C
text: Anyway , so this is <disfmarker>
speaker: B
text: Well I 'll be here working on something .
speaker: B
text: Guaranteed ,
speaker: B
text: it 's just uh will I be here , you know , in
speaker: B
text: uh <disfmarker>
speaker: B
text: I 'll be here too actually
speaker: B
text: but <disfmarker>
speaker: A
text: Hmm .
speaker: C
text: No it 's just um you know they 're coming for us so that we can bug them
speaker: G
text: Ye
speaker: C
text: and ask them more questions
speaker: C
text: and sit down together
speaker: C
text: and write sensible code
speaker: C
text: and they can give some nice talks and stuff .
speaker: C
text: But uh
speaker: C
text: just make a <disfmarker>
speaker: B
text: But it 's not like we need to be with them twenty - four hours a day s for the seven days that they 're here .
speaker: C
text: Not <disfmarker> not unless you really really want to .
speaker: E
text: They 're very dependent
speaker: C
text: Not unless you really want to .
speaker: C
text: And they 're both nice guys
speaker: C
text: so you may <disfmarker> may want to .
speaker: C
text: OK , that much from the parser and generator side ,
speaker: C
text: unless there are more questions on that .
speaker: G
text: So , no sample generator output yet ?
speaker: C
text: No .
speaker: G
text: OK .
speaker: C
text: It <disfmarker> Just a mail that , you know , he 's sending me the <disfmarker> the <disfmarker> the stuff soon
speaker: G
text: This is being sent ,
speaker: G
text: mm - hmm .
speaker: G
text: OK .
speaker: G
text: Mm - hmm .
speaker: C
text: and I was completely flabbergasted here
speaker: C
text: and I <disfmarker> and that 's also it 's <disfmarker> it 's going to produce the concept - to - speech uh blah - blah - blah information for <disfmarker> necessary for one point one in English <disfmarker>
speaker: C
text: based on the English ,
speaker: C
text: you know , in English .
speaker: C
text: So .
speaker: C
text: I was like " OK ,
speaker: E
text: We 're done .
speaker: C
text: we 're done ! "
speaker: G
text: So that was like one of the first l You know , the first task was getting it working for English .
speaker: G
text: So that 's basically over now .
speaker: G
text: Is that right ?
speaker: C
text: Yeah .
speaker: G
text: So the basic requirement fulfilled .
speaker: C
text: Um , the basic requirement is fulfilled almost .
speaker: C
text: When Andreas Stolcke and <disfmarker> and his gang ,
speaker: G
text: Mm - hmm .
speaker: C
text: when they have um changed the language model of the recognizer and the dictionary , then we can actually a put it all together
speaker: G
text: Mm - hmm .
speaker: G
text: So the speech recognizer also works .
speaker: G
text: Uh - huh .
speaker: G
text: Mm - hmm .
speaker: C
text: and
speaker: C
text: you can speak into it and ask for TV and movie information
speaker: E
text: Toll .
speaker: C
text: and then when
speaker: C
text: if <disfmarker> if something actually happens and some answers come out , then we 're done .
speaker: G
text: Mm - hmm .
speaker: G
text: If <disfmarker> and they 're kind of correct .
speaker: E
text: So it 's not done basically .
speaker: C
text: Hmm ?
speaker: G
text: And they kind of are <disfmarker> are correct .
speaker: E
text: Right .
speaker: G
text: It 's not just like anything .
speaker: E
text: Perhaps if the answers have something to do with the questions for example .
speaker: G
text: And they 're mostly in English .
speaker: G
text: So .
speaker: C
text: Then um <disfmarker>
speaker: G
text: Are they <disfmarker> is it using the database ?
speaker: G
text: the German TV movie .
speaker: C
text: Yeah .
speaker: G
text: OK .
speaker: G
text: So <vocalsound> all the actual data might be German names ?
speaker: C
text: Um well actually th um
speaker: G
text: Or are they all like American TV programs ?
speaker: C
text: um well <disfmarker>
speaker: E
text: I want to see " Die Dukes Von Hazard "
speaker: C
text: The <disfmarker>
speaker: C
text: OK , so you don't know how the German dialogue <disfmarker> uh the German <disfmarker> the demo dialogue actually works .
speaker: C
text: It works <disfmarker>
speaker: C
text: the first thing is what 's , you know , showing on TV ,
speaker: C
text: and then the person is presented with what 's running on TV
speaker: C
text: in Germany on that day , on that evening
speaker: G
text: Mm - hmm ,
speaker: G
text: mm - hmm .
speaker: C
text: and so you take one look at it and then you say " well that 's really nothing <disfmarker> there 's nothing for me there "
speaker: C
text: " what 's running in the cinemas ? "
speaker: G
text: Mm - hmm .
speaker: C
text: So maybe there 's something better happening there .
speaker: C
text: And then you get <disfmarker> you 're shown what movies play which films ,
speaker: C
text: and it 's gonna be of course all the Heidelberg movies and what films they are actually showing .
speaker: G
text: Mm - hmm .
speaker: C
text: And most of them are going to be Hollywood movies .
speaker: G
text: Hmm .
speaker: C
text: So , " American Beauty " is " American Beauty " ,
speaker: C
text: right ?
speaker: C
text: Yeah .
speaker: E
text: Mm - hmm .
speaker: G
text: Right .
speaker: C
text: And um .
speaker: G
text: But they 're shown like on a screen .
speaker: G
text: It 's a <disfmarker> I mean so would the generator ,
speaker: C
text: N
speaker: G
text: like the English language sentence of it is <disfmarker> " these are the follow you know the following films are being shown " or something like that ?
speaker: C
text: Yeah , but it in that sense it doesn't make <disfmarker> In that case uh it doesn't really make sense to read them out loud .
speaker: G
text: S
speaker: G
text: Right .
speaker: G
text: So it 'll just display <disfmarker>
speaker: C
text: if you 're displaying them .
speaker: G
text: OK .
speaker: G
text: So we don't have to worry about um <disfmarker>
speaker: C
text: But uh it 'll tell you that this is what 's showing in Heidelberg and there you go .
speaker: G
text: Yeah .
speaker: C
text: And the presentation agent will go " Hhh ! " <comment> Nuh ?
speaker: G
text: OK .
speaker: C
text: Like that <disfmarker> the avatar .
speaker: G
text: OK .
speaker: C
text: And um .
speaker: C
text: And then you pick <disfmarker> pick a movie and <disfmarker> and <disfmarker> and it show shows you the times
speaker: C
text: and you pick a time
speaker: C
text: and you pick seats and all of this .
speaker: C
text: So .
speaker: G
text: OK .
speaker: C
text: Pretty straightforward .
speaker: E
text: OK .
speaker: C
text: But it 's <disfmarker> so this time we <disfmarker> we are at an advantage
speaker: C
text: because it was a problem for the German system to incorporate all these English movie titles .
speaker: G
text: Yeah .
speaker: C
text: Nuh ?
speaker: G
text: Right .
speaker: C
text: But in English , that 's not really a problem ,
speaker: G
text: Mm - hmm .
speaker: C
text: unless we get some <disfmarker> some topical German movies that have just come out and that are in their database .
speaker: G
text: Right .
speaker: C
text: So the person may select " Huehner Rennen " or whatever .
speaker: E
text: " Chicken Run " .
speaker: C
text: OK .
speaker: C
text: Then uh on to the modeling .
speaker: C
text: Right ?
speaker: B
text: Yeah , yeah , I guess .
speaker: C
text: Um then modeling ,
speaker: C
text: there it is .
speaker: E
text: OK . What 's the next thing ?
speaker: B
text: Yep .
speaker: B
text: e
speaker: C
text: This is very rough but this is sort of what um Johno and I managed to come up with .
speaker: C
text: The idea here is that <disfmarker>
speaker: B
text: This is the uh s the schema of the XML here ,
speaker: B
text: not an example or something like that .
speaker: C
text: Yeah this is not an XML
speaker: E
text: OK .
speaker: C
text: this is sort of towards an <disfmarker> a schema ,
speaker: C
text: nuh ?
speaker: A
text: Right .
speaker: C
text: definition .
speaker: C
text: The idea is , so , imagine we have a library of schema
speaker: C
text: such as the Source - Path - Goal
speaker: C
text: and then we have forced uh motion ,
speaker: C
text: we have cost action ,
speaker: E
text: Mm - hmm .
speaker: G
text: Mm - hmm .
speaker: C
text: we have a whole library of schemas .
speaker: C
text: And they 're gonna be , you know , fleshed out in <disfmarker> in their real ugly detail ,
speaker: C
text: Source - Path - Goal ,
speaker: C
text: and there 's gonna be s a lot of stuff on the Goal and blah - blah - blah , that a goal can be and so forth .
speaker: C
text: What we think is <disfmarker>
speaker: C
text: And all the names could <disfmarker> should be taken " cum grano salis " .
speaker: C
text: So .
speaker: C
text: This is a <disfmarker>
speaker: C
text: the fact that we 're calling this " action schema " right now should not entail that we are going to continue calling this " action schema " .
speaker: C
text: But what that means <vocalsound> is we have here first of all
speaker: C
text: on the <disfmarker> in the <disfmarker> in the first iteration a stupid list of Source - Path - Goal actions
speaker: B
text: Actions that can be categorized with <disfmarker>
speaker: B
text: or that are related to Source - Path - Goal .
speaker: C
text: wi
speaker: E
text: OK .
speaker: C
text: to that schema
speaker: G
text: Mm - hmm .
speaker: C
text: and we will have you know forced motion and cost action actions .
speaker: B
text: And then those actions can be in multiple categories at the same time if necessary .
speaker: C
text: So a push may be in <disfmarker> in <disfmarker> in both you know push uh in this or this
speaker: G
text: Forced motion and caused action for instance ,
speaker: C
text: uh <disfmarker>
speaker: C
text: Exactly .
speaker: G
text: OK .
speaker: C
text: Yeah .
speaker: C
text: Also , these things may or may not get their own structure in the future .
speaker: C
text: So this is something that , you know , may also be a res As a result of your work
speaker: C
text: in the future , we may find out that , you know , there 're really s these subtle differences between
speaker: C
text: um
speaker: C
text: even within the domain of entering in the light of a Source - Path - Goal schema , that we need to put in <disfmarker> fill in additional structure up there .
speaker: C
text: But it gives us a nice handle .
speaker: C
text: So with this we can basically um you know s slaughter the cow any anyway we want .
speaker: C
text: Uh .
speaker: C
text: It <disfmarker> it is <disfmarker> It was sort of a <disfmarker> it gave us some headache ,
speaker: C
text: how do we avoid writing down that we have sort of the Enter Source - Path - Goal
speaker: C
text: that this <disfmarker> But this sort of gets the job done in that respect
speaker: C
text: and maybe it is even conceptually somewhat adequate in a sense that um we 're talking about two different things .
speaker: C
text: We 're talking more on the sort of intention level , up there ,
speaker: C
text: and more on the <disfmarker> this is the <disfmarker> your basic bone um schema , down there .
speaker: B
text: Uh one question , Robert .
speaker: B
text: When you point at the screen is it your shadow that I 'm supposed to look at ?
speaker: G
text: Yeah . It 's the shadow .
speaker: B
text: OK .
speaker: B
text: Whereas I keep looking where your hand is ,
speaker: B
text: and it doesn't <disfmarker>
speaker: C
text: Well , that wouldn't have helped you at all .
speaker: G
text: Right .
speaker: B
text: Yeah .
speaker: B
text: Basically , what this is <disfmarker> is that there 's an interface between what we are doing and the action planner
speaker: E
text: Spit right here .
speaker: B
text: and right now the way the interface is " action go " and then they have the <disfmarker> what the person claimed was the source and the person claimed as the goal passed on .
speaker: G
text: Mm - hmm .
speaker: B
text: And the problem is , is that the current system does not distinguish between goes of type " going into " , goes of type " want to go to a place where I can take a picture of " , et cetera .
speaker: C
text: So this is sort of what it looks like
speaker: C
text: now , some simple " Go " action from it <disfmarker> from an object named " Peter 's Kirche " of the type " Church " to an object named " Powder - Tower " of the type " Tower " .
speaker: G
text: This is the uh <disfmarker> what the action planner uses ?
speaker: C
text: Right ?
speaker: G
text: This is <disfmarker>
speaker: B
text: Right . Currently .
speaker: G
text: OK .
speaker: C
text: Currently .
speaker: G
text: And is that <disfmarker> and tha that 's changeable ?
speaker: G
text: or not ?
speaker: C
text: Yeah , well <disfmarker>
speaker: G
text: Like are we adapting to it ?
speaker: G
text: Or <disfmarker>
speaker: C
text: No .
speaker: C
text: We <disfmarker> This is the output , sort of , of the natural language understanding ,
speaker: G
text: Oh , yeah .
speaker: G
text: Uh - huh .
speaker: C
text: right ?
speaker: C
text: the input into the action planning , as it is now .
speaker: G
text: Mm - hmm .
speaker: G
text: Mm - hmm .
speaker: C
text: And what we are going to do ,
speaker: C
text: we going to <disfmarker>
speaker: C
text: and you can see here ,
speaker: C
text: and again for Johno please <disfmarker> please focus the shadow ,
speaker: B
text: OK .
speaker: C
text: um we 're gon
speaker: C
text: uh uh
speaker: C
text: here you have the action and the domain object
speaker: C
text: and w and on <disfmarker> on <disfmarker>
speaker: G
text: What did you think he was doing ?
speaker: G
text: OK , sorry .
speaker: B
text: I just <disfmarker>
speaker: E
text: A laser pointer would be most appropriate here I think .
speaker: D
text: Eee .
speaker: C
text: Yeah I <disfmarker> I um have <disfmarker> I have no <disfmarker>
speaker: B
text: Robert likes to be abstract
speaker: B
text: and that 's what I just thought he was doing .
speaker: G
text: You look up here .
speaker: G
text: OK .
speaker: C
text: Sort of between here and here ,
speaker: C
text: so as you can see this is on one level and we are going to add another um " Struct " , if you want , IE a rich action description on that level .
speaker: E
text: Mm - hmm .
speaker: C
text: So in the future <disfmarker>
speaker: G
text: So it 's just an additional information <disfmarker>
speaker: C
text: Exactly .
speaker: C
text: In the future though , the content of a hypothesis will not only be an object and an <disfmarker> an action and a domain object but an action , a domain object , and a rich action description ,
speaker: G
text: Right ?
speaker: G
text: that doesn't hurt the current way .
speaker: G
text: Mm - hmm .
speaker: G
text: Mm - hmm .
speaker: C
text: which is <disfmarker>
speaker: B
text: Which <disfmarker> which we 're abbreviating as " RAD " .
speaker: G
text: Good .
speaker: G
text: Hmm .
speaker: E
text: Rad !
speaker: F
text: So um you had like an action schema and a Source - Path - Goal schema ,
speaker: G
text: Hmm .
speaker: G
text: Hmm .
speaker: G
text: Mm - hmm .
speaker: F
text: right ?
speaker: F
text: So how does this Source - Path - Goal schema fit into the uh action schema ?
speaker: F
text: Like is it one of the tags there ?
speaker: G
text: Yeah can you go back to that one ?
speaker: B
text: So the Source - Path - Goal schema in this case ,
speaker: B
text: I 've <disfmarker> if I understand how we described <disfmarker> we set this up ,
speaker: B
text: um
speaker: B
text: cuz we 've been arguing about it all week ,
speaker: B
text: but uh we 'll hold the <disfmarker> the <disfmarker>
speaker: B
text: Well in this case it will hold the <disfmarker> <vocalsound> I mean the <disfmarker> the features I guess .
speaker: B
text: I 'm not <disfmarker> it 's hard for me to exactly s
speaker: B
text: So basically that will store the <disfmarker> the object that is w
speaker: B
text: the Source will store the object that we 're going from ,
speaker: E
text: Mm - hmm .
speaker: B
text: the Goal will store the <disfmarker> the f
speaker: G
text: So the fillers of the role source .
speaker: B
text: we 'll fill those in fill those roles in ,
speaker: G
text: OK .
speaker: B
text: right ?
speaker: C
text: Yeah .
speaker: B
text: The S Action - schemas basically have extra <disfmarker>
speaker: B
text: See we <disfmarker> so those are <disfmarker> schemas exist
speaker: B
text: because in case we need extra information
speaker: B
text: instead of just making it an attribute and which <disfmarker> which is just one thing we <disfmarker> we decided to make it 's own entity so that we could explode it out later on in case there is some structure that <disfmarker> that we need to exploit .
speaker: G
text: OK , so th
speaker: G
text: sorry I just don't kn
speaker: G
text: um um um <disfmarker>
speaker: G
text: This is just uh XML mo notational
speaker: G
text: but um the fact that it 's action schema and then sort of slash action schema
speaker: G
text: that 's a whole entit
speaker: B
text: That 's a block ,
speaker: G
text: That 's a block ,
speaker: B
text: yeah .
speaker: G
text: whereas source is just an attribute ?
speaker: G
text: Is that <disfmarker>
speaker: C
text: No , no , no .
speaker: C
text: Source is just not spelled out here .
speaker: G
text: Oh , OK , OK .
speaker: C
text: Source meaning <disfmarker> Source will be uh will have a name , a type , maybe a dimensionality ,
speaker: G
text: Uh - huh , uh - huh .
speaker: C
text: maybe canonical uh orientation <disfmarker>
speaker: G
text: OK could it <disfmarker> it could also be blocked out then as <disfmarker>
speaker: B
text: Yeah ,
speaker: B
text: the <disfmarker> So <disfmarker>
speaker: G
text: OK .
speaker: B
text: Yeah .
speaker: C
text: s Source it will be ,
speaker: C
text: you know we 'll f
speaker: C
text: we know a lot about sources
speaker: C
text: so we 'll put all of that in Source .
speaker: G
text: OK .
speaker: C
text: But it 's independent whether we are using the SPG schema in an Enter , View , or Approach mode ,
speaker: G
text: Mm - hmm .
speaker: C
text: right ?
speaker: C
text: This is just properties of the SPG <comment> schema .
speaker: C
text: We can talk about Paths being the fastest , the quickest , the nicest and so forth ,
speaker: C
text: uh or <disfmarker> or <disfmarker> and the Trajector should be coming in there as well .
speaker: G
text: OK .
speaker: C
text: And then G the same about Goals .
speaker: G
text: OK .
speaker: G
text: So I guess the question is when you actually fill one of these out , it 'll be under action schema ?
speaker: G
text: Those are <disfmarker>
speaker: G
text: It 's gonna be one <disfmarker> y you 'll pick one of those for <disfmarker>
speaker: B
text: Right .
speaker: G
text: OK these are <disfmarker> this is just a layout of the possible that could go <disfmarker> play that role .
speaker: B
text: Right , so the <disfmarker> the <disfmarker> the roles will be filled in with the schema
speaker: C
text: Hmm ?
speaker: G
text: OK , go it .
speaker: G
text: Uh - huh .
speaker: B
text: and then what actual a action is chosen is <disfmarker> will be in the <disfmarker> in the action schema section .
speaker: G
text: OK .
speaker: G
text: OK .
speaker: G
text: S S
speaker: G
text: OK , so one question .
speaker: G
text: This was <disfmarker> in this case it 's all um clear , sort of obvious ,
speaker: G
text: but you can think of the Enter , View and Approach as each having their roles ,
speaker: G
text: right ?
speaker: G
text: the <disfmarker> I mean it 's <disfmarker> it 's implicit that the person that 's moving is doing entering viewing and approaching ,
speaker: G
text: but you know the usual thing is we have bindings between sort of <disfmarker>
speaker: G
text: they 're sort of like action specific roles and the more general Source - Path - Goal specific roles .
speaker: G
text: So are we worrying about that or not for now ?
speaker: C
text: Yes , yes .
speaker: G
text: OK .
speaker: C
text: Since you bring it up now , we will worry about it .
speaker: G
text: OK .
speaker: C
text: Tell us more about it .
speaker: C
text: What do you <disfmarker> what do you <disfmarker>
speaker: G
text: What 's that ?
speaker: G
text: Oh I guess it <disfmarker>
speaker: G
text: I <disfmarker> I may be just um reading this and interpreting it into my head in the way that I 've always viewed things
speaker: C
text: Hmm .
speaker: E
text: Hmm .
speaker: G
text: and <vocalsound> that <disfmarker> that may or may not be what you guys intended .
speaker: G
text: But if it is , then the top block is sort of like
speaker: G
text: um , you know , you have to list exactly what X - schema
speaker: G
text: or in this action schema ,
speaker: G
text: there 'll be a certain one , that has its own s structure
speaker: G
text: and maybe it has stuff about that specific to entering or viewing or approaching ,
speaker: G
text: but those could include roles like the thing that you 're viewing , the thing that you 're entering , the thing that you 're
speaker: G
text: whatever ,
speaker: G
text: you know , that <disfmarker> which are <disfmarker>
speaker: E
text: So very specific role names are " viewed thing " , " entered thing " <disfmarker>
speaker: G
text: think <disfmarker> think of enter , view and approach as frames
speaker: G
text: and they have frame - specific parameters and <disfmarker> and roles
speaker: E
text: Yeah .
speaker: C
text: Mm - hmm .
speaker: C
text: Yeah .
speaker: G
text: and you can also describe them in a general way as Source - Path - Goal schema
speaker: G
text: and maybe there 's other image schemas that you could you know add after this that you know , how do they work in terms of you know a force dynamics
speaker: C
text: Mm - hmm .
speaker: G
text: or how do they work in f terms of other things .
speaker: C
text: Mm - hmm , Mm - hmm , Mm - hmm .
speaker: G
text: So all of those have um basically f either specific <disfmarker> frame specific roles or more general frame specific roles that might have binding .
speaker: G
text: So the question is are um <disfmarker> how to represent when things are linked in a certain way .
speaker: G
text: So we know for Enter that there 's Container potentially involved
speaker: C
text: Mm - hmm .
speaker: G
text: and it 's not <disfmarker>
speaker: G
text: uh I don't know if you wanna have in the same level as the action schema SPG schema
speaker: G
text: it <disfmarker> it 's somewhere in there that you need to represent that there is some container
speaker: G
text: and the interior of it corresponds to some part of the Source - Path - Goal um you know goal <disfmarker> uh goal I guess in this case .
speaker: C
text: Mm - hmm .
speaker: G
text: So uh is there an easy way in this notation to show when there 's identity basically between things
speaker: C
text: Yeah .
speaker: G
text: and I di don't know if that 's something we need to invent
speaker: G
text: or you know just <disfmarker>
speaker: B
text: The <disfmarker>
speaker: B
text: wa wasn't there supposed to be a link in the
speaker: F
text: Right .
speaker: B
text: I don't know if this answers your question ,
speaker: B
text: I was just staring at this while you were talking ,
speaker: B
text: sorry .
speaker: G
text: It 's OK .
speaker: B
text: Uh a link between the action schema , a field in the s in the schema for the image schemas that would link us to which action schema we were supposed to use
speaker: B
text: so we could <disfmarker>
speaker: C
text: Yeah .
speaker: C
text: Um , well that 's <disfmarker> that 's one <disfmarker> one thing is that we can link up ,
speaker: C
text: think also that um we can have one or m as many as we want links from <disfmarker> from the schema up to the s action um description of it .
speaker: G
text: Hmm .
speaker: C
text: But the notion I got from Nancy 's idea was that we may f find sort of concepts floating around i in the a action description of the action f " Enter " frame up there that are , e when you talk about the real world , actually identical to the goal of the <disfmarker> the S Source - Path - Goal schema ,
speaker: G
text: Exactly .
speaker: G
text: Right , right .
speaker: C
text: and do we have means of <disfmarker> of telling it within that
speaker: G
text: Right .
speaker: C
text: a and the answer is absolutely .
speaker: G
text: Yeah .
speaker: C
text: The way <disfmarker> we absolutely have those means that are even part of the M - three - L A API ,
speaker: G
text: Oh great .
speaker: G
text: s Uh - huh .
speaker: C
text: meaning we can reference .
speaker: C
text: So meaning <disfmarker>
speaker: G
text: Great .
speaker: G
text: That 's exactly what is necessary .
speaker: B
text: Yeah .
speaker: C
text: And um .
speaker: B
text: St
speaker: C
text: This referencing thing however is of temporary nature
speaker: C
text: because sooner or later the W - three - C will be finished with their X - path , uh , um , specification
speaker: C
text: and then it 's going to be even much nicer .
speaker: C
text: Then we have real means of pointing at an individual instantiation of one of our elements here
speaker: G
text: Mm - hmm .
speaker: G
text: Mm - hmm .
speaker: C
text: and link it to another one , and this not only within a document but also via documents ,
speaker: E
text: Mm - hmm .
speaker: G
text: OK .
speaker: C
text: and <disfmarker> and all in a v very easy e homogenous framework .
speaker: G
text: So you know <disfmarker> happen to know how <disfmarker> what <disfmarker> what " sooner or later " means like in practice ?
speaker: C
text: That 's
speaker: G
text: Or estimated .
speaker: C
text: but it 's soon .
speaker: G
text: OK , OK .
speaker: C
text: So it 's g it 's <disfmarker> the spec is there
speaker: C
text: and it 's gonna part of the M - three - L AP <disfmarker> API filed by the end of this year
speaker: C
text: so that this means we can start using it basically now .
speaker: G
text: Mm - hmm .
speaker: C
text: But this is a technical detail .
speaker: G
text: So a pointer <disfmarker> a way to really say pointers .
speaker: B
text: Basically references from the roles in the schema <disfmarker> the bottom schemas to the action schemas is wha uh I 'm assuming .
speaker: G
text: Yeah .
speaker: G
text: OK , yeah .
speaker: C
text: Yeah .
speaker: C
text: Yeah ,
speaker: G
text: OK .
speaker: C
text: I mean personally , I 'm looking even more forward to the day when we 're going to have X forms , which l is a form of notation where it allows you to say that if the SPG action up there is Enter , then the goal type can never be a statue .
speaker: G
text: Uh - huh .
speaker: G
text: Right .
speaker: E
text: Mm - hmm .
speaker: G
text: So you have constraints that are dependent on the c actual s specific filler , uh , of some attribute .
speaker: C
text: Mm - hmm , yeah .
speaker: C
text: W
speaker: C
text: Yeah e exactly .
speaker: C
text: Um , you know this , of course , does not make sense in light of the Statue of Liberty ,
speaker: G
text: Uh - huh .
speaker: E
text: Right .
speaker: C
text: however <vocalsound> it is uh you know sort of <disfmarker> these sort of things are imaginable .
speaker: G
text: Tsk .
speaker: G
text: Yeah .
speaker: G
text: Or the Gateway Arch in St .
speaker: C
text: Yeah ?
speaker: F
text: S So um , like are you gonna have similar schemas for FM
speaker: G
text: Louis .
speaker: C
text: Yeah .
speaker: G
text: So .
speaker: F
text: like forced motion and caused action and stuff
speaker: F
text: like you have for SPG ?
speaker: C
text: Yeah .
speaker: F
text: And if so like can <disfmarker> are you able to enforce that you know if <disfmarker> if it 's <disfmarker> if it 's SPG action then you have that schema ,
speaker: F
text: if it 's a forced motion then you have the other schema present in the <disfmarker>
speaker: C
text: Um we have absolute <disfmarker>
speaker: C
text: No .
speaker: C
text: We have absolutely no means of enforcing that ,
speaker: C
text: so it would be considered valid if we have an SPG action " Enter " and no SPG schema , but a forced action schema .
speaker: C
text: Could happen .
speaker: G
text: Whi - which is not bad ,
speaker: G
text: because I mean , that there 's multiple sens
speaker: G
text: I mean that particular case , there 's mult there <disfmarker> there 's a forced side of <disfmarker> of that verb as well .
speaker: C
text: Hmm .
speaker: C
text: It <disfmarker> maybe it means we had nothing to say about the Source - Path - Goal .
speaker: F
text: OK .
speaker: C
text: What 's also nice , and for a i for me in my mind
speaker: C
text: it 's <disfmarker> it 's crucially necessary , is that we can have multiple schemas and multiple action schemas in parallel .
speaker: F
text: Right .
speaker: C
text: And um we started thinking about going through our bakery questions ,
speaker: C
text: so when I say " is there a bakery here ? "
speaker: C
text: you know I do ultimately want our module to be able to first of all f tell the rest of the system " hey this person actually wants to go there "
speaker: C
text: and " B " , <comment> that person actually wants to buy something to eat there .
speaker: C
text: Nuh ?
speaker: C
text: And if these are two different schemas ,
speaker: C
text: IE the Source - Path - Goal schema of getting there and then the buying snacks schema ,
speaker: C
text: nuh ? <disfmarker>
speaker: G
text: Would they both be listed here in <disfmarker>
speaker: C
text: Yes .
speaker: G
text: OK .
speaker: G
text: Under so o under action schema there 's a list that can include both <disfmarker> both things .
speaker: C
text: ye Yeah , they they would <disfmarker> both schemas would appear ,
speaker: B
text: Right .
speaker: C
text: so what is the
speaker: E
text: Snack action .
speaker: C
text: uh is <disfmarker> is there a " buying s snacks " schema ?
speaker: G
text: That 's interesting .
speaker: C
text: What is the uh <disfmarker> <vocalsound> have
speaker: G
text: What ?
speaker: C
text: the buying snack schema ?
speaker: E
text: See .
speaker: D
text: Buying <disfmarker> <vocalsound> buying his food <disfmarker>
speaker: E
text: I 'm sure there 's a commercial event schema in there somewhere .
speaker: G
text: Oop .
speaker: G
text: I <vocalsound> d f
speaker: C
text: Yeah ,
speaker: C
text: a " commercial event " or something .
speaker: G
text: Yeah I <disfmarker> I <disfmarker>
speaker: C
text: Yeah ?
speaker: C
text: So uh <disfmarker> <vocalsound> so we would <disfmarker> we would instantiate the SPG schema with a Source - Path - Goal blah - blah - blah
speaker: G
text: I see .
speaker: C
text: and the buying event you know at which <disfmarker> however that looks like , the place f thing to buy .
speaker: G
text: Uh - huh .
speaker: G
text: Uh - huh .
speaker: G
text: Interesting .
speaker: G
text: Would you say that the <disfmarker> like <disfmarker>
speaker: G
text: I mean you could have a flat structure and just say these are two independent things ,
speaker: G
text: but there 's also this sort of like causal ,
speaker: G
text: well , so one is really facilitating the other and it 's part of a compound action of some kind , which has structure .
speaker: C
text: Yeah .
speaker: C
text: Now it 's technically possible that you can fit schema within schema ,
speaker: G
text: uh I <disfmarker> I think that 's nicer for a lot of reasons
speaker: C
text: and schema within schemata <disfmarker>
speaker: G
text: but might be a pain
speaker: G
text: so uh <disfmarker>
speaker: C
text: um
speaker: C
text: Well , for me it seems that uh <disfmarker>
speaker: G
text: I mean there are truly times when you have two totally independent goals that they might express at once ,
speaker: C
text: r Yes .
speaker: G
text: but in this case it 's really like there 's a purpo means that you know f for achieving some other purpose .
speaker: C
text: Well , if I 'm <disfmarker> if I 'm recipient of such a message
speaker: C
text: and I get a Source - Path - Goal where the goal is a bakery
speaker: C
text: and then I get a commercial action which takes place in a bakery ,
speaker: C
text: right ?
speaker: G
text: Uh - huh .
speaker: C
text: and <disfmarker> and <disfmarker> and they <disfmarker> they are obviously , via identifiers , identified to be the same thing here .
speaker: G
text: Yeah .
speaker: G
text: See that <disfmarker> that bothers me that they 're the same thing .
speaker: C
text: No , no , just the <disfmarker>
speaker: C
text: Yeah ?
speaker: G
text: Yeah
speaker: G
text: because they 're two different things
speaker: G
text: one of which is l
speaker: G
text: you could think of one a sub you know pru whatever pre - condition for the second .
speaker: C
text: Yeah , yeah !
speaker: G
text: Right .
speaker: G
text: Yeah , yeah .
speaker: G
text: So . So . OK .
speaker: G
text: So there 's like levels of granularity .
speaker: G
text: So uh there 's <disfmarker> there 's um a single event of which they are both a part .
speaker: G
text: And they 're <disfmarker> independently they <disfmarker> they are events which have very different characters as far as Source - Path - Goal whatever .
speaker: C
text: Mm - hmm , yeah .
speaker: G
text: So when you identify Source - Path - Goal and whatever , there 's gonna to be a desire , whatever , eating , hunger ,
speaker: G
text: whatever other frames you have involved , they have to match up in <disfmarker> in nice ways .
speaker: G
text: So it seems like each of them has its own internal structure and mapping to these schemas
speaker: C
text: Mm - hmm .
speaker: G
text: you know from the other <disfmarker>
speaker: G
text: But you know that 's just <disfmarker> That 's just me .
speaker: G
text: Like <disfmarker> <vocalsound> I <disfmarker> I <disfmarker>
speaker: C
text: Well , I think we 're gonna hit a lot of interesting problems
speaker: C
text: and as I prefaced it this is the result of one week of arguing <vocalsound> about it
speaker: G
text: Mm - hmm .
speaker: G
text: Between you guys
speaker: G
text: uh
speaker: B
text: Yeah .
speaker: G
text: OK .
speaker: C
text: and um <disfmarker> and so <disfmarker>
speaker: E
text: Yeah I mean I <disfmarker> I still am not entirely sure that I really fully grasp the syntax of this .
speaker: E
text: You know , like what <disfmarker>
speaker: B
text: Well it 's not <disfmarker> it 's not actually a very <disfmarker> actually , it doesn't actually <disfmarker>
speaker: C
text: Um it occur <disfmarker> it occurs to me that I mean ne
speaker: E
text: Right .
speaker: E
text: Or the intended interpretation of this .
speaker: E
text: Yeah .
speaker: C
text: um well I should have <disfmarker> we should have added an ano an XML example ,
speaker: C
text: or some XML examples
speaker: E
text: Yeah .
speaker: G
text: yeah that would be <disfmarker> that would be nice .
speaker: C
text: and <disfmarker> and this is on <disfmarker> on a <disfmarker> on <disfmarker> on my list of things until next <disfmarker> next week .
speaker: E
text: OK .
speaker: C
text: It 's also a question of the recursiveness and <disfmarker> and a hier hierarchy um in there .
speaker: G
text: Yeah .
speaker: G
text: Yeah .
speaker: C
text: Do we want the schemas just blump blump blump blump ?
speaker: C
text: I mean it 's <disfmarker> if we can actually you know get it so that we can , out of one utterance , activate more than one schema , I mean , then we 're already pretty good ,
speaker: G
text: Mm - hmm .
speaker: C
text: right ?
speaker: A
text: Well <disfmarker> well you have to be careful with that uh uh thing
speaker: A
text: because uh <vocalsound> I mean many actions presuppose some <disfmarker> um almost <vocalsound> infinitely many other actions .
speaker: A
text: So if you go to a bakery <pause> you have a general intention of uh not being hungry .
speaker: G
text: Yeah .
speaker: G
text: Mayb - yeah .
speaker: A
text: You have a specific intentions to cross the traffic light to get there .
speaker: G
text: Mm - hmm .
speaker: E
text: Yeah .
speaker: A
text: You have a further specific intentions to left <disfmarker> to lift your right foot
speaker: C
text: Hmm ?
speaker: A
text: and so uh uh I mean y you really have to focus on on <disfmarker> on
speaker: G
text: Right .
speaker: A
text: and decide the level of <disfmarker> of abstraction that <disfmarker> that you aim at it kind of zero in on that ,
speaker: G
text: Right .
speaker: C
text: Yeah .
speaker: A
text: and more or less ignore the rest , unless there is some implications that <disfmarker> that you want to constant draw from <disfmarker> from sub - tasks um that are relevant
speaker: G
text: M Th
speaker: A
text: uh I mean but very difficult .
speaker: G
text: The other thing that I just thought of is that you could want to go to the bakery because you 're supposed to meet your friend there or som
speaker: A
text: Yeah .
speaker: C
text: Mm - hmm .
speaker: G
text: you know so you <disfmarker> like being able to infer the second thing is very useful and probably often right .
speaker: B
text: Well the <disfmarker> the <disfmarker> the utterance was " is there a bakery around here ? " ,
speaker: G
text: But having them separate <disfmarker>
speaker: B
text: not " I want to go to a bakery . "
speaker: G
text: Well maybe their friend said they were going to meet them in a bakery around the area .
speaker: A
text: Right .
speaker: G
text: And I 'm , yeah <disfmarker> I 'm <disfmarker> I 'm inventing contexts which are maybe unlikely ,
speaker: A
text: Right .
speaker: B
text: Sure it <disfmarker>
speaker: B
text: OK .
speaker: G
text: but yeah I mean like <disfmarker>
speaker: B
text: Yeah .
speaker: G
text: but it 's still the case that um you could <disfmarker> you could override that default by giving extra information
speaker: C
text: Mm - hmm , yeah .
speaker: G
text: which is to me a reason why you would keep the inference of that separate from the knowledge of " OK they really want to know if there 's a bakery around here " ,
speaker: C
text: Yeah .
speaker: G
text: which is direct .
speaker: C
text: Well there <disfmarker> there <disfmarker> there should never be a hard coded uh <vocalsound> shortcut from <pause> the bakery question to the uh double schema thing ,
speaker: G
text: Right .
speaker: C
text: how uh <disfmarker>
speaker: C
text: And , as a matter of fact , when I have traveled with my friends we make these <disfmarker> exactly these kinds of appointments .
speaker: G
text: Mm - hmm .
speaker: G
text: Yeah .
speaker: E
text: Mm - hmm .
speaker: G
text: Exactly .
speaker: C
text: We o o
speaker: G
text: It 's <disfmarker> I met someone at the bakery you know in the Victoria Station t you know <vocalsound> train station London before ,
speaker: E
text: Mm - hmm .
speaker: A
text: Right .
speaker: E
text: Yep .
speaker: A
text: Well .
speaker: G
text: yeah .
speaker: G
text: It 's like <disfmarker>
speaker: A
text: I have a question about the slot of the SPG action .
speaker: A
text: So <vocalsound> the Enter - View - Approach the <disfmarker> the <disfmarker> the EVA um , those are fixed slots in this particular action .
speaker: A
text: Every action of this kind will have a choice .
speaker: A
text: Or <disfmarker> or <disfmarker> or <disfmarker> or will it just
speaker: A
text: um uh <disfmarker>
speaker: E
text: Every SPG <disfmarker> every SPG action either is an Enter or a View or an Approach ,
speaker: A
text: is it change <disfmarker>
speaker: A
text: Right , right .
speaker: C
text: Mm - hmm .
speaker: E
text: right ?
speaker: E
text: OK .
speaker: A
text: So <disfmarker> so I <disfmarker> I mean for <disfmarker> for each particular action that you may want to characterize you would have some number of slots that define uh uh uh you know in some way what this action is all about .
speaker: A
text: It can be either A , B or C .
speaker: A
text: Um . So is it a fixed number or <disfmarker> or do you leave it open <disfmarker> it could be between one and fifteen
speaker: A
text: uh <disfmarker>
speaker: A
text: it 's <disfmarker> it 's <disfmarker> it 's flexible .
speaker: C
text: Um , the uh <disfmarker>
speaker: C
text: Well , it sort of depends on <disfmarker> on if you actually write down the <disfmarker> the schema
speaker: C
text: then you have to say it 's either one of them
speaker: C
text: or it can be none ,
speaker: C
text: or it can be any of them .
speaker: C
text: However the uh <disfmarker> it seems to be sensible to me to r to view them as mutually exclusive
speaker: C
text: um
speaker: C
text: maybe even not .
speaker: G
text: J Do you mean within the Source - Path - Goal actions ?
speaker: A
text: uh <vocalsound> ye uh uh b I uh I <disfmarker> u I understand
speaker: C
text: Yeah .
speaker: G
text: Those three ?
speaker: A
text: uh
speaker: A
text: but <disfmarker>
speaker: C
text: And um how <disfmarker> how where is the end ?
speaker: C
text: So that 's <disfmarker>
speaker: A
text: No , no .
speaker: A
text: There <disfmarker> a a actually by I think my question is simpler than that ,
speaker: A
text: um <vocalsound> is <disfmarker>
speaker: A
text: OK , so you have an SPG action
speaker: A
text: and <disfmarker> and it has three different um uh aspects
speaker: A
text: um
speaker: A
text: because you can either enter a building or view it or <disfmarker> or approach it and touch it or something .
speaker: A
text: Um now you define uh another action ,
speaker: C
text: Forced action or forced motion .
speaker: A
text: it 's <disfmarker> it 's called um uh s S P G - one
speaker: C
text: Yeah .
speaker: A
text: action
speaker: A
text: a different action . Um and this <disfmarker> uh action - two would have various variable possibilities of interpreting what you would like to do . And <disfmarker> i in <disfmarker> in a way similar to either Enter - View - Approach you may want to send a letter , read a letter , or dictate a letter , let 's say .
speaker: B
text: Oh the <disfmarker> OK
speaker: A
text: So , h
speaker: B
text: uh maybe I 'd <disfmarker>
speaker: B
text: The uh <disfmarker>
speaker: B
text: These actions <disfmarker>
speaker: B
text: I don't know if I 'm gonna answer your question or not with this ,
speaker: B
text: but the categories inside of action schemas ,
speaker: B
text: so , SPG action is a category .
speaker: B
text: Real
speaker: B
text: although I think what we 're specifying here is this is a category where the actions " enter , view and approach " would fall into
speaker: B
text: because they have a related Source - Path - Goal schema in our tourist domain .
speaker: B
text: Cuz viewing in a tourist domain is going up to it and <disfmarker> or actually going from one place to another to take a picture , in this <disfmarker> in a <disfmarker>
speaker: A
text: Right .
speaker: A
text: Oh , s so it 's sort of automatic derived fr from the structure that <disfmarker> that is built elsewhere .
speaker: B
text: derived
speaker: B
text: I don't know if I u
speaker: E
text: This is a cate this a category structure here ,
speaker: E
text: right ?
speaker: E
text: Action schema .
speaker: B
text: Right .
speaker: E
text: What are some types of action schemas ?
speaker: E
text: Well one of the types of action schemas is Source - Path - Goal action .
speaker: E
text: And what are some types of that ?
speaker: E
text: And an Enter , a View , an Approach .
speaker: B
text: Right .
speaker: C
text: Hmm .
speaker: E
text: Those are all Source - Path - Goal actions .
speaker: B
text: Inside of Enter there will be roles that can be filled basically .
speaker: B
text: So if I want to go from outside to inside <vocalsound> then you 'd have the roles that need to filled , where you 'd have a Source - Path - Goal set of roles .
speaker: B
text: So you 'd the Source would be outside and Path is to the door or whatever ,
speaker: B
text: right ?
speaker: A
text: Right .
speaker: B
text: So if you wanted to have a new type of action you 'd create a new type of category .
speaker: B
text: Then this category would <disfmarker> we would put it <disfmarker>
speaker: B
text: or not necessarily <disfmarker>
speaker: B
text: We would put a new action in the m uh in the categories that <disfmarker> in which it has the
speaker: B
text: um <disfmarker>
speaker: B
text: Well , every action has a set of related schemas
speaker: B
text: like Source - Path - Goal or force , whatever ,
speaker: E
text: Mm - hmm .
speaker: B
text: right ?
speaker: A
text: Right .
speaker: B
text: So we would put " write a letter " in the categories uh that <disfmarker> in which it had <disfmarker> it w had uh schemas u
speaker: E
text: There could be a communication event action or something like that
speaker: C
text: Mm - hmm .
speaker: B
text: Exactly .
speaker: E
text: and you could write it .
speaker: B
text: Schemas uh that of that type .
speaker: B
text: And then later , you know , there <disfmarker> the <disfmarker> we have a communication event action where we 'd define it down there as <disfmarker>
speaker: G
text: Hmm .
speaker: G
text: So there 's a bit a redundancy ,
speaker: G
text: right ?
speaker: G
text: in <disfmarker> in which the things that go into a particular <disfmarker> You have categories at the top under action schema
speaker: G
text: and the things that go under a particular category are um supposed to have a corresponding schema definition for that type .
speaker: G
text: So I guess what 's the function of having it up there too ?
speaker: G
text: I mean I guess I 'm wondering whether <disfmarker> You could just have
speaker: G
text: under action schema you could just sort of say whatever you know it 's gonna be Enter , View or Approach or whatever number of things
speaker: C
text: Mm - hmm .
speaker: G
text: and pos partly because you need to know somewhere that those things fall into some categories .
speaker: G
text: And it may be multiple categories as you say which is um the reason why it gets a little messy
speaker: C
text: Yeah .
speaker: G
text: um but if it has <disfmarker> if it 's supposed to be categorized in category X then the corresponding schema X will be among the structures that <disfmarker> that follow .
speaker: B
text: Right .
speaker: C
text: Yeah .
speaker: B
text: Well , this is one of things we were arguing about .
speaker: G
text: That 's like <disfmarker>
speaker: C
text: th this is <disfmarker> this r
speaker: G
text: OK ,
speaker: G
text: sorry .
speaker: C
text: this is <disfmarker> this is more <disfmarker> this is probably the way that th that 's the way that seemed more intuitive to Johno I guess
speaker: G
text: You didn't tell me to <disfmarker>
speaker: C
text: also for a while <disfmarker> for
speaker: G
text: Uh - huh .
speaker: G
text: But now you guys have seen the light .
speaker: C
text: No , no , no . Uh we have not <disfmarker> we have not seen the light .
speaker: G
text: So .
speaker: B
text: No .
speaker: G
text: I it 's easy to go back and forth
speaker: B
text: The <disfmarker> the reason <disfmarker> One reason we 're doing it this way is in case there 's extra structure that 's in the Enter action that 's not captured by the schemas ,
speaker: G
text: isn't it ?
speaker: G
text: Uh - huh .
speaker: G
text: I agree .
speaker: G
text: Right .
speaker: G
text: Right .
speaker: B
text: right ?
speaker: G
text: Which is why I would think you would say Enter
speaker: G
text: and then just say all the things that are relevant specifically to Enter .
speaker: G
text: And then the things that are abstract will be in the abstract things as well .
speaker: G
text: And that 's why the bindings become useful .
speaker: B
text: Right , but <disfmarker>
speaker: E
text: Ri - You 'd like <disfmarker> so you 're saying you could practically turn this structure inside out ?
speaker: E
text: or something ,
speaker: E
text: or <disfmarker> ?
speaker: G
text: Um Ye - I see what you mean by that ,
speaker: C
text: No basically w
speaker: G
text: but I <disfmarker> I don't if I would <disfmarker> I would need to have t have that .
speaker: C
text: Get <disfmarker> get rid of the sort of SPG slash something
speaker: G
text: Right .
speaker: C
text: uh or the sub - actions category ,
speaker: C
text: because what does that tell us ?
speaker: G
text: Uh - huh .
speaker: G
text: Yeah .
speaker: C
text: Um and I agree that you know this is something we need to discuss ,
speaker: G
text: I in fact what you could say is for Enter ,
speaker: C
text: yeah .
speaker: G
text: you could say " here , list all the kinds of schemas that <disfmarker> on the category that <disfmarker>
speaker: E
text: List all the parent categories .
speaker: G
text: you know i
speaker: G
text: list all the parent categories " .
speaker: G
text: It 's just like a frame hierarchy ,
speaker: G
text: right ?
speaker: E
text: Yeah .
speaker: G
text: like you have these blended frames .
speaker: C
text: Mm - hmm .
speaker: G
text: So you would say enter and you 'd say my parent frames are such - and - such ,
speaker: G
text: h and then those are the ones that actually you then actually define and say how the roles bind to your specific roles
speaker: G
text: which will probably be f richer and fuller and have other stuff in there .
speaker: E
text: Yeah .
speaker: E
text: This sounds like a paper I 've read around here recently in terms of <disfmarker>
speaker: G
text: Yeah it could <vocalsound> be not a coincidence .
speaker: G
text: Like I said , I 'm sure I 'm just hitting everything with a hammer that I developed ,
speaker: E
text: Yeah .
speaker: G
text: but I mean you know uh it 's <disfmarker>
speaker: G
text: I 'm just telling you what I think ,
speaker: G
text: you just hit the button and it 's like <disfmarker>
speaker: C
text: And , I guess fr uh
speaker: E
text: Yeah I mean but there 's a good question here .
speaker: E
text: Like , I mean uh do you <disfmarker> When do you need <disfmarker>
speaker: E
text: Damn this headset !
speaker: E
text: When you this uh ,
speaker: G
text: Metacomment .
speaker: E
text: eh <disfmarker>
speaker: E
text: Yeah . <comment> That 's all recorded .
speaker: E
text: Um .
speaker: G
text: " Damn this project . "
speaker: E
text: Why do you <disfmarker>
speaker: G
text: No just kidding .
speaker: E
text: I don't know . Like <disfmarker>
speaker: E
text: How do I <disfmarker> how do I come at this question ?
speaker: E
text: Um .
speaker: E
text: I just don't see why you would <disfmarker>
speaker: E
text: I mean does th
speaker: E
text: Who uses this uh <disfmarker> this data structure ?
speaker: E
text: You know ? Like , do you say " alright I 'm going to uh <disfmarker> <pause> do an SPG action " .
speaker: E
text: And then you know somebody ne either the computer or the user says " alright , well , I know I want to do a Source - Path - Goal action so what are my choices among that ? "
speaker: E
text: And " oh , OK , so I can do an Enter - View - Approach " .
speaker: E
text: It 's not like that ,
speaker: E
text: right ?
speaker: E
text: It 's more like you say " I want to , uh <disfmarker> <pause> I want to do an Enter . "
speaker: B
text: Well only one of <disfmarker>
speaker: E
text: And then you 're more interested in knowing what the parent categories are of that .
speaker: E
text: Right ?
speaker: E
text: So that the um <disfmarker> the uh sort of representation that you were just talking about seems more relevant to the kinds of things you would have to do ?
speaker: G
text: Hmm .
speaker: B
text: I 'd <disfmarker> I
speaker: B
text: I think I 'd <disfmarker>
speaker: B
text: I 'm not sure if I understand your question .
speaker: B
text: Only one of those things are gonna be lit up when we pass this on .
speaker: E
text: OK .
speaker: B
text: So only Enter will be <disfmarker>
speaker: B
text: if we <disfmarker> if our <disfmarker> if our module decided that Enter is the case , View and Approach will not be there .
speaker: E
text: OK .
speaker: E
text: OK .
speaker: C
text: Well <vocalsound> uh it 's <disfmarker> it sort of came into my mind that sometimes even two could be on , and would be interesting .
speaker: G
text: Yeah .
speaker: C
text: um nevertheless um
speaker: E
text: Mayb - Well maybe I 'm not understanding where this comes from and where this goes to .
speaker: B
text: Well in that case , we can't <disfmarker> we can't w if <disfmarker> if <disfmarker>
speaker: G
text: OK .
speaker: C
text: l let 's <disfmarker> let 's not <disfmarker>
speaker: B
text: well the thing is if that 's the case we <disfmarker> our <disfmarker> I don't think our system can handle that currently .
speaker: E
text: What are we doing with this ?
speaker: C
text: No , not at all .
speaker: C
text: But <disfmarker> U s <vocalsound> t So <disfmarker>
speaker: E
text: In principle .
speaker: G
text: " Approach and then enter . "
speaker: C
text: the <disfmarker> I think the <disfmarker> in some sense we <disfmarker> we ex get the task done extremely well
speaker: G
text: Run like this
speaker: G
text: uh <disfmarker>
speaker: C
text: because this is exactly the discussion we need <disfmarker> need .
speaker: G
text: Mm - hmm .
speaker: C
text: Period .
speaker: C
text: No more qualifiers than that .
speaker: G
text: No , this is the useful ,
speaker: C
text: So .
speaker: G
text: you know , don don't worry .
speaker: C
text: and um and <disfmarker> and I th I hope
speaker: C
text: um uh
speaker: C
text: let 's make a <disfmarker> a <disfmarker> a <disfmarker> a sharper claim .
speaker: C
text: We will not end this discussion anytime soon .
speaker: G
text: Yeah ,
speaker: G
text: I can guarantee that .
speaker: C
text: And it 's gonna get more and more complex the <disfmarker> the l complexer and larger our domains get .
speaker: E
text: Sigh .
speaker: C
text: And I think um we will have all of our points in writing pretty soon .
speaker: C
text: So this is nice about being being recorded also .
speaker: E
text: Right .
speaker: C
text: The um <disfmarker>
speaker: D
text: That 's true .
speaker: B
text: The r uh the <disfmarker> in terms of why is <disfmarker> it 's laid out like this versus some other <disfmarker>
speaker: C
text: the people <disfmarker>
speaker: E
text: Yeah .
speaker: E
text: Yeah .
speaker: B
text: um that 's kind of a contentious point between the two of us
speaker: B
text: but <vocalsound> this is one wa so this is a way to link uh the way these roles are filled out to the action .
speaker: E
text: In my view .
speaker: E
text: Mm - hmm .
speaker: B
text: Because if we know that Enter is a t is an SPG action ,
speaker: E
text: Mm - hmm .
speaker: B
text: right ?
speaker: B
text: we know to look for an SPG schema and put the appropriate <disfmarker> fill in the appropriate roles later on .
speaker: E
text: Mm - hmm .
speaker: G
text: And you could have also indicated that by saying " Enter , what are the kinds of action I am ? "
speaker: E
text: Yeah .
speaker: C
text: Mm - hmm , yeah .
speaker: B
text: Right .
speaker: E
text: Yeah .
speaker: G
text: Right ?
speaker: G
text: So there 's just like sort of reverse organization ,
speaker: G
text: right ?
speaker: G
text: So like unless @ @ <disfmarker> Are there reasons why one is better than the other I mean that come from other sources ?
speaker: E
text: Again <disfmarker>
speaker: C
text: Yes because nobod no the modules don't <disfmarker>
speaker: G
text: Yeah .
speaker: G
text: uh
speaker: C
text: This is <disfmarker> this is a schema that defines XML messages that are passed from one module to another ,
speaker: G
text: Mm - hmm .
speaker: C
text: mainly meaning from the natural language understanding , or from the deep language understanding to the action planner .
speaker: G
text: Mm - hmm .
speaker: C
text: Now the <disfmarker> the reason for <disfmarker> for not using this approach is because you always will have to go back ,
speaker: C
text: each module will try <disfmarker> have to go back to look up which uh you know entity can have which uh , you know , entity can have which parents ,
speaker: C
text: and then <disfmarker>
speaker: C
text: So you always need the whole body of <disfmarker> of y your model um to figure out what belongs to what .
speaker: C
text: Or you always send it along with it ,
speaker: G
text: Mm - hmm .
speaker: G
text: Mm - hmm .
speaker: C
text: nuh ?
speaker: C
text: So you always send up " here I am <disfmarker> I am this person , and I can have these parents "
speaker: G
text: Mm - hmm .
speaker: C
text: in every message .
speaker: G
text: OK , so it 's just like a pain to have to send it .
speaker: C
text: which e
speaker: C
text: It may or may not be a just a pain
speaker: C
text: it 's <disfmarker> it 's <disfmarker>
speaker: C
text: I 'm completely willing to <disfmarker> to <disfmarker> to throw all of this away
speaker: G
text: OK , I understand .
speaker: C
text: and completely redo it ,
speaker: E
text: Well <disfmarker>
speaker: C
text: you know and <disfmarker> and <disfmarker> and it after some iterations we may just do that .
speaker: G
text: Mm - hmm .
speaker: E
text: I <disfmarker> I would just like to ask um like , if it could happen for next time ,
speaker: E
text: I mean , just beca cuz I 'm new
speaker: E
text: and I don't really just <disfmarker> I just don't know what to make of this
speaker: C
text: Mm - hmm .
speaker: E
text: and what this is for , and stuff like that , you know ,
speaker: E
text: so if someone could make an example of what would actually be in it ,
speaker: C
text: Yeah .
speaker: E
text: like first of all what modules are talking to each other using this ,
speaker: C
text: Yeah , we <disfmarker> I will promise for the next time to have fleshed out N <comment> XML examples for a <disfmarker> a run through and <disfmarker> and see how this <disfmarker> this then translates ,
speaker: E
text: right ?
speaker: E
text: And <disfmarker>
speaker: E
text: OK .
speaker: G
text: Be great .
speaker: C
text: and how this can come about ,
speaker: C
text: nuh ?
speaker: C
text: including the sort of " miracle occurs here " um part .
speaker: E
text: Right .
speaker: C
text: And um
speaker: C
text: is there more to be said ?
speaker: C
text: I think
speaker: C
text: um <disfmarker>
speaker: C
text: In principle what I <disfmarker> I think that this approach does ,
speaker: C
text: and e e whether or not we take the Enter - View and we all throw up <disfmarker> up the ladder
speaker: C
text: um wha how do how does Professor Peter call that ?
speaker: G
text: Yeah .
speaker: C
text: The uh hhh , <comment> silence su sublimination ?
speaker: C
text: Throwing somebody up the stairs ?
speaker: C
text: Have you never read the Peter 's Principle
speaker: E
text: Nope .
speaker: C
text: anyone here ?
speaker: A
text: Oh , uh
speaker: F
text: People reach their level of uh max their level of <disfmarker> at which they 're incompetent or whatever .
speaker: A
text: Yeah .
speaker: C
text: Maximum incompetence
speaker: C
text: and then you can throw them up the stairs
speaker: A
text: Yeah .
speaker: E
text: Alright .
speaker: A
text: Right , right .
speaker: G
text: Oh !
speaker: C
text: um . Yeah .
speaker: A
text: Promote them ,
speaker: A
text: yeah .
speaker: C
text: OK , so we can promote Enter - View all <disfmarker> all up a bit
speaker: C
text: and and get rid of the uh blah - blah - X - blah uh asterisk sub - action item altogether .
speaker: E
text: OK .
speaker: C
text: No <disfmarker> no problem with that
speaker: C
text: and we <disfmarker> w we <disfmarker> we will play around with all of them
speaker: C
text: but the principal distinction between having the <disfmarker> the pure schema and their instantiations on the one hand , and adding some whatever , more intention oriented specification um on parallel to that <disfmarker> that <disfmarker> this approach seems to be uh workable to me .
speaker: C
text: I don't know .
speaker: C
text: If you all share that opinion then that made my day much happier .
speaker: G
text: Uh yeah wait <disfmarker>
speaker: B
text: This is a simple way to basically link uh roles to actions .
speaker: G
text: R Yeah , yeah . That 's fine .
speaker: E
text: Sure .
speaker: B
text: That 's the <disfmarker> that was the intent of <disfmarker> of it , basically .
speaker: G
text: Uh that 's true .
speaker: E
text: Sure .
speaker: G
text: Although um roles <disfmarker>
speaker: C
text: Yeah .
speaker: B
text: So I <disfmarker> I do I 'm <disfmarker> I 'm not <disfmarker>
speaker: G
text: Yeah I <disfmarker> I <disfmarker>
speaker: C
text: I 'm <disfmarker> I 'm never happy when he uses the word " roles " ,
speaker: G
text: Yeah .
speaker: G
text: I was going to <disfmarker>
speaker: C
text: I 'm <disfmarker>
speaker: B
text: I b I mean ROLLS
speaker: B
text: so
speaker: G
text: Bread rolls ?
speaker: E
text: Oh you meant pastries , then ?
speaker: B
text: Yeah , pastries is what I 'm talking about .
speaker: G
text: Pastry
speaker: G
text: oh ba oh the bak bakery example .
speaker: D
text: Bakery .
speaker: E
text: This is the bakery example .
speaker: D
text: Bakery .
speaker: G
text: I see .
speaker: E
text: Got it . Alright .
speaker: G
text: Right . OK .
speaker: E
text: Help !
speaker: G
text: I guess I 'll agree to that , then .
speaker: C
text: OK .
speaker: C
text: That 's all I have for today .
speaker: C
text: Oh no ,
speaker: C
text: there 's one more issue .
speaker: C
text: Bhaskara brought that one up .
speaker: C
text: Meeting time rescheduling .
speaker: G
text: I n Didn't you say something about Friday ,
speaker: G
text: or <disfmarker> ?
speaker: C
text: Yeah .
speaker: G
text: Hmm .
speaker: C
text: So it looks like
speaker: C
text: you have not been partaking ,
speaker: C
text: the Monday at three o ' clock time has turned out to be not good anymore .
speaker: C
text: So people have been thinking about an alternative time
speaker: C
text: and the one we came up with is Friday two - thirty ?
speaker: C
text: three ?
speaker: C
text: What was it ?
speaker: B
text: You have class until two ,
speaker: B
text: right ?
speaker: B
text: so if we don't want him <disfmarker> if we don't want him to run over here
speaker: F
text: Mm - hmm .
speaker: C
text: Two - th Two - thirty - ish or three or Friday at three or something around that time .
speaker: G
text: So do I .
speaker: G
text: Yeah .
speaker: E
text: Mm - hmm .
speaker: B
text: two thirty - ish or three is <disfmarker>
speaker: F
text: Yeah .
speaker: F
text: Yeah .
speaker: F
text: e
speaker: C
text: Um how <disfmarker> how are your <disfmarker>
speaker: G
text: That would be good .
speaker: A
text: uh Friday
speaker: A
text: uh Yeah , that 's fine .
speaker: E
text: Uh <disfmarker>
speaker: C
text: And I know that you have until three <disfmarker> You 're busy ?
speaker: D
text: Yeah .
speaker: G
text: So three is <disfmarker> sounds good ?
speaker: A
text: Yeah .
speaker: E
text: Yeah .
speaker: G
text: I 'll be free by then .
speaker: E
text: I could do that .
speaker: E
text: Yeah I mean earlier on Friday is better but three <disfmarker> you know I mean <disfmarker> if it were a three or a three thirty time then I would take the three or whatever ,
speaker: C
text: Mm - hmm .
speaker: E
text: but yeah sure three is fine .
speaker: C
text: Yeah ,
speaker: C
text: and you can always make it shortly after three probably .
speaker: E
text: I mean .
speaker: D
text: Yeah , and I don't need to be here particularly deeply .
speaker: C
text: Often ,
speaker: C
text: no , but uh ,
speaker: D
text: Yeah .
speaker: C
text: whenever .
speaker: D
text: But yeah .
speaker: C
text: You are more than welcome if you think that this kind of discussion gets you anywhere in <disfmarker> in your life then uh you 're free to c
speaker: D
text: It 's fascinating .
speaker: G
text: " That 's the right answer . "
speaker: D
text: I 'm just glad that I don't have to work it out
speaker: D
text: because .
speaker: E
text: Yeah .
speaker: C
text: Hmm ?
speaker: D
text: I 'm just glad that don't have to work it out myself ,
speaker: D
text: that I 'm not involved at all in the working out of it
speaker: D
text: because .
speaker: E
text: Yeah .
speaker: C
text: Uh but you 're a linguist .
speaker: C
text: You should <disfmarker>
speaker: D
text: Oh yeah . That 's why I 'm glad that I 'm not involved in working it out .
speaker: C
text: OK .
speaker: A
text: So it 's at Friday at three ?
speaker: A
text: there that 's
speaker: C
text: And um
speaker: E
text: So already again this week ,
speaker: E
text: huh ?
speaker: C
text: How diligent do we feel ?
speaker: C
text: Yeah .
speaker: C
text: Do feel that we have done our chores for this week
speaker: C
text: or <disfmarker>
speaker: F
text: Yeah .
speaker: F
text: So I mean clearly there 's <disfmarker> I can talk about the um the parser changes on Friday at least ,
speaker: C
text: OK , Bhaskara will do the big show on Friday .
speaker: F
text: so .
speaker: G
text: And you guys will argue some more ?
speaker: E
text: Yeah . Between now and then .
speaker: B
text: And between now and then yeah .
speaker: G
text: and have some ?
speaker: G
text: probably .
speaker: E
text: Promise ?
speaker: C
text: We will <disfmarker> r
speaker: A
text: Yeah .
speaker: B
text: We will .
speaker: B
text: Don't worry .
speaker: G
text: Yeah .
speaker: G
text: And we 'll get the summary
speaker: A
text: Yeah .
speaker: G
text: like , this <disfmarker> the c you know , short version ,
speaker: G
text: like <disfmarker>
speaker: A
text: An - and I would like to second Keith 's request .
speaker: G
text: S
speaker: A
text: An example wo would be nice
speaker: C
text: Yes .
speaker: E
text: Yeah .
speaker: A
text: t to have kind of a detailed example .
speaker: C
text: Yes . I 've <disfmarker> I 've <disfmarker> I 've <disfmarker> I guess I 'm on record for promising that now .
speaker: A
text: OK .
speaker: C
text: So um <disfmarker>
speaker: G
text: Like have it <disfmarker> we 'll have it in writing .
speaker: G
text: So .
speaker: G
text: or , better , speech .
speaker: G
text: So .
speaker: C
text: This is it
speaker: C
text: and um
speaker: B
text: The other good thing about it is Jerry can be on here on Friday
speaker: B
text: and he can weigh in as well .
speaker: C
text: Yeah .
speaker: C
text: and um if you can get that binding point also maybe with a nice example that would be helpful for Johno and me .
speaker: G
text: Oh yeah
speaker: G
text: uh
speaker: G
text: OK .
speaker: G
text: let 's uh yeah they 're <disfmarker>
speaker: C
text: Give us <disfmarker>
speaker: D
text: No problem ,
speaker: E
text: I think you 've got one on hand ,
speaker: E
text: huh ?
speaker: D
text: yeah .
speaker: G
text: I have several in my head ,
speaker: G
text: yeah .
speaker: G
text: Always thinking about binding .
speaker: C
text: Well the <disfmarker> the <disfmarker> the binding is technically no problem
speaker: C
text: but it 's <disfmarker> it <disfmarker> for me it seems to be conceptually important that we find out if we can s if <disfmarker> if there <disfmarker> if there are things in there that are sort of a general nature ,
speaker: C
text: we should distill them out
speaker: G
text: Mm - hmm .
speaker: C
text: and put them where the schemas are .
speaker: C
text: If there are things that you know are intention - specific , then we should put them up somewhere ,
speaker: G
text: So , in general they 'll be bindings across both intentions and the actions .
speaker: C
text: a
speaker: C
text: Yep .
speaker: G
text: So <disfmarker>
speaker: C
text: That 's wonderful .
speaker: G
text: Yeah .
speaker: G
text: So it 's gen it 's general across all of these things
speaker: G
text: it 's like <disfmarker> I mean Shastri would say you know binding is like <vocalsound> an essential cognitive uh process .
speaker: C
text: Yeah .
speaker: G
text: So . <vocalsound> Um .
speaker: C
text: OK .
speaker: G
text: So I don't think it will be isolated to one or the two ,
speaker: G
text: but you can definitely figure out where <disfmarker>
speaker: G
text: Yeah , sometimes things belong and <disfmarker>
speaker: G
text: So actually I 'm not sure <disfmarker>
speaker: G
text: I would be curious to see how separate the intention part and the action part are in the system .
speaker: G
text: Like I know the whole thing is like intention lattice , or something like that ,
speaker: C
text: Mm - hmm .
speaker: G
text: right ?
speaker: G
text: So is the ri right now are the ideas the rich <disfmarker> rich the RAD or whatever is one you know potential block inside intention .
speaker: G
text: It 's still <disfmarker> it 's still mainly intention hypothesis
speaker: C
text: Yeah .
speaker: C
text: Yeah .
speaker: G
text: and then that 's just one way to describe the <disfmarker> the action part of it .
speaker: C
text: Yeah .
speaker: G
text: OK .
speaker: C
text: It 's <disfmarker>
speaker: B
text: It 's an a attempt to refine it basically .
speaker: C
text: And yeah ,
speaker: G
text: OK , great uh - huh .
speaker: C
text: it 's an <disfmarker> an <disfmarker> it 's <disfmarker> it 's sort of <disfmarker>
speaker: G
text: Not just that you want to go from here to here ,
speaker: G
text: it 's that the action is what you intend
speaker: C
text: Yeah .
speaker: G
text: and this action consists of all com complicated modules and image schemas and whatever .
speaker: G
text: So .
speaker: C
text: Yeah . And <disfmarker> and there will be a <disfmarker> a <disfmarker> a relatively high level of redundancy
speaker: C
text: in the sense that um ultimately one <disfmarker>
speaker: G
text: Mm - hmm .
speaker: G
text: which is ,
speaker: G
text: yeah , It 's fine
speaker: C
text: so th so that if we want to get really cocky we we will say " well if you really look at it , you just need our RAD . "
speaker: C
text: You can throw the rest away ,
speaker: G
text: Mm - hmm .
speaker: C
text: right ?
speaker: G
text: Right .
speaker: C
text: Because you 're not gonna get anymore information out of the action a as you find it there in the domain object .
speaker: G
text: Right .
speaker: G
text: Mm - hmm .
speaker: C
text: But then again um in this case , the domain object may contain information that we don't really care about either .
speaker: G
text: Mm - hmm .
speaker: C
text: So .
speaker: C
text: H But w we 'll see that then , and how <disfmarker> how it sort of evolves .
speaker: G
text: Mm - hmm .
speaker: C
text: I mean if <disfmarker> if people really like our <disfmarker> our RAD ,
speaker: C
text: I mean w what might happen is that they will get rid of that action thing completely ,
speaker: C
text: you know , and leave it up for us to get the parser input um
speaker: G
text: Mmm . We know the things that make use of this thing so that we can just change them so that they make use of RAD .
speaker: C
text: Yeah .
speaker: C
text: Yeah .
speaker: G
text: I can't believe we 're using this term .
speaker: D
text: You don't have to use the acronym .
speaker: G
text: So I 'm like RAD !
speaker: G
text: Like every time I say it , it 's horrible .
speaker: G
text: OK .
speaker: G
text: I see what you mean .
speaker: C
text: Mm - hmm .
speaker: B
text: RAD 's a great term .
speaker: G
text: Is the <disfmarker>
speaker: G
text: But what is the " why " ?
speaker: E
text: It 's rad , even !
speaker: B
text: Why ?
speaker: G
text: Why ?
speaker: E
text: It happened to c be what it stands for .
speaker: C
text: Well <disfmarker>
speaker: B
text: It just happened to be the acronym .
speaker: G
text: Yeah . That 's <disfmarker> doesn't make it a great term .
speaker: G
text: It 's just like those jokes where you have to work on both levels .
speaker: C
text: ye no but i
speaker: D
text: Just think of it as <disfmarker> as " wheel " in German .
speaker: G
text: Do you see what I mean ?
speaker: C
text: but if you <disfmarker> if you <disfmarker> if you work in th in that XML community it is a great acronym
speaker: G
text: Like
speaker: C
text: because it e evokes whatever RDF <disfmarker>
speaker: G
text: Oh .
speaker: C
text: RDF is the biggest thing
speaker: C
text: right ?
speaker: C
text: That 's the rich <disfmarker> sort of " Resource Description Framework "
speaker: E
text: Oh " rich de "
speaker: G
text: Oh .
speaker: C
text: and um <disfmarker> and also <disfmarker>
speaker: C
text: So , description , having the word d term " description " in there is wonderful ,
speaker: G
text: Mm - hmm .
speaker: C
text: uh " rich " is also great ,
speaker: C
text: rwww .
speaker: F
text: Hmm .
speaker: B
text: Who doesn't like to be a
speaker: E
text: Everybody likes action .
speaker: G
text: Oh .
speaker: G
text: Yeah . OK .
speaker: B
text: Yeah .
speaker: E
text: Plus it 's hip .
speaker: G
text: But what if it 's not an action ?
speaker: E
text: The kids 'll like it .
speaker: D
text: Yeah all the kids 'll love it .
speaker: F
text: Hmm .
speaker: C
text: It 's <disfmarker> it 's rad ,
speaker: C
text: yeah .
speaker: G
text: And intentions will be " RID " ?
speaker: G
text: Like ,
speaker: G
text: " OK " .
speaker: G
text: Um are the <disfmarker> are the sample data that you guys showed sometime ago <disfmarker>
speaker: G
text: like the things <disfmarker>
speaker: G
text: maybe <disfmarker> maybe you 're gonna run a trial tomorrow .
speaker: G
text: I mean , I 'm just wondering whether the ac some the actual sentences from this domain will be available .
speaker: G
text: Cuz it 'd be nice for me to like look if I 'm thinking about examples
speaker: G
text: I 'm mostly looking at child language which you know will have some overlap but not total with the kinds of things that you guys are getting .
speaker: G
text: So you showed some in this <disfmarker> here before
speaker: C
text: Mm - hmm .
speaker: G
text: and maybe you 've posted it before
speaker: G
text: but where would I look if I want to see ?
speaker: C
text: Oh I <disfmarker> You want audio ?
speaker: G
text: You know .
speaker: C
text: or do you want transcript ?
speaker: G
text: No just <disfmarker> just transcript .
speaker: C
text: Yeah , well just transcript is just not available
speaker: C
text: because nobody has transcribed it yet .
speaker: G
text: Sorry .
speaker: G
text: Oh , OK .
speaker: C
text: Um I can e I can uh I 'll transcribe it though .
speaker: G
text: I take that back then .
speaker: C
text: It 's no problem .
speaker: G
text: OK , well don't <disfmarker> don't make it a high priority <disfmarker>
speaker: G
text: I <disfmarker> In fact if you just tell me like you know like two examples
speaker: C
text: Yeah .
speaker: G
text: I mean , y
speaker: C
text: Mm - hmm .
speaker: G
text: The <disfmarker> the <disfmarker> the representational problems are <disfmarker> I 'm sure , will be there ,
speaker: C
text: OK .
speaker: G
text: like enough for me to think about .
speaker: G
text: So .
speaker: C
text: OK , so Friday ,
speaker: C
text: whoever wants and comes , and can .
speaker: G
text: OK .
speaker: E
text: OK .
speaker: G
text: Here .
speaker: C
text: This Friday .
speaker: G
text: OK .
speaker: C
text: The big parser show .
speaker: C
text: Now you can all turn off your <disfmarker>

Meeting summary:
text: The data collection script has been slightly modified, so that it encourages more natural dialogue between the subjects and the "wizard".
text: Another trial run will take place, while a call to recruit subjects is being emailed to students.
text: Meanwhile, the translation of the TV and cinema information system to english is almost complete.
text: This was the basic requirement of the project.
text: On the other hand, there was a presentation of the model that offers more elaborate action planning for SmartKom, of which Enter/View/Approach (EVA) modes are a part.
text: These modes will form categories of complete XML schemas with information filled in from the language understanding in a more elaborate way than the current Object-"Go Action"-Object model.
text: These categories will, in turn, be linked with action schemas, one of which is Source-Path-Goal (SPG).
text: Categories and action schemas can have -in theory- any number of blocks depending on the expansion of the domain.
text: The notation provides for linking and referencing between different schemas.
text: The model also allows for multiple action schemas to be triggered in parallel.
text: However, the structure of the model is open for discussion, since its use was to elicit discussion and highlight issues.
text: As the data collection is about to start, a call for the recruitment of subjects is going to be sent out.
text: The main pool of subjects is going to be the student community in the institute.
text: Along with the "wizard", who is going to be an integral part of the experiments, another person needs to be hired as the instructor for the tasks involved in them.
text: Meetings were rescheduled and are now going to take place on Fridays.
text: For the next meeting, there is going to be a presentation of the modifications in the parser module of the basic system.
text: Additionally, the proposed XML model will be put to the test with concrete data.
text: Similarly, such examples will clarify issues relating to the binding and redundancy of features with common characteristics amongst the shcemas (eg "Container" for Enter and "Goal" for SPG).
text: Subjects in the trial runs of the experiment were given detailed descriptions of the tasks, which led to the subsequent dialogue being a re-iteration or re-phrasing of the instructions.
text: Using pictures instead would be one way to deal with the problem, however, it was deemed too laborious and it would divert the focus of the experiment.
text: As the original action planner of the SmartKom system only included a generic SPG schema, a new module was presented that allows for variety in the user intentions to be included.
text: This being only a model, there are several issues that will need to be clarified in the future.
text: How the model deals with redundancy of information among categories and action schemas, and whether a flat or a hierarchical model would be preferable are two of them.
text: What is also clear is that as the domain of research broadens beyond the study of EVA modes, the complexity of the model will also increase.
text: Another trial run of the data collection experiment is to take place, while subjects are being recruited.
text: There have been some adjustments in the script.
text: The prior description of tasks the subjects are going to be given is now going to be more schematic, although the intentions are still going to be clear.
text: The lack of detailed, written explanation will hopefully encourage more natural and varied dialogue between subjects and "wizard".
text: On the other hand, the generator module of the system has been translated from german.
text: Eventually, a user is going to be able to request and receive TV- and cinema-related information in english.
text: This will satisfy the basic project requirements.
text: The model of a new module for SmartKom was presented.
text: It is an interface between the language understanding and the action planning modules.
text: One layer of XML schemas creates a richer representation of the linguistic analysis, which is subsequently used to trigger one or more action schemas.
text: The model keeps the concept of XML messages being sent between the modules of the system, although it is open-ended as to the number of schemas involved.