ПоискПочтаДискКалендарьДеньгиМой КругФотки

Друзья, 28 июля мы закрываем Я.ру. Приносим вам свои извинения.




записи по  

месяцам · меткам · типам

выделить все / снять выделение

twirl написал
изменено 24 июня 2013 года, в 21:03
W3C TAG Member Election
W3C Technical Architecture Group (The TAG) is now holding an election for a new member, and I'm running for it.

Let me introduce myself. My name is Sergey Konstantinov, and I'm working for Yandex (most recently as a Maps API R&D Head). Obviously, I'm not well-known at W3C as Yandex hasn't been a member for a full year yet. But this doesn't mean that we have little experience with standards. Just the opposite - we have years of experience in dealing Web Standards and maintaining our own APIs, which are de facto standards in our home markets. We acquired some expertise in API lifecycle management the hard way, and we know very well that the rapid development of new standards always carries risks.

So our primary concern is the fresh new Web Standards which emerged in the last few years. There are dozens of new standards, and that's very good for developers as they have new possibilities; but it also means that inevitably there will be the problems of growth: inconsistencies, controversies and architecture flaws.

The TAG's stated mission is: "(1) to document and build consensus around principles of Web architecture and to interpret and clarify these principles when necessary; (2) to resolve issues involving general Web architecture brought to the TAG; (3) to help coordinate cross-technology architecture developments inside and outside W3C.". So that's why I'm here, and that's exactly the thing I'd like to do. If the TAG needs reform to comply with its mission -- then, okay, call me the reformist.

Working on our own APIs we strictly keep to "use-case-centic" approach. It means that we understand the task not just as creating some methods and formats, but building useful tools for the web masters that allow them to solve their users' problems. Every piece of functionality must have a reason: who will use it? how? what problem does it solve? And, of course: is it clear, how to use it and what problem it solves?

Regretfully, for Web Standards, though these principles are generally accepted, their implementation leads to inconsistencies across the different Working Groups, because every WG has its own vision on Standards development. We have many standards which are pretty clean and functional, but make the developers to write bad code, to make common mistakes or even to abandon the idea of using the Standard in their services. The structure that should coordinate all the WGs to help WGs to elaborate the common approach is the TAG.

Let me say a risky thought: the beauty and the cleanness and the perfection of the standard do not automatically mean the ergonomics and the usefulness. Let me also say that the task of encouraging the developers to use the standard properly, of spreading good programming techniques and of making the standard work as it intended to, is far more tricky thing than just to make it clean and functional. I'm sure that our vast experience in dealing with the webmasters will be of help for the TAG and for the Web in general.

I should also note, that from our distant view there is also a clearly visible lack of W3C localization. Russian (Indian, Japanese, Chinese, etc) developers are greatly relying on local content and local developer societies, and the W3C is relatively unknown here - nor the local demands are known to W3C. I hope to bring some local expectations to the TAG and to popularize the Web Standards and W3C work to local communities in addition to the main work with standards.


Что получается:    изменить 
Подписаться на комментарии к записи

Получать уведомления о всех ответах в этом обсуждении.

Отписаться от комментарев к записи

Получать уведомления только о тех ответах в этом обсуждении, которые адресованы лично вам.

К сожалению, комментарий не удалось отправить. Попробуйте ещё раз.я в курсе