TPAC2007Session4

From W3C Wiki

TPAC 2007: Session 4: Lightning Talks

/!\ This session transcript needs to be edited. Please consider updating this entry

agenda audio

Transcript

>> Our next session, the last one before lunch, is the all exciting lightening talks.

>> I am happy to have Matt [ indiscernible ] to talk through Rotan and he will be moderating this for us today.

>> We are voting on a wild card session, and the second session will have the last presentation which is voted on the online poll, and the link is in the information for the key package.

I am going to get the video set up and we will start with PBS.

>> I'm sorry.

>> TV?

>> The video is not up yet, actually.

>> The title of this sort of come out, because when we were organizing the division and the program, the question is what is the view from the outside look like. And someone told me I am not qualified, because I had been in the W3C for too long.

>> My slide is not up yet.

>> I'll wait.

>> All right.

>> So the -- what?

>> It's coming.

>> [ LAUGHTER ]

>> Okay.

>> So the goal that is to define what makes [ indiscernible ] succeed and -- [ Speaker/Audio unclear due to strong accent ]

>> So go to my next slide, sir.

>> What are the necessary -- what's going on?

>> Hold on.

Sorry.

>> [ LAUGHTER ]

>> [ LAUGHTER ]

>> Sorry.

>> [ Speaker/Audio unclear due to strong accent ]

>> [ LAUGHTER ]

>> [ APPLAUSE ]

>> So let me know what you want me to do.

>> That will probably distract the audience more.

>> Okay.

>> Yeah, sure.

>> [ APPLAUSE ]

>> So apprenticeship to my next -- flip to my next slide.

>> What are the necessary -- [ Speaker/Audio Not Clear ]

>> Flip to my next slide.

>> You need to define success, as you heard from all of the data and [ indiscernible ] that everybody lives in their own world and calls it their own.

I don't believe that success is a standard process, meaning the [ indiscernible ] process that is bow does.

>> Success also -- bogus.

>> [ Speaker/Audio unclear due to strong accent ]

>> So flip to my next slide.

>> This slide sort of lists what they call the out and out [ indiscernible ]

>> HTTP was successful because of the protocol.

>> HTML has had a problem, because it was really never [ Speaker/Audio unclear due to strong accent ]

>> You can see the HTTP was extremely successful, because not only was it adopted and successful because of many things.

>> Let's get rid of the slides and do the --

>> So it was extremely successful because a lot of things that people couldn't imagine they were able to build on top of HTTP.

>> They are able to do [ indiscernible ] on top of HTTP.

>> [ Speaker/Audio unclear due to strong accent ]

>> I think that is a market and measurement of success.

I would hold HTTP up as the board standarder for doing the standards right.

>> [ Speaker/Audio unclear due to strong accent ]

>> I don't hold them to the same level.

>> They have a lot of the adaptability problems.

>> It I have seen a huge -- I have seen a huge amount of -- [ Speaker/Audio unclear due to strong accent ]

>> That I think is a -- [ Speaker/Audio unclear due to strong accent ]

>> Things that I call question able are like HTML [ indiscernible ] I wouldn't inflict that on my worth enemy.

>> All of the things have the target that work for the -- [ Speaker/Audio unclear due to strong accent ]

>> This is my goal, it meets my goal, go away.

>> It doesn't necessarily lead to people building on that complicated lead finish the next level.

>> Don't define success in the standard process in the HTTP process.

>> Standards that work are ones that allow people to build on what you have done, and often successful standards not only solve the problems that you set out to solve, but they end up solving a lot more.

>> Again, I hold HTTP up on that.

>> Hopefully I have not made anymore enemies than I already have by talking about HTTP standard.

>> [ APPLAUSE ]

>> I am going to give the slides one more try.

>> Questions, yes, were there any questions?

>> No questions.

>> Let's give Debbie [ indiscernible ]

