Re: Working draft

Minor updates. Left to be defined three 'alignment' methods / models, one
over plain statements (Resources), over resource types / kinds statements
(Templates) and over aggregated types of Template kinds (Queries). All of
those providing model activation, entity / record identity matching /
merge, links and attributes augmentation / resolution and order in contexts
(i.e.: causal relationship) in an uniform model based messaging interchange.

Best,
Sebastián.


On Jan 8, 2018 8:37 AM, "Sebastian Samaruga" <ssamarug@gmail.com> wrote:

This is an effort on making the previous document clearer. It is far from
complete, but it focuses on implementation patterns I'll follow when I
finally get the way of building some code.

https://github.com/CognescentBI/BISemantics/blob/master/TOC.pdf?raw=true

Regards,
Sebastian.

On Dec 25, 2017 11:34 AM, "Sebastian Samaruga" <ssamarug@gmail.com> wrote:

> By now I only could state here my 'intentions' in respect to 'patterns'
> I'd like to use in a functional integration model. I'll try that my next
> post point to some working piece of code.
>
> I think I've found the way of performing functional / declarative C(R)UD
> by means of query models resolution patterns (inspired by a previous blog
> post in this list: "Paradigm shifts for the decentralized Web") for the
> approach of 'decentralizing' model integrations I'm trying to build.
>
> Sorry again for the lack of 'code'. I'm just trying to 'dump' what I'd
> like to do as an analysis document while I gather the resources for
> building something functional:
>
> Basically the idea is to functionally 'homogenize' data sources: their
> data, schemas and (inferred) 'behaviors' (flows / transforms / processes).
> By means of semantic aggregation into layers and three 'alignment' models
> of sources (identity of records / entities without common keys via class /
> metaclass abstractions, resolution of missing relations / attributes and
> contextual 'sorting': for example cause / effect in a process events
> context) one should obtain:
>
> 1. An homogeneous (functional) metamodel of data and schema (Resources).
> Like an XML document.
>
> 2. An homogeneous (functional) metamodel of entailed 'processes'
> (transforms / flows) and the behaviors they entails (integration of, for
> example, action / flow A in origin X entails action / flow B in origin Y).
> Resembles an XSL transform. Templates extracted from 'kinds' (basic form of
> type inference).
>
> The grace resides in that those metamodel being obtained, aggregated and
> aligned from raw data (an RDF dump of a database, for example) and then to
> parse simultaneously Template inferred 'code' applied to their
> corresponding 'data' Resources and to obtain resulting metamodels.
>
> So, aggregate and align diverse data sources in homogeneous structures
> which provides Templates (code / flow / transforms) which applies over
> Resources (data) when they have determinate structure or 'shapes'.
>
> Apologizes for the quality of attached documents. Regards,
>
> Sebastián.
>
> https://github.com/CognescentBI/BISemantics/blob/master/Spec
> ification.pdf?raw=true
>