Skip to main content

Home/ Web2.0/ Group items tagged interoperability

Rss Feed Group items tagged

avivajazz  jazzaviva

EgoPage for Writers, Bloggers, Musicians, Marketers, Many Many More! - 0 views

  •  
    There are heaps of other sites all around the web where you can put your short stories, anything from DeviantART to Yahoo! Geocities, so when the magical unicorns went to create Ego, they knew exactly what they wanted. Ego was born to be a tool that specializes in creative writing of all sorts, one not distracted by social functionality. With lovely typography and beautiful designs, writers and roleplayers can focus on their writing and have results like this page, without any branding or distractions to the reader. Owning Your Content With some websites you need to agree to Terms of Service pages far too long to read, selling your soul, and your creations, to the website operators. Not so with Ego. There are no Terms of Service beyond three simple rules: No Pornography, No Illigal Material, and the unicorns may remove content they feel inappropriate. If your content is removed, this simply means that your account will be restricted from publishing through the ego website, and to host your content you'll need to use the Download Zip functionality to get the html files, and upload them to a hosting service. You will continue to have access to your content regardless of these rules, unless we're legally required to remove it, or we become aware of attempts on your part to disrupt access for other users. Interoperability When you publish through Ego, not only is the static html file available, but also a 'JSON' based computer source code file, which can be read in the vast majority of common programming languages, and manipulated with ease. This means that if you provide a link to one of your pages on another website, they can potentially do all sorts of interesting things with the data, like import it in to their own competing publishing systems, add it to a search engine, or combine it with other useful information like maps. If you'd like more information on this, check out our page on Hacking. Additionally, when creating a new page, there are a few othe
  •  
    There are heaps of other sites all around the web where you can put your short stories, anything from DeviantART to Yahoo! Geocities, so when the magical unicorns went to create Ego, they knew exactly what they wanted. Ego was born to be a tool that specializes in creative writing of all sorts, one not distracted by social functionality. With lovely typography and beautiful designs, writers and roleplayers can focus on their writing and have results like this page, without any branding or distractions to the reader. Owning Your Content With some websites you need to agree to Terms of Service pages far too long to read, selling your soul, and your creations, to the website operators. Not so with Ego. There are no Terms of Service beyond three simple rules: No Pornography, No Illigal Material, and the unicorns may remove content they feel inappropriate. If your content is removed, this simply means that your account will be restricted from publishing through the ego website, and to host your content you'll need to use the Download Zip functionality to get the html files, and upload them to a hosting service. You will continue to have access to your content regardless of these rules, unless we're legally required to remove it, or we become aware of attempts on your part to disrupt access for other users. Interoperability When you publish through Ego, not only is the static html file available, but also a 'JSON' based computer source code file, which can be read in the vast majority of common programming languages, and manipulated with ease. This means that if you provide a link to one of your pages on another website, they can potentially do all sorts of interesting things with the data, like import it in to their own competing publishing systems, add it to a search engine, or combine it with other useful information like maps. If you'd like more information on this, check out our page on Hacking. Additionally, when creating a new page, there are a few othe
Hendy Irawan

Open Data Protocol (OData) - 0 views

  •  
    "The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today. OData does this by applying and building upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores. The protocol emerged from experiences implementing AtomPub clients and servers in a variety of products over the past several years. OData is being used to expose and access information from a variety of sources including, but not limited to, relational databases, file systems, content management systems and traditional Web sites. OData is consistent with the way the Web works - it makes a deep commitment to URIs for resource identification and commits to an HTTP-based, uniform interface for interacting with those resources (just like the Web). This commitment to core Web principles allows OData to enable a new level of data integration and interoperability across a broad range of clients, servers, services, and tools. OData is released under the Open Specification Promise to allow anyone to freely interoperate with OData implementations."
Dr. Sorin Adam Matei

OGC Network™ | OGC Network - 0 views

  •  
    OGC Network™ is a window onto the dynamic, constantly changing geospatial web as described by the OpenGIS® Reference Model (ORM). Multiple communities of interest for research in geospatial interoperability are supported, and persistent demonstration capability is provided. Here you will find the latest information on OGC-compatible software, services, and information models (e.g. GML profiles, SLD examples, etc.). From this site you can quickly locate OGC-compatible geospatial web services, the latest XML schema documents, discussion forums, conformance testing resources, and GML profile working areas. Instructions on signing up for authoring privileges are on the help page.
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

Introduction ‎(Google Wave Federation Protocol)‎ - 0 views

  • Google Wave Federation Protocol
  • for sharing waves between wave providers
  • anyone can build a wave server and interoperate
  • ...2 more annotations...
  • open source, production-quality, reference implementation of the Google Wave client and server
  • open federation endpoint
Cathy Oxley

The Next Big Thing is Web 3.0 | - 108 views

  • ...9 more comments...
  •  
    Rediffmail login Rediffmail Sign In
  •  
    Hotmail login Hotmail Sign In
  •  
    Web 3.0 is the Semantic web ITpedia says: Web 3.0 gives meaning to documents and links. The current web can be regarded as a collection of documents linked to each other via links. The functioning of the web depends on good agreements about the form (syntax) of web pages and links. https://en.itpedia.nl/2011/05/31/web-3-0-semantisch-web/
  •  
    You've picked up the perfect dog-friendly grooming kit from the local pet Store https://udluthfi.co.id/
  •  
    With Web 3.0, the data generated by disparate and increasingly powerful computing resources, including mobile phones, desktops, appliances, vehicles, and sensors, will be sold by users through decentralized data networks, ensuring that users retain ownership control. https://www.verzdesign.com/
  •  
    Oh, yeah. That's good to hear. We use it for SaaS companies. Thanks for sharing. https://quickhr.co/features/payroll
  •  
    [url=https://mrbetresenas.ar/]mr bet casino login[/url] mr bet casino login sparta slot [youtube converter](https://www.typingservice.org/)
  •  
    Web 3.0 is a term used to describe the next evolution of the internet, in which the focus is on creating a decentralized, distributed network that is powered by blockchain technology. This new version of the web is expected to enable new applications and services, such as decentralized finance (DeFi), non-fungible tokens (NFTs), and autonomous organizations (AOs), that are not possible with current web technologies. Additionally, Web 3.0 is expected to enable greater privacy, security, and control for users, as well as more interoperability between different platforms and systems. learn more visit our website. https://bylocalseo.com/
1 - 7 of 7
Showing 20 items per page