Re: Working draft (revisited)

The usefulness of coding it up is that it gives clarity. It's easy to
posit things in a vaguely convincing (to yourself, to begin with) way,
but coding the detail, even for an hypothetical example, exposes the
bits you've not thought of, enabling clarity of thought.

On 21 December 2017 at 00:59, Sebastian Samaruga <> wrote:
> Hi all,
> I know I've been publishing a series of posts that maybe lacks of academic
> formality or shape / coherence. My intentions are not to spam the lists with
> content that maybe don't deserve the reading time of the subscribers. That's
> why I warn everybody that I'm just a Semantic 'hobbyist' dumping thoughts in
> a bottle.
> Feel free to skip reading my mesagges. Although sometimes I receive very
> valuable feedback, sometimes people seems bothered with what I publish.
> My attempt now is finally to start writting code. I've added an appendix to
> the document which explains details I didn't realized in the past and which
> are fundamental for the deployment of an implementation (WIP, fuzzy draft).
> I've also suffered of paralysis in an 'analysis' phase in which because of
> lack knowledge and work responsabilities I couldn't code much.
> The idea is to write a very small functional API library for the processing
> of streams (bus) of models of knowledge (resources) and their contexts
> (templates) from which to apply aggregation and alignment / inference. Then,
> given opportune APIs, provide implementations of connectors and 'deployers'
> wrapper endpoints
> Again, this is a very fuzzy early draft of a document WIP which doesn't
> qualify yet even as an analysis or specification document. But it's useful
> for me to post it, even as a reminder of the work progress I've doing.
> Thanks,
> Sebastián.

Peter Brooks

Mobile: +27 82 717 6404
Direct:  +27 21 447 9752
Skype:  Fustbariclation
Twitter: Fustbariclation
Google+: Fustbariclation
Author Page:

Received on Thursday, 21 December 2017 04:35:35 UTC