{
  "version": "https://jsonfeed.org/version/1.1",
  "title": "chem-bla-ics",
  "description": "Chemblaics (pronounced chem-bla-ics) is the science that uses open science and computers to solve problems in chemistry, biochemistry and related fields.",
  "home_page_url": "https://chem-bla-ics.linkedchemistry.info/",
  "feed_url": "https://chem-bla-ics.linkedchemistry.info/2009/08/13/last-call-xep-0244-io-data.json",
  "icon": "https://chem-bla-ics.linkedchemistry.info/assets/images/chem-bla-ics_logo.png",
  "language": "en",
  "authors": [
    {
      "name": "Egon Willighagen",
      "url": "https://orcid.org/0000-0001-7542-0286",
      "_orcid": "0000-0001-7542-0286"
    }
  ],
  "items": [

    {
      "id": "https://doi.org/10.59350/y1ka2-ad976",
      "url": "https://chem-bla-ics.linkedchemistry.info/2009/08/13/last-call-xep-0244-io-data.html",
      "title": ""LAST CALL: XEP-0244 (IO Data)"",
      "content_html": "<p>Today I received this email, which is a milestone for the <a href=\"http://en.wikipedia.org/wiki/Extensible_Messaging_and_Presence_Protocol\">XMPP</a>\n(aka Jabber) work Johannes, Ola and I have been working on as SOAP alternative using the intrinsically asynchronous XMPP as transport\nprotocol instead of HTTP as SOAP commonly does (see\n<a href=\"https://chem-bla-ics.linkedchemistry.info/2008/10/31/next-generation-asynchronous.html\">Next generation asynchronous webservices <i class=\"fa-solid fa-recycle fa-xs\"></i></a>):</p>\n\n<blockquote>\n  <p>This message constitutes notice of a Last Call for comments on XEP-0244 (IO Data).</p>\n\n  <p>Abstract: This specification defines an XMPP protocol extension for handling the input to and output from a remote entity.</p>\n\n  <p>URL: <a href=\"https://www.xmpp.org/extensions/xep-0244.html\">http://www.xmpp.org/extensions/xep-0244.html</a></p>\n\n  <p>This Last Call begins today and shall end at the close of business on 2009-09-01.</p>\n\n  <p>Please consider the following questions during this Last Call and send your feedback to the standards @ xmpp.org discussion list:</p>\n\n  <ol>\n    <li>Is this specification needed to fill gaps in the XMPP protocol stack or to clarify an existing protocol?</li>\n    <li>Does the specification solve the problem stated in the introduction and requirements?</li>\n    <li>Do you plan to implement this specification in your code? If not, why not?</li>\n    <li>Do you have any security concerns related to this specification?</li>\n    <li>Is the specification accurate and clearly written?</li>\n  </ol>\n\n  <p>Your feedback is appreciated!</p>\n</blockquote>\n\n<p>There remains quite a lot to do, and you are more than welcome to join in the project. There is a Java library and we’ve\nintegrated the specs into <a href=\"http://www.bioclipse.net/\">Bioclipse</a> and <a href=\"http://taverna.sf.net/\">Taverna</a> (see\n<a href=\"https://chem-bla-ics.linkedchemistry.info/2009/01/21/details-behind-calling-xmpp-cloud.html\">Details behind the “Calling XMPP cloud services from Taverna2” <i class=\"fa-solid fa-recycle fa-xs\"></i></a>),\nbut there is no support for BioCatalogue yet, and no libraries for other programming language yet.</p>",
      "summary": "Today I received this email, which is a milestone for the XMPP (aka Jabber) work Johannes, Ola and I have been working on as SOAP alternative using the intrinsically asynchronous XMPP as transport protocol instead of HTTP as SOAP commonly does (see Next generation asynchronous webservices ):",
      
      "date_published": "2009-08-13T00:00:00+00:00",
      "date_modified": "2026-03-07T00:00:00+00:00",
      "tags": ["xmpp","bioinfo","cheminf"],
      
      
      
      
      
      
        "authors": [ { "name": "Egon Willighagen", "url": "https://orcid.org/0000-0001-7542-0286" } ]
      
    }

  ]
}