Création des Logiciels de gestion d'Entreprise, Création et référencement des sites web, Réseaux et Maintenance, Conception
seo Google welcomes ISO decision on OOXML 2013
Seo Master present to you: Google welcomes the ISO decision to not approve the fast track of Office Open XML (OOXML) proposed standard DIS 29500 (ECMA 376).
Our engineers conducted an independent analysis of the OOXML specification and found several areas of concern, which we communicated both to the ISO and to the public. These include and are not limited to the following:
The ISO approval required at least 2/3 (i.e., 66.66%) of the votes cast by participating (P) members to be positive, and no more than 1/4 (i.e., 25%) of the total number of national body votes cast negative. Neither of these criteria were met by the proposed standard.
The concerns from many technical experts around the world were submitted as comments by the voting bodies to ISO on September 2, 2007. These must now be resolved at a Ballot Resolution Meeting (BRM) on February 25-29, 2008. In contrast, ODF was approved unanimously (23-0 among P members, 31-0 overall) as an international standard by ISO in May 2006.
As we represented our position in many countries, we were encouraged by the process observed in some places that truly evaluated the proposed standard on its technical merits as well as the feasibility of implementing the standard for the people of the country. These countries successfully declined or abstained due to insufficient information about the standard or the lack of time to evaluate the specification. In addition, many irregularities have been reported in the voting process (see here, here and here).
Technical standards should be arrived at transparently, openly, and based on technical merit. Google is committed to helping the standards community remain true to this ideal and maintain their independence from any commercial pressure.
Google supports one open document format and calls on industry participants to collaboratively work on ODF. With multiple implementations of one open standard for documents, users, businesses and governments around the world can have both choice and freedom to access their own documents, share with others and pass onto future generations.2013, By: Seo Master
Our engineers conducted an independent analysis of the OOXML specification and found several areas of concern, which we communicated both to the ISO and to the public. These include and are not limited to the following:
- for a specification of this size it was not given enough time for review;
- the undocumented features of OOXML prevents its implementation by other vendors;
- dependencies on other Microsoft proprietary formats and their technical defects makes it difficult to fully implement; and
- the overall cost for vendors of implementing multiple standards (hence the lack of OOXML implementations in the marketplace).
The ISO approval required at least 2/3 (i.e., 66.66%) of the votes cast by participating (P) members to be positive, and no more than 1/4 (i.e., 25%) of the total number of national body votes cast negative. Neither of these criteria were met by the proposed standard.
The concerns from many technical experts around the world were submitted as comments by the voting bodies to ISO on September 2, 2007. These must now be resolved at a Ballot Resolution Meeting (BRM) on February 25-29, 2008. In contrast, ODF was approved unanimously (23-0 among P members, 31-0 overall) as an international standard by ISO in May 2006.
As we represented our position in many countries, we were encouraged by the process observed in some places that truly evaluated the proposed standard on its technical merits as well as the feasibility of implementing the standard for the people of the country. These countries successfully declined or abstained due to insufficient information about the standard or the lack of time to evaluate the specification. In addition, many irregularities have been reported in the voting process (see here, here and here).
Technical standards should be arrived at transparently, openly, and based on technical merit. Google is committed to helping the standards community remain true to this ideal and maintain their independence from any commercial pressure.
Google supports one open document format and calls on industry participants to collaboratively work on ODF. With multiple implementations of one open standard for documents, users, businesses and governments around the world can have both choice and freedom to access their own documents, share with others and pass onto future generations.2013, By: Seo Master
seo Introducing Google Doctype 2013
Seo Master present to you:
The open web is the web built on open standards: HTML, JavaScript, CSS, and more. The open web is a beautiful soup of barely compatible clients and servers. It comprises billions of pages, millions of users, and thousands of browser-based applications. You can access the open web with open source and proprietary browsers, on open source and proprietary operating systems, on open source and proprietary hardware.
Google has built its business here, on the open web, and we want to help you build here too. To that end, we are happy to announce the formation of an encyclopedia for web developers, by web developers: Google Doctype.
In its current (beta) form, Google Doctype contains dozens of articles written by top Googlers on topics important to all web developers: security, performance, caching, DOM manipulation, CSS styling, and more. It contains over 8,000 lines of JavaScript code: Google's own battle-tested JavaScript library, released today under a liberal open source license. And it contains the beginnings of a test-driven reference of the open web: a reference of every element, every attribute, every DOM method, every CSS property, all backed up by test cases.
Well, not quite every property; at least, not yet. We're still working on filling in a few of the details about the world's largest development platform ever, and we need your help. And so we humbly offer this fledgling encyclopedia under a Creative Commons Attribution license, and we invite the web developers of the world to contribute to it. Sign in with your Google account and edit any page, any article, anywhere. Create new ones, update old ones, and help expand the world's understanding of the open web.2013, By: Seo Master
The open web is the web built on open standards: HTML, JavaScript, CSS, and more. The open web is a beautiful soup of barely compatible clients and servers. It comprises billions of pages, millions of users, and thousands of browser-based applications. You can access the open web with open source and proprietary browsers, on open source and proprietary operating systems, on open source and proprietary hardware.
Google has built its business here, on the open web, and we want to help you build here too. To that end, we are happy to announce the formation of an encyclopedia for web developers, by web developers: Google Doctype.
In its current (beta) form, Google Doctype contains dozens of articles written by top Googlers on topics important to all web developers: security, performance, caching, DOM manipulation, CSS styling, and more. It contains over 8,000 lines of JavaScript code: Google's own battle-tested JavaScript library, released today under a liberal open source license. And it contains the beginnings of a test-driven reference of the open web: a reference of every element, every attribute, every DOM method, every CSS property, all backed up by test cases.
Well, not quite every property; at least, not yet. We're still working on filling in a few of the details about the world's largest development platform ever, and we need your help. And so we humbly offer this fledgling encyclopedia under a Creative Commons Attribution license, and we invite the web developers of the world to contribute to it. Sign in with your Google account and edit any page, any article, anywhere. Create new ones, update old ones, and help expand the world's understanding of the open web.2013, By: Seo Master
seo Standards-based Persistence For Java™ Apps On Google App Engine 2013
Seo Master present to you: When I sat down to write this post I decided to glance back at my last post on this blog. One sentence in particular jumped out at me: "...I would never again feel compelled to build an [Object-Relational] Mapping framework in Java." Well, friends, never say never. Now that we've unveiled an early look at Java support for Google App Engine, I'm thrilled to announce the availability of a JDO and JPA implementation for the App Engine datastore under the Apache 2 open source license.
The App Engine datastore is an incredible piece of technology. Based on Google's own Bigtable, it's one of the key reasons App Engine enables developers to write web applications that scale without infrastructure headaches. But, it isn't necessarily what most of us are accustomed to using for persistence. Wouldn't it be lovely if we could use an existing programming model on top of the datastore API? And wouldn't it be even lovelier if that existing programming model simplified the process of porting web applications on and off App Engine?
Fortunately for us Java developers we have not one, but two persistence standards at our disposal, JDO and JPA. And, to make adopting these persistence standards easier, we have the DataNucleus project (formerly JPOX), which provides plugins that connect these standards to various types of datasources. Andy Jefferson, founder of the DataNucleus project, was not only enthusiastic about our effort to add an App Engine plugin to his project, he was also incredibly helpful (thanks Andy!). I hope you're as excited about the results as I am: Standards-based persistence for the App Engine datastore!
Since App Engine for Python launched almost a year ago I've admired not just the applications that have been built by the developer community but the infrastructure as well. Even though the DataNucleus App Engine plugin was developed by Googlers, it uses the public App Engine APIs that are available to everyone. It uses no backdoors or special privileges. Rather, it is merely the first instance of what I hope will be a torrent of Java infrastructure developed for App Engine for Java. Feel free to peruse the code at http://code.google.com/p/datanucleus-appengine. If you find a bug, send us a patch. And if you think you can do better, do better! There's absolutely nothing stopping you.
2013, By: Seo Master
The App Engine datastore is an incredible piece of technology. Based on Google's own Bigtable, it's one of the key reasons App Engine enables developers to write web applications that scale without infrastructure headaches. But, it isn't necessarily what most of us are accustomed to using for persistence. Wouldn't it be lovely if we could use an existing programming model on top of the datastore API? And wouldn't it be even lovelier if that existing programming model simplified the process of porting web applications on and off App Engine?
Fortunately for us Java developers we have not one, but two persistence standards at our disposal, JDO and JPA. And, to make adopting these persistence standards easier, we have the DataNucleus project (formerly JPOX), which provides plugins that connect these standards to various types of datasources. Andy Jefferson, founder of the DataNucleus project, was not only enthusiastic about our effort to add an App Engine plugin to his project, he was also incredibly helpful (thanks Andy!). I hope you're as excited about the results as I am: Standards-based persistence for the App Engine datastore!
Since App Engine for Python launched almost a year ago I've admired not just the applications that have been built by the developer community but the infrastructure as well. Even though the DataNucleus App Engine plugin was developed by Googlers, it uses the public App Engine APIs that are available to everyone. It uses no backdoors or special privileges. Rather, it is merely the first instance of what I hope will be a torrent of Java infrastructure developed for App Engine for Java. Feel free to peruse the code at http://code.google.com/p/datanucleus-appengine. If you find a bug, send us a patch. And if you think you can do better, do better! There's absolutely nothing stopping you.
2013, By: Seo Master
seo Interview with Ian Hickson on X/HTML 5 2013
Seo Master present to you:
What is more important to the future of the web than the future of HTML, and adoption of technology in the browsers? Our own Ian Hickson has been blazing a trail under the WHATWG umbrella, as he tries to do the right thing, and standardize what is already being down, instead of making a specification in an isolated room.
Back in 2005, Ian conducted a comprehensive, detailed analysis of how markup is used on the Web which gives his real world metrics to go by.
Vlad Alexander from xhtml.com was invited to post a series of questions to the X/HTML 5 team on their public mailing list, and recently published their Q & A session.
If you haven't stayed up to date on what is happening around the standards, take a peek to see how the team answered questions such as:
What is more important to the future of the web than the future of HTML, and adoption of technology in the browsers? Our own Ian Hickson has been blazing a trail under the WHATWG umbrella, as he tries to do the right thing, and standardize what is already being down, instead of making a specification in an isolated room.
Back in 2005, Ian conducted a comprehensive, detailed analysis of how markup is used on the Web which gives his real world metrics to go by.
Vlad Alexander from xhtml.com was invited to post a series of questions to the X/HTML 5 team on their public mailing list, and recently published their Q & A session.
If you haven't stayed up to date on what is happening around the standards, take a peek to see how the team answered questions such as:
- Why do we need X/HTML 5? When did this need become apparent?
- X/HTML 5 is currently in Working Draft stage. What is the tentative timetable for moving X/HTML 5 through the standards approval process towards Recommendation stage?
- X/HTML 5 introduces new markup constructs such as sectioning elements, enhancements to the input element, a construct for dialogs, a way to mark up figures, and much more. Can you briefly describe these new constructs and the reason they were added?
- X/HTML 5 has a construct for adding additional semantics to existing elements using predefined class names. Predefined class names could be the most controversial part of X/HTML 5, because the implementation overloads the class attribute. XHTML 2 provides similar functionality using the role attribute. Which approach is better and why?
- Is it due to a flaw in HTML that it is difficult to build authoring tools, such as WYSIWYG editors, that generate markup rich in semantics, embody best-practices and that can be easily used by non-technical people?
- Since much of the content on the Web is created using such authoring tools, can we ever achieve a semantically rich and accessible Web?
- The XHTML 5 spec says that "generally speaking, authors are discouraged from trying to use XML on the Web". Why write an XML spec like XHTML 5 and then discourage authors from using it? Why not just drop support for XML (XHTML 5)?
seo Google Hosts C++ Standards Meeting 2013
Seo Master present to you:
Two weeks ago, Google hosted a two-day informal meeting to discuss Concepts, a major new language feature for the next version of C++. Concepts are the foundation of generic programming, but until now they haven't been part of the actual C++ language. Last week's meeting was part of a multi-year effort to improve C++ by adding explicit support for Concepts. Papers have already been given at the Principles for Programming Language Symposium (pdf) and the Object Oriented Programming, Systems, Languages & Applications Conference (pdf).
Attendees at last week's meeting made significant progress: the group finalized many details of Concepts and resolved concerns about implementation issues. Keep an eye on the C++ Standards Committee Website, as the final version of the concepts proposal will be available in just a few weeks.
[Photo caption: Attendees at the C++ Concepts meeting came from both industry and academia. Left to right: Martin Sebor (Rogue Wave), Chris Lattner (Apple), John Spicer (EDG), Herb Sutter (Microsoft), Andrew Lumsdaine (Indiana University), Michael Wong (IBM), Bjarne Stroustrup (Texas A&M), Gabriel Dos Reis (Texas A&M), Thomas Witt (Zephyr Associates), Mat Marcus (Adobe), Steve Clamage (Sun), Sean Parent (Adobe), Lawrence Crowl (Google), Nathan Myers (Aspera Software), Doug Gregor (Indiana University), Jaakko Jaarvi (Texas A&M), Matt Austern (Google).]2013, By: Seo Master
Two weeks ago, Google hosted a two-day informal meeting to discuss Concepts, a major new language feature for the next version of C++. Concepts are the foundation of generic programming, but until now they haven't been part of the actual C++ language. Last week's meeting was part of a multi-year effort to improve C++ by adding explicit support for Concepts. Papers have already been given at the Principles for Programming Language Symposium (pdf) and the Object Oriented Programming, Systems, Languages & Applications Conference (pdf).
Attendees at last week's meeting made significant progress: the group finalized many details of Concepts and resolved concerns about implementation issues. Keep an eye on the C++ Standards Committee Website, as the final version of the concepts proposal will be available in just a few weeks.
[Photo caption: Attendees at the C++ Concepts meeting came from both industry and academia. Left to right: Martin Sebor (Rogue Wave), Chris Lattner (Apple), John Spicer (EDG), Herb Sutter (Microsoft), Andrew Lumsdaine (Indiana University), Michael Wong (IBM), Bjarne Stroustrup (Texas A&M), Gabriel Dos Reis (Texas A&M), Thomas Witt (Zephyr Associates), Mat Marcus (Adobe), Steve Clamage (Sun), Sean Parent (Adobe), Lawrence Crowl (Google), Nathan Myers (Aspera Software), Doug Gregor (Indiana University), Jaakko Jaarvi (Texas A&M), Matt Austern (Google).]2013, By: Seo Master
seo IETF Applications Area Architecture Workshop 2013
Seo Master present to you:
On February 11 and 12 Google hosted the Internet Engineering Task Force (IETF) Application Area Architecture Workshop. This was a chance for people active in the IETF Applications Area to get together and work on architectural issues, topics that span many specific groups in the Applications area.
The Applications Area is the part of the IETF that deals with applications
On February 11 and 12 Google hosted the Internet Engineering Task Force (IETF) Application Area Architecture Workshop. This was a chance for people active in the IETF Applications Area to get together and work on architectural issues, topics that span many specific groups in the Applications area.
The Applications Area is the part of the IETF that deals with applications
"...that is, things that are not security (part of the security area), nor networks (most of the other areas), but rather things that use the networks and security services to provide things of benefit to the end-user."This was of particular interest to me since that includes specifications like the Atom Syndication Format and the Atom Publishing Protocol, which we use extensively at Google. From the call for participation:
"These should be a few pages of text on some topic related to Applications area architectural issues. Since the group of attendees is expected to span HTTP and AtomPub, email, IM, calendaring, directories and more, issues should be of interest to more than one of these groups. Some existing Applications architecture "modules" that already are reused include SASL, URLs, MIME types, XML and XML schemas and namespaces, HTTP as a substrate, TLS, ABNF, BEEP."We had around 20 attendees and the breakout sessions ranged over all the topics listed above and many more. There were two days of great conversation and everyone had a good time.
"Thank you for the high quality hosting and convenience of location and food!"2013, By: Seo Master-Lisa Dusseault (Apps Area Director)