W3C home > Mailing lists > Public > public-semweb-lifesci@w3.org > December 2010

Re: An Universal Exchange Language

From: Adrian Walker <adriandwalker@gmail.com>
Date: Tue, 14 Dec 2010 17:36:54 -0500
Message-ID: <AANLkTi=dKXkmupetc4_VM4scjN1pgmmCj6Kcys9nNMFF@mail.gmail.com>
To: Matthias Löbe <matthias.loebe@imise.uni-leipzig.de>
Cc: public-semweb-lifesci@w3.org
Hi Mathias --

You asked for suggestions related to a future Universal Exchange Language.

I'd suggest that the Language should look outwards towards human usability
and understandability, as well as inwards towards the technology.

Fortunately, there's a system that supports this.  It's called Executable
English and it's live online at the site below [1]

There's a short overview paper [2] explaining why combining three kinds of
semantics may be important for a project of this kind.

                                                    -- Adrian

[1]   Internet Business Logic
A Wiki and SOA Endpoint for Executable Open Vocabulary English Q/A over SQL
and RDF
Online at www.reengineeringllc.com
Shared use is free, and there are no advertisements

[2]
www.reengineeringllc.com/A_Wiki_for_Business_Rules_in_Open_Vocabulary_Executable_English.pdf



Adrian Walker
Reengineering




2010/12/14 Matthias Löbe <matthias.loebe@imise.uni-leipzig.de>

> Hello to all,
>
> The US President's Council of Advisors on Science and Technology
> (PCAST) has released a think tank document on "a path forward to
> future health information technology"
> [
> http://www.whitehouse.gov/sites/default/files/microsites/ostp/pcast-health-it-report.pdf
> ].
>
> A central point is to create an "Universal Exchange Language" that is
> architecturally neutral, XML-based, extensible, optimized for
> representing structured data, and that should have the ability to
> include/ reference controlled vocabularies. That language would be
> used to design fine-grained data elements that could be tagged with
> metadata. These data elements should be modular, reusable, interlinked
> and should not be tied to a specific context.
>
> Estimation of the costs for developing such a language is $20 million
> to $40 million.
>
> Any suggestions?
>
> Matthias
>
> --
> Matthias Löbe, Inst. for Medical Informatics (IMISE), University of Leipzig
> Härtelstr. 16, D-04107 Leipzig, +49 341 97 16113,
> loebe@imise.uni-leipzig.de
>
>
Received on Tuesday, 14 December 2010 22:37:29 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:01:00 GMT