Re: Semantic Web Browser (was: Working draft)

On 15 January 2018 at 02:05, Sebastian Samaruga <ssamarug@gmail.com> wrote:

> Hi,
>
> I'm currently updating my ongoing efforts on building the 'backend' side
> of the coin of a 'Semantic' solution, in this link and attached file. I'm
> focusing on isolating data (resources), schema (templates) and behavior
> (queries) aggregated and / or inferred into RDF quads from current
> applications for being available and published 'semantically' (as services).
>
> https://github.com/CognescentBI/BISemantics/blob/master/TOC.pdf?raw=true
>
> But, what it would be like to have a 'Semantic Web Browser' which
> declaratively renders API frontend / backend interactions, instead of
> having to rely on 'document web' techniques to interface with and render
> service interactions. This link of a previous post gave me a hint:
>
> https://ruben.verborgh.org/blog/2017/12/20/paradigm-
> shifts-for-the-decentralized-web/
>
> But what could be achieved with declarative solutions to the user /
> service interaction 'problem' should be solved in the semantic realm as
> well, giving, perhaps, the freedom for user interfaces (application)
> providers to use some kind of declarative constructs and templating
> language and provide 'branding' to their products using open APIs.
>

Very good idea!  We are thinking along the same lines

Tabulator / mashlib [1] does this.

Example in the wild : https://timbl.com/timbl/Public/Test/

Pro tip: you can drag URIs to the address bar into a new or existing tab.

[1] https://github.com/linkeddata/mashlib


>
> Best regards,
> Sebastián.
>
>
> On Jan 9, 2018 9:17 PM, "Sebastian Samaruga" <ssamarug@gmail.com> wrote:
>
> 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
>>
>
>
>