[Audio Cutting In and

[Audio Cutting In and

[Audio Cutting In and Out]

[Audio Cutting In and Out]

>> I'm going to talk about the multimobile working interaction group.

>> You can go forward.

>> So, the multimobile interaction group is working on applications that will allow us to use the web more than the traditional mobility.

We work with the keyboard and mouse.

To that we are implementing voice and handwriting interactions.

>> We have other interactions that are being implemented like [ indiscernible ] and [ indiscernible ]

>> Users can do a lot of different things when they want to interact with people.

We want to bring that as a more natural and mature application.

>> This time -- we don't actually have time to do the demos in this session, but the exciting thing about the applications that we are developing now is that they are starting to be based on the standards of the multimobile group and the browsers group, and other groups.

We are excited about improving the groups on standards.

>> This is an example of the reference application, and this is multimobile group, and this is T-shirt ordering.

We have several different objects that you can order, T-shirts or pants, they can be different colors or sizes, and you can say something like I would like a T-shirt in a large in this color.

There is not only the interaction of different modalities, but we can also point at the same time we are speaking and have that information being integrated and result in a T-shirt.

>> The screen shot that we just showed is something the working group members have already implemented.

This next one is a little bit of what might be the next step.

>> You can kind out what the user is, it is speech integrating and all of that.

>> Just to talk a little bit about the plumbing that under lies, in this application there is the architecture that has pieces the functionality.

We have the interaction manager with the code and the modalities, and the interaction manager that focuses on the -- [ Speaker/Audio Faint & Unclear ]

>> We use E CCI for keeping track of the user preferences and the device properties, and then we have the different modalities and the speech interaction, ISSL, [ indiscernible ], and [ indiscernible ], and all of the voice standards, and Inc. EML is by the multimobile working group, and then we have a common [ indiscernible ] in the working group.

>> The user input is represented in ammo which is being developed by the multimobile working group.

>> [ Speaker/Audio Faint & Unclear ] faint.

>> Okay.

>> This is a summary about the points of the multimobile working group.

>> This is some of the principals and they are loosely coupled in an event phase of the multiple modalities and the combination of the applications.

>> That is important and this is the requirements for our group.

There is a invent stage of the life cycles and alikes that we define.

We strongly believe that it is in cancellation of the modality components of the other modality groups.

[Audio Cutting In and Out]

>> Thank you.

>> [ APPLAUSE ]

>> Again, there is nobody queued up.

>> [ LAUGHTER ]

>> Hello everybody, I am [ indiscernible ] from [ indiscernible ]

>> [ indiscernible ] is one of the -- [ Speaker/Audio unclear due to strong accent ]

>> I would like to explain to you why.

The idea of the mobile is simple.

>> [ Speaker/Audio unclear due to strong accent ]

>> And what is amazing is that she understands it.

>> Basically -- [ Speaker/Audio unclear due to strong accent ]

>> You can try to access it.

>> Why the mobile to these sites.

If you try to access them from -- [ Speaker/Audio unclear due to strong accent ] -- for example, it's a good smart form and browsers, but what you see doesn't make that much sense.

>> [ Speaker/Audio unclear due to strong accent ]

>> One of the important things for the user to bring on is the time for it to download.

>> It takes a good [ indiscernible ] connection and 45 seconds to download.

>> [ Speaker/Audio unclear due to strong accent ]

>> On 3G in good condition, it will take about 10 seconds.

>> It is fantastic and [ Speaker/Audio unclear due to strong accent ]

>> [ Speaker/Audio unclear due to strong accent ]

>> Most people in this world don't have the -- [ Speaker/Audio unclear due to strong accent ]

>> What people would pay is from 50-cents to -- [ Speaker/Audio unclear due to strong accent ]

>> [ Speaker/Audio unclear due to strong accent ]

>> Actually, [ Speaker/Audio unclear due to strong accent ], mobile friendly internet.

>> Helping to explain the work and make the offer.

>> The additions out there are very nice -- [ Speaker/Audio unclear due to strong accent ]

>> Do it yourself, website implementation tools, and that is pertaining to everybody -- [ Speaker/Audio unclear due to strong accent ]

>> So in confusion, I would like to say that [ Speaker/Audio unclear due to strong accent ]

>> It's about mobility and creativity.

>> [ APPLAUSE ]

>> Any questions?

>> That is a problem, so which one of you will own the -- [ Speaker/Audio unclear due to strong accent ]

>> So someone would have to buy it and you own it.

>> In the future there will be more coming from that icon, so that will suggest how the internet will be working.

>> [ Speaker/Audio unclear due to strong accent ]

>> It probably don't matter if you can't spell it, because it is probably only me.

I can have the.org, -- [ Speaker/Audio unclear due to strong accent ]

>> That's a great demand, because it is slightly cheaper.

>> [ LAUGHTER ]

>> And this technology stack that has been around for a long time, based on the HTML, does the [ Speaker/Audio Not Clear ] allow you to adapt the content to a device.

It's not very -- [ inaudible ] -- build a browser, to say hey, I have a hand held style sheet and it says don't worry about the complicated designs it is able to be downloaded to specific net work connections.

I can make my site look good on a browser, but just with one domain that I want to pay for.

Why do we need a whole set of different domains.

We have browsers that can do this.

Why are we aren't we saying let's make the browsers work.

>> Right, but I --

>> [ APPLAUSE ]

>> Right but I would say that we need people to encourage to use the internet, and they have not tried it or they have tried and had a bad experience.

>> For a lot of people they have never used the mobile because of the [ indiscernible ]

>> [ Speaker/Audio unclear due to strong accent ]

>> So it would work, but the people need to know in advance.

>> I think we are going to close the queue after the people in line are done.

>> Keep the questions nice and short.

>> I realize that this is wonderful that I made people realize that people now -- [ Speaker/Audio unclear due to strong accent ]

>> It's important that the slides should be used in the multiple languages.

>> There is a site on that called dot lang.

>> [ Speaker/Audio unclear due to strong accent ]

>> We could have -- you could get your -- put your site at NXXdot lang, dot mobr, or moby dot languor -- [ Speaker/Audio unclear due to strong accent ] encourage the people to use the internet even more.

>> [ APPLAUSE ]

>> They are unable to support it, because of what we need to make sure of, but if they had the main level, then it would be the massive data on or about it.

If dot Moby -- [ Speaker/Audio unclear due to strong accent ]

>> Maybe not directly, but there is a compliance check.

>> I think we should take the names for that what are.

They are simple and use them for what you want.

>> The user -- [ Speaker/Audio unclear due to strong accent ]

>> [ Speaker/Audio unclear due to strong accent ]

>> I think that maybe I am saying the same thing as the previous speakers.

What are we going to do reset all of our sites for a different [ indiscernible ], because they need to work in some other way in a normal way.

[Audio Cutting In and Out]

>> [ Speaker/Audio unclear due to strong accent ]

>> Okay.

>> Let's have something uncontroversial.

>> [ LAUGHTER ]

>> [ indiscernible ] is back.

>> [ APPLAUSE ]

>> [ LAUGHTER ]

>> Why is my keyboard not working?

>> Speakers in audience unclear.

>> My laptop has just blown up here.

>> Okay.

So [ indiscernible ] is back.

>> [ LAUGHTER ]

>> [ LAUGHTER ]

>> [ APPLAUSE ]

>> [ indiscernible ] is back.

>> [ indiscernible ] is worse.

>> I am [ indiscernible ] and I am going to talk to you about one type of spam, link spam.

I am not going to talk about all of the spams.

Just like e-mail spam -- [ Speaker/Audio Not Clear ]

>> It's targeted at the search engine, and the solution is simple just mark the website at the user that is from the blogger comment and the external comments that is added to such.

>> The parking green is for the [ indiscernible ] blogger and the one is red that shouldn't be in the context.

>> We have now throne out of the -- thrown out of all of comments, we have thrown out the baby in the back waters.

The day we have throne out the link -- thrown out of the link spam -- [ Speaker/Audio unclear due to strong accent ]

>> We have to have an authentication mechanism.

And we can choose the ID, and then we use the method for marketing again, here is the comments that is coming from the blogger, here is who posted this, and so as far as the search engines are concerned -- speaker/audio unclear due to loud background noises, buzzing.

>> This has an interesting effect on the -- [ Speaker/Audio Not Clear ] so in summary, let's make link spam the small talk of sham.

We can go -- spam.

We can do it in weeks.

>> All we have to do is have the -- [ Speaker/Audio Not Clear ]

>> I don't have time to go into the rest of the link spams to eliminate, but it will be available in my book at the bookstore.

>> [ LAUGHTER ]

>> [ APPLAUSE ]

>> Thank you.

>> My name is -- [ Speaker/Audio unclear due to strong accent ]

>> I'm trying to explain to you what are the -- [ Speaker/Audio unclear due to strong accent ] -- as you will all note the amount of content that we -- [ Speaker/Audio unclear due to strong accent ] -- is increasing increasing.

>> And now the web is starting to see us there and the access information any where any time.

>> If we think about the use of expectation, the mobile is very different.

>> You serve the mobile, they don't want to type all of the things or include on spy ware or [ indiscernible ] or finding the information they want.

>> Also, it is important that they would like to get with us on our [ Speaker/Audio unclear due to strong accent ]

>> Also, it is very important to take into account the location and the time in the situations and that is very important.

>> This our challenge for self-condensed.

And what are you telling us from the user requirements that we can face especially you are saying interfaces of lab rally is the -- liberally is the nice approach.

>> [ Speaker/Audio unclear due to strong accent ]

>> But also from the believer [ Speaker/Audio unclear due to strong accent ] point of view.

>> The challenge here is how to index the contents on the -- [ Speaker/Audio unclear due to strong accent ]

>> From how the content is ready to lead from a normal device.

>> The channels of the content are not the -- [ Speaker/Audio unclear due to strong accent ]

>> So that content at the present time should not be here when it comes to browsing on the specific device.

>> So this is a very challenging point.

>> Here are the -- [ Speaker/Audio unclear due to strong accent ]

That can be used during this time with the challenges.

I know so.

>> They can come out with different criteria, so you need to come up with a -- [ Speaker/Audio unclear due to strong accent ] -- for finding different rankings and things that can be combined with the different sources.

>> [ APPLAUSE ]

>> Sorry about the technical problems.

They will hopefully be sorted out a little better for the next session.

>> There is a vote for the lightening talks.

The URI is on the [ indiscernible ] channel on the [ indiscernible ] and I will also circulate it to people who ask.

>> Let's give a hand to those who spoke in lightening talks, and also to Matt for the moderation.

>> A couple of things.

We have two different locations for lunch.

We are going to try to make think as -- going to try to make this as smoothly as possible.

>> The other people that we are going to ask to go up there is the AC advisory committees and the divided guests on the team.

>> It's the bounce tables and the invited guests and the team and round tables.

There are some signs out there that are under the tent and you should be able to walk out there and get some fresh out there as well.

>> This is a first time you have been to the [ Speaker/Audio Not Clear ] meeting.

>> We are going to reconvene this afternoon at 1:30, 13:30.

It is okay to leave your laptops here if you want to, we will have someone watching over them.

>> So if you are looking forward to the second lightening talks session, that will be later on this afternoon.

Please look for that.

>> Thank you.

>> Music playing.

>> W3C conference on lunch break until 1:30 eastern time.

>> Please stand by for real-time captioned text.

>> Captioner on music hold.

>> Please come in and take your seats and we will start in just a minute or two.