Re: Applications

Paola, thanks for the feedback.

What my attempts are about where, in the beginning, to match different URIs
or identifiers which refer to the same entity (in different databases /
ontologies, for example) to perform some kind of "ontology matching".

Then I've tried to develop a mechanism for using RDF Quads for encoding an
object graph (and a layers class hierarchy) using Contexts to denote the
class of an instance, Subjects to denote class instances and attributes
(members) and values: Predicates / Objects.

Quads are "reified" as Resource(s). Also, Resource is a functional wrapper
reactive and event driven of an URI. And an URI could be implemented with
whatever backend which could produce or consume events (databases,
services, etc.). Resource layers hierarchy (Context) is to be implemented
by an actor / role type object pattern.

Then I've realized that some basic type inference could be performed with,
for example, aggregating Subjects with the same predicates (Subject Kinds).
Idem for Predicates, Objects and Contexts. I've also realized that plain
"facts" statements could be aggregated in the previously mentioned class
hierarchy to abstract further, from plain data, instance / class layers of
what I call data / schema / behavior layers. Higher layers (i.e.: Behavior)
"aggregate" lower layers.

Layers shape is as follow:

Resource : Functional URI wrapper.

(Context : Resource, Occurrence : Resource, Attribute : Resource, Value :
Resource);

Each layer abstract:

Statement (data instance):

(Statement, Occurrence, Attribute, Value);

someOne buys someProduct;


Entity (data class):
(Entity, Statement, Occurrence, Attribute);
someBuyer, someProduct (Entity);

Role (schema instance):
(Role, Entity, Statement, Occurrence);
Buyer, Product (Role);

Class (schema class):
(Class, Role, Entity, Statement);
Person, Good (Class);

Flow (behavior instance):
(Flow, Class, Role, Entity);
someBought (Flow);

Behavior (behavior class):

(Behavior, Flow, Class, Role);
Buy (Behavior);

This "aggregations" are part of what I call "Augmentation(s)": Aggregation,
Alignment and Activation are ones of those, which are functional transforms
described declaratively in an object graph metamodel. The act of applying
an Augmentation implies one source Resource (context), one template
Resource (transform) and a resulting (set of) Resource(s).

One also could Augment Resource(s) in a functional manner, using reactive
event driven APIs so, for example applying "Person" class to "Employee"
role could shield a Resource set of people being working for someone. The
ultimate goal is to be able to "plug" as much "backends" connectors as
posible into distributed peers which exposes protocols / APIs for knowledge
driven hypermedia applications.

Best Regards,
Sebastián.


On Sun, Apr 14, 2019, 9:48 PM Paola Di Maio <paola.dimaio@gmail.com> wrote:

> Sebastian
>
> thanks for the post  and for sharing your docs
> I have only briefly glanced through them - working on deadlines all the
> time -
> and it looks interesting.
> I think many of us struggle to be coherent and no, this forum primary goal
> is not  psychoanalysis although many of us could do with some :-)
>
> Sharing thoughts can help us better formulate questions
> \
> I would be grateful if you could explain a bit more of  what you are
> sharing with us, and what kind of input you d like to receive on the docs,
> or explain how these can contribute to the mission
>
> thank you,
>
> PDM
>
>
>
> On Fri, Apr 12, 2019 at 2:43 AM Sebastian Samaruga <ssamarug@gmail.com>
> wrote:
>
>> Sorry if I dare to post my spare thoughts again in this lists. I
>> apologize but it is in the hope of sharing what comes into my writings
>> trying to look for someone with more knowledge to "validate" or to "guide"
>> my points of view.
>>
>> Going through my most recent attempts of having something concrete for
>> sharing in plain English I realize one mistake I'm committing: I'm trying
>> to describe combustion vehicles (Hypermedia Applications) saying that
>> petroleum exists (Semantic Intelligence).
>>
>> As long as my post are going I've just got a stack of (incoherent)
>> "analysis" documents as the result of my work. And I had only those until
>> now because I was stuck because of the previously mentioned mistake (ah,
>> and because of my Bipolar Disease maniac episodes...).
>>
>> So, I should try to describe applications instead and see how and where
>> fuel should burn properly inside a motion vehicle to generate traction.
>> Every semicolon I write is updated into my GitHub repository, so, sorry if
>> you browse that "scrapbook" and you don't find anything even intelligible.
>>
>> https://github.com/snxama/scrapbook/blob/master/Application.docx?raw=true
>>
>> There is a brief technical description work in progress document. For now
>> it just a list of statements about a potential backend. Session and
>> Inteteraction layers are not specified.
>>
>> https://github.com/snxama/scrapbook/blob/master/Index2.docx?raw=true
>>
>> Best Regards,
>> Sebastian Samaruga:
>> http://snxama.blogspot.com
>>
>>

On Sun, Apr 14, 2019, 9:48 PM Paola Di Maio <paola.dimaio@gmail.com> wrote:

> Sebastian
>
> thanks for the post  and for sharing your docs
> I have only briefly glanced through them - working on deadlines all the
> time -
> and it looks interesting.
> I think many of us struggle to be coherent and no, this forum primary goal
> is not  psychoanalysis although many of us could do with some :-)
>
> Sharing thoughts can help us better formulate questions
> \
> I would be grateful if you could explain a bit more of  what you are
> sharing with us, and what kind of input you d like to receive on the docs,
> or explain how these can contribute to the mission
>
> thank you,
>
> PDM
>
>
>
> On Fri, Apr 12, 2019 at 2:43 AM Sebastian Samaruga <ssamarug@gmail.com>
> wrote:
>
>> Sorry if I dare to post my spare thoughts again in this lists. I
>> apologize but it is in the hope of sharing what comes into my writings
>> trying to look for someone with more knowledge to "validate" or to "guide"
>> my points of view.
>>
>> Going through my most recent attempts of having something concrete for
>> sharing in plain English I realize one mistake I'm committing: I'm trying
>> to describe combustion vehicles (Hypermedia Applications) saying that
>> petroleum exists (Semantic Intelligence).
>>
>> As long as my post are going I've just got a stack of (incoherent)
>> "analysis" documents as the result of my work. And I had only those until
>> now because I was stuck because of the previously mentioned mistake (ah,
>> and because of my Bipolar Disease maniac episodes...).
>>
>> So, I should try to describe applications instead and see how and where
>> fuel should burn properly inside a motion vehicle to generate traction.
>> Every semicolon I write is updated into my GitHub repository, so, sorry if
>> you browse that "scrapbook" and you don't find anything even intelligible.
>>
>> https://github.com/snxama/scrapbook/blob/master/Application.docx?raw=true
>>
>> There is a brief technical description work in progress document. For now
>> it just a list of statements about a potential backend. Session and
>> Inteteraction layers are not specified.
>>
>> https://github.com/snxama/scrapbook/blob/master/Index2.docx?raw=true
>>
>> Best Regards,
>> Sebastian Samaruga:
>> http://snxama.blogspot.com
>>
>>