Skip to main content

Home/ Web2.0/ Group items tagged w3c

Rss Feed Group items tagged

Hendy Irawan

The Forms Working Group - 0 views

    The Forms working group is chartered by the W3C to develop the next generation of forms technology for the world wide web. The mission is to address the patterns of intricacy, dynamism, multi-modality, and device independence that have become prevalent in Web Forms Applications around the world. The technical reports of this working group have the root name XForms due to the use of XML to express the vocabulary of the forms technology developed by the working group. The Forms Working Group is comprised of W3C members and invited experts. The Working Group meets weekly by phone. Face to face meetings occur roughly every 3 months and are hosted by member organizations. We are especially interested in people with a rich experience in developing Web forms and supporting tools.
Hendy Irawan

Introduction to W3C Widgets - QuirksBlog - 0 views

    "Essentially, a widget is a local HTML/CSS/JavaScript web application. A mobile phone user downloads a widget once, and from that moment on he has a web application stored locally on his mobile phone. Although currently widgets are mostly used for relatively limited functions such as clocks, RSS readers, or Twitter or Flickr clients, as well as for games, there's no theoretical reason why they couldn't contain a complete, complicated, JavaScript-heavy web application; for instance a mobile-optimised spreadsheet application."
Graham Perrin

ODF versus OOXML: Don't forget about HTML! - O'Reilly XML Blog - 0 views

  • Don't forget about HTML
  • February 25, 2007
  • HTML’s potential and actual suitability for much document interchange
  • ...27 more annotations...
  • HTML is the format to consider first
  • validated, standards compliant XHTML in particular
  • HTML at one end (simple WP documents)
  • PDF at the other end (full page fidility but read-only)
  • W3C versus ISO
  • Lie adopts an extreme view towards overlap of standards:
  • overlap at all brings nothing but misery and bloat.
  • The next dodgy detail is to make blanket comparisons between HTML and ODF/OOXML.
  • ODF and OOXML deal with many issues that HTML/CSS simply does not.
  • the W3C argument might be to say that every part should have a URL
  • a strange theory that MS wants ODF and OOXML to both fail
  • being pro-ODF does not mean you have have to be anti-OOXML
  • HTML is the format of choice for interchange of simple documents
  • ODF will evolve to be the format of choice for more complicated documents
  • OOXML is the format of choice for full-fidelity dumps from MS Office
  • PDF is the format of choice for non-editable page-faithful documents
  • all have overlap
  • we need to to encourage a rich library of standard technologies,
  • widely deployed,
  • free,
  • unencumbered,
  • explicit,
  • awareness of when each is appropriate
  • an adequate set of profiles and profile validators
  • using ISO Schematron
  • Plurality
Kheeran D

HTML 5: Could it kill Flash and Silverlight? - Network World - 0 views

  • The World Wide Web Consortium's (W3C) HTML 5 proposal is geared toward Web applications
  • HTML 5 tackles the gap that Flash, Silverlight, and JavaFX are trying to fill

website designing company in rohini - 0 views


website designing company in rohini webexpert seo services

started by ogeninfo on 05 Apr 17 no follow-up yet
Gary Edwards

Siding with HTML over XHTML, My Decision to Switch - Monday By Noon - 1 views

  • Publishing content on the Web is in no way limited to professional developers or designers, much of the reason the net is so active is because anyone can make a website. Sure, we (as knowledgeable professionals or hobbyists) all hope to make the Web a better place by doing our part in publishing documents with semantically rich, valid markup, but the reality is that those documents are rare. It’s important to keep in mind the true nature of the Internet; an open platform for information sharing.
  • XHTML2 has some very good ideas that I hope can become part of the web. However, it’s unrealistic to think that all web authors will switch to an XML-based syntax which demands that browsers stop processing the document on the first error. XML’s draconian policy was an attempt to clean up the web. This was done around 1996 when lots of invalid content entered the web. CSS took a different approach: instead of demanding that content isn’t processed, we defined rules for how to handle the undefined. It’s called “forward-compatible parsing” and means we can add new constructs without breaking the old. So, I don’t think XHTML is a realistic option for the masses. HTML 5 is it.
    • Gary Edwards
      Great quote from CSS expert Hakon Wium Lie.
  • @marbux: Of course i disagree with your interop assessment, but I wondered how it is that you’re missing the point. I think you confuse web applications with legacy desktop – client/server application model. And that confusion leads to the mistake of trying to transfer the desktop document model to one that could adequately service advancing web applications.
    Response to marbux comments.
    # See also my comment on the same web page that explains why HTML 5 is NOT it for document exchange between web editing applications. . - comment by marbux # Response to marbux supporting the WebKit layout/document model. Marbux argues that HTML5 is not interoperable, and CSS2 near useless. HTML5 fails regarding the the interop web appplications need. I respond by arguing that the only way to look at web applications is to consider that the browser layout engine is the web application layout engine! Web applications are actually written to the browser layout/document model, OR, to take advantage of browser plug-in capabilities. The interoperability marbux seeks is tied directly to the browser layout engine. In this context, the web format is simply a reflection of that layout engine. If there's an interop problem, it comes from browser madness differentials. The good news is that there are all kinds of efforts to close the browser gap: including WHATWG - HTML5, CSS3, W3C DOM, JavaScript Libraries, Google GWT (Java to JavaScript), Yahoo GUI, and the my favorite; WebKit. The bad news is that the clock is ticking. Microsoft has pulled the trigger and the great migration of MSOffice client/server systems to the MS WebSTack-Mesh architecture has begun. Key to this transition are the WPF-.NET proprietary formats, protocols and interfaces such as XAML, Silverlight, LINQ, and Smart Tags. New business processes are being written, and old legacy desktop bound processes are being transitioned to this emerging platform. The fight for the Open Web is on, with Microsoft threatening to transtion their entire business desktop monopoly to a Web platform they own. The Web is going to be broken. There is no way of stopping Microsoft at this point. What we can do though is focus on Open Web solutions that are worthy alternatives to Microsoft's proprietary push. For me, this means the WebKit layout/document model supported by Apple, Adobe and Google. ~ge~
    A CMS expert argues for HTML over XHTML, explaining his reasons for switching. Excellent read! He nails the basics. for similar reasons, we moved from ODF to ePUB and then to CDf and finally to the advanced WebKit document model, where wikiWORD will make it's stand.
