Google Developers Blog: standards
COLLECTED BY
Organization:
Internet Archive
The Internet Archive discovers and captures web pages through many different web crawls.
At any given time several distinct crawls are running, some for months, and some every day or longer.
View the web archive through the
Wayback Machine .
Wide17 was seeded with the "Total Domains" list of 256,796,456 URLs provided by Domains Index on June 26th, and crawled with max-hops set to "3" and de-duplication set "on".
The Wayback Machine - https://web.archive.org/web/20190427211616/https://developers.googleblog.com/search/label/standards
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.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?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!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.By Max Ross, Software Engineer
By Mark Pilgrim, Google Code Team Google Doctype .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.
Post by Joe Gregorio, Google Developer Programs 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."...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!"-Lisa Dusseault (Apps Area Director)
By Zaheda Bhorat, Open Source Team Google welcomes the ISO decision to not approve the fast track of Office Open XML (OOXML) proposed standard DIS 29500 (ECMA 376).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). Open Document Format (ODF) , which already offers a high degree of interoperability, wide support, and offers the level playing field the world needs. Google is a supporter of ODF and has successfully integrated this open format into Google Docs and Spreadsheets. ODF also enjoys implementation in over twelve other products .here , here and here ).
Posted by Dion Almaer, Google Developer Programs comprehensive, detailed analysis of how markup is used on the Web which gives his real world metrics to go by.recently published their Q & A session .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)? here .
Post by Matt Austern, Software Engineering Team 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).]
