W3C home > Mailing lists > Public > semantic-web@w3.org > January 2018

Semantic Web Browser (was: Working draft)

From: Sebastian Samaruga <ssamarug@gmail.com>
Date: Sun, 14 Jan 2018 22:05:08 -0300
Message-ID: <CAOLUXBssSxJMiGq=9E=6s-_NhSCOruqAsRBHOE7-EJdo+XLNUQ@mail.gmail.com>
To: W3C Semantic Web IG <semantic-web@w3.org>, public-rww <public-rww@w3.org>, DBpedia <Dbpedia-discussion@lists.sourceforge.net>, pragmaticweb@lists.spline.inf.fu-berlin.de

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)..


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:


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.

Best regards,

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..


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.



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

Received on Monday, 15 January 2018 01:06:36 UTC

This archive was generated by hypermail 2.3.1 : Monday, 15 January 2018 01:06:44 UTC