- From: SULLIVAN, BRYAN L <bs3131@att.com>
- Date: Thu, 23 Jan 2014 03:17:44 +0000
- To: Koichi Takagi <ko-takagi@kddi.com>
- CC: "public-web-mobile@w3.org" <public-web-mobile@w3.org>
If we avoid problematic words but arrive at the same destination I am happy. I am not a fan of arbitrary lists or vocabulary prohibitions, and do not recommend that W3C engage in either. But reasoned focus on priorities given real-world use cases, yes. Whatever you accept to call that, I'm ok with it. Thanks, Bryan Sullivan On Jan 22, 2014, at 7:14 PM, "Koichi Takagi" <ko-takagi@kddi.com> wrote: The word "Profile" may cause misunderstanding. Generally speaking, the meaning of the word "Profile" is [1] (as Natasha said). In terms of this meaning, "Profile" shall destroy the idea "one Web"[2]. Anyway, if we need another discussion, we should choose (or define) the different word. I think that's why Robin does not use the word "Profile" in the draft[2]. # I cannot find any other better word^^;;; [1] http://en.wikipedia.org/wiki/Profile_%28engineering%29 [2] http://www.w3.org/TR/mobile-bp/#OneWeb Koichi > Hi all, > >>> On Wednesday, January 22, 2014 at 5:25 PM, Natasha Rooney wrote: >>> >>> >>> >>>> Sorry, can you clarify what you mean by profiles? I'm not sure what > that is. >>> >>> Lists of standards that something must adhere to. So, mobile browsers > should have adhered to all the standards detailed on the "Coremob" profile. >> >> Oh, please please please no! Please let's not do that. Those silly lists > are really unhelpful and constantly fall out of date (and are actually > harmful in that they put a ceiling on what standards are to be supported > by user agents). WAC tried to do this and it failed miserably, and so have > a whole bunch of other organizations that don't get the Web. >> >> One of the main reasons why we have living standards now is to put an > end to profiles - i.e., the platform wants to be constantly updated (a > platform that accesses constantly updating applications but can't update > itself can only harm the Web... as legacy browsers once did before folks > moved to an evergreen development model - but we are still seeing how toxic > non-updating browsers can be in Android 2.3 and old version of Windows where > people are stuck on IE8... poor souls). >> >> Profiles encourage people to reference dated/versioned specs (very bad!), > which are what stagnate the Web. Instead, for example, if one references > WHATWG HTML, it means "keep up with this living and always improving thing". > That's much better and how the Web really works (or, ideally, how we want > it to work). > > +100! ^^ > > I dislike profile. > I did a similar argument last year in web-based signage BG.*1 This is easily > understandable thing when you watch the short history from XHTML to HTML5. > > [1] > http://lists.w3.org/Archives/Public/public-websignage/2013May/0006.htm > l (web-based signage bg ml) > > Regards, > > Satoru Takagi
Received on Thursday, 23 January 2014 03:18:34 UTC