W3C home > Mailing lists > Public > public-lod@w3.org > May 2020

Re: Apologies

From: Lee Curtis <lee.curtis@me.com>
Date: Sun, 3 May 2020 10:05:15 +1000
Cc: semantic-web at W3C <semantic-web@w3c.org>, public-rww <public-rww@w3.org>, public-lod <public-lod@w3.org>
Message-Id: <0950FBBB-A1FF-4030-962B-003D4E064589@me.com>
To: Sebastian Samaruga <ssamarug@gmail.com>
Hi Seb

I’ve been on a similar journey. Both bipolar and your search for this particular Rosetta Stone. I may have reached out to you earlier, apologies if I have. 

I was going to offer this a personal reply but reconsidered. Perhaps, there is another lone wolf out there that wants to engage.  

It’s a fascinating topic but one that seems not to resonate with members of the W3C. Nor many in enterprise, TBH. I hope your experience differs. I too believe that Enterprise use cases are compelling and with concerted effort would have driven funding, innovation and skill sets. Sadly, it didn’t happen and semantic web didn’t get the adoption and traction it deserved. 

I’ve implemented many of these concepts too both in RDF/RDFS (I never upgraded to OWL) and also in code (Java). I ceased work on it about 10 years ago due to economic factors (feeding a family). The passion that once burned bright has now dimmed. 

For EAI, I leveraged the patterns encoded in Apache Camel and found it effective. I also explored Lambda functions within an RDF graph (not AWS marketing term) as an attempt to create a symbolic computational graph - i suspect Wolfram Alpha has nailed it. 

I employed an RDF graph (Using OpenRDF nee Sesame) combined with embedded and annotated CONSTRUCT queries (later SPIN) to create a graph-embedded transformational substrate that facilitated mapping between common data structures and industry standards such as Swagger/OpenAPI.

I mapped most JVM scripting languages - including AppleScript, VB, python and Ruby. It was cute. I also audited my documents, spreadsheets and PDF and augmented them with some naive NLP. I hooked up libpcap and mapped a few networks. In a vain attempt to create awareness of the environment the software operated in. A kind of semantic self-awareness. 

I did go so far as to deploy an enterprise project controls system for a mid-size client using some of the ideas but my software engineers kept pushing to use their own approaches (SQL and static code) and I eventually caved and that diluted the implementation.

Many of the ideas and approaches are still part of my work today but the “graphs as a source of truth” for data and processing hasn’t seen the light of day in a decade. Maybe, one day I’ll revisit them. 

Anyways if you want to chat, drop me a line. I would be fun to kick around these old ideas again and maybe dust off some code. 

Stay safe

Lee Curtis
M: +61 415 125 747 | Skype: lee_curtis

>> On 3 May 2020, at 04:34, Sebastian Samaruga <ssamarug@gmail.com> wrote:
> 
> Hi all. This mail is an apology for the often sent messages which are the result of one of my maniac depressive episodes (and is also one of such messages).
> 
> This style of writing is kind of a therapeutic one: when I've put in clear text what my attempts are for, chances are I'll find a cure for this disease...
> 
> The document attached is another of such attempts. Updates of drafts will be in the repository and in the blog. Thanks a lot for your patience if you dare in understanding.
> 
> It's a raw description of an enumeration of items for an ESB / EAI integration patterns infrastructure, a "Rosetta Stone" for workflows, knowledge and information integration.
> 
> What I'm looking in this lists is guidelines regarding implementation and existing state of the art in this subject. I didn't begin coding yet for this reasons and would help a lot to know which features / APIs / formats a solution like this would need to be useful. Thanks,
> 
> Sebastián Samaruga
> http://sebxama.blogspot.com
> http://github.com/sebxama/scrapbook
> 
> <Items.docx>

Received on Sunday, 3 May 2020 00:05:33 UTC

This archive was generated by hypermail 2.4.0 : Sunday, 3 May 2020 00:05:35 UTC