Graham Perrin

SweoIG/TaskForces/CommunityProjects/LinkingOpenData - ESW Wiki - 0 views

  • LinkingOpenData
  • The Open Data Movement aims at making data freely available to everyone
  • The goal of the W3C SWEO Linking Open Data community project is to extend the Web with a data commons
  • ...3 more annotations...
  • publishing various open data sets as RDF
  • RDF links between data items from different data sources
  • Generating Linked Data from non RDF Data Sources via the Virtuoso Sponger
Graham Perrin

About AJAW and the Tabulator - 0 views

  • one possible form of a semantic web browser
  • bugs on other platforms
  • make RDF access easy
  • ...12 more annotations...
  • demonstrate the use of Web architecture and Semantic web architecture
  • throw up problems
  • for the W3C TAG
  • best practices documents
  • find problems in general implementations or usage
  • find and design new breadcrumb protocols
  • conventions by which pointers are left and followed
  • make classes of problem solvable
  • Other browsers have tended to focus on a document at a time, or work by amassing a large static database of RDF
  • This browser works in a web of documents
  • much semantic web data is isolated from other webs of data,
  • links across systems. This browser is designed to use these links
Graham Perrin

Mindswap - 19 views

  • Mindswap
  • Maryland Information and Network Dynamics Lab Semantic Web Agents Project
  • The MINDSWAP Group
  • ...3 more annotations...
  • Semantic Web Research Group
  • working with Semantic Web technology
  • inside the MIND LAB at University of Maryland Institute for Advanced Computer Studies
Hendy Irawan

XForms Essentials - 0 views

    At last, XForms-officially described at a way for web forms to serve as XML data collection tools. Increasingly, IT departments are using XML and native XML databases to store mission-critical data. Workflow and routing systems rely on XML for data representation. Web services, which are growing immensely in popularity, are the final piece of the puzzle-making it easy (and providing needed tool support) to send and receive XML data and documents.
Hendy Irawan

XForms - Wikibooks, open books for an open world - 0 views

    XForms is a World Wide Web Consortium recommendation for creating web forms and web applications. XForms is easy to learn, provides a rich user experience and does not require you to learn JavaScript. This is a collaborative project and we encourage everyone who is using XForms to contribute their complete working XForms examples. All example programs must conform to the creative-commons-2.5 share-alike with attribution license agreement [1]. Note: We have restructured the main page to make it easier to classify your examples. Note for example that now all the search examples have been grouped together. The "Next Page" links have not yet been updated. Instructors: please sign our Guest Registry if you are using this book for learning or teaching XForms. Contributors: please see our Naming Conventions to ensure your examples are consistent with the textbook. If you are looking for a specific example program, please feel free to use the Examples Wanted section. If you feel these examples are useful please create links to this site. This book has over 30 contributors. Recent Changes Google Code Version Control System Book Statistics Related Wikibooks: XQuery XForms/REST/XQuery Note: Almost all of the examples have been tested with the FireFox 2.0 XForms addon and the newer 0.8.6ff3 FireFox 3.0 addon. Please let us know if you find any errors.
Hendy Irawan

XForms Tutorial - 0 views

    XForms is the next generation of HTML forms. In our XForms tutorial you will learn how to use XForms in your applications. Start learning XForms now!

W3 Total Cache Wordpress Plugin Review | Speed Up Wordpress Site Plugins 2014 - 0 views

    w3 total cache settings wordpress w3 total cache w3 total cache cdn w3 total cache wordpress w3 total cache w3 total cache browser cache settings w3 total cache help w3 total cache guide w3c total cache w3 total cache vs hyper cache cache plugin wordpress w3tc object cache w3tc

Web application Development Company India - iStudio Technologies - 3 views

As the best web application development company in India, we at iStudio Technologies provides the most valuable and splendid service in web app development. Holding more than a decade of experience...

technology app

started by istudiosmo on 06 Oct 18 no follow-up yet
1 - 20 of 20
Showing 20 items per page