Re: Status

Thanks and welcome for your greetings!

I apologise but I have one couple of more festive discernments today. It
was a reply from Hans Teijgeler (from 15926.org) that motivated this lines:

It's there something like a "general purpose" tool or framework fear out
there? Or it's an improper word (or name) for something?. It's like selling
sheets of paper which, you say, could be used for writing a novel, a letter
or build a paper plane, being those tools as "generic", for example, as
other general purpose tools, semantic, (upper) ontologies, graph / tuple
oriented stores, etc.

I think the relational model we all know and love would be equally
intimidating in its pure mathematical formalization as are the efforts and
standards of today's semantics community to the rest of the developers
world. It's since that SQL and RDBMS tools exists that all the usefulness
of this model gets evident in the resolution of business use cases.

I think the same could have happened in the beggining with the notion of a
Turing machine, a general purpose machine. And also this could happen
(envision usefulness) with another standard, ISO 13250: Topics Maps, if you
plan to do something useful with it knowing only its Data Model or
Reference Model (both of which can be modelled and rendered in the ways
that I propose and leveraging integration with other types or sources of
knowledge) you may also find it hard in knowing where to begin.

The concepts I'd like and that is my purpose to build something about
someday are in a level compared to that of a sheet of paper, "smart" enough
to help writing novels, letters or making paper planes. And, in respect to
ontologies as a stack of layers it's in the role of a kind of "assembly"
language for integration and knowledge applications.

Someone told me about templates, but tools and layers will be needed, this
is like leveraging an interactive and functional user interface for an
application from source bytes of an XML document: there is storage, then
Unicode, the DTDs / XSDs, services and then transforms and parsing into
some application framework or engine rendering state and interactions on an
application server.

All kind of stuff that can't be done, for example, just with traditional
tools alone (for a traditional application) neither with just the bunch of
semantic standards out there (for a semantic application) not even
mentioning the lack of "semantic" standards industry hasn't for them in
favor of traditional solutions.

So, I mean, my lack of focus in solving a particular problem is that I'd
like to be general purpose enough to enable multiple, diverse domain
applications and purposes solutions to be built upon a common integration
infrastructure and services. It's like we are needing something like a
"SemanticEE" or a "Semantic.NET". Maybe I'm missing something but I'm just
trying to envision the building blocks ("assembly" / "virtual machine")
language for such a "Computable Semantic Web".

There are OGMs (Object Graph Mapping) tools and that's the kind of general
purpose components I'd like to provide. As an example a declarative Domain
Driven Development MVC framework such as Apache Isis[1], enhanced for
semantic backends, could be a top down solution in some environment
providing the necessary semantic services (such as an OGM instead of ORM)
for building elementary apps.

[1]: http://isis.apache.org/

Best Regards and Happy Holydays!

Sebastián.
http://snxama.blogspot.com
http://github.com/snxama/scrapbook


On Mon, Dec 23, 2019, 7:39 AM Amirouche Boubekki <
amirouche.boubekki@gmail.com> wrote:

> Le lun. 23 déc. 2019 à 07:33, Paola Di Maio <paola.dimaio@gmail..com> a
> écrit :
> >
> > Happy Holidays, Sebastian and everyone
> >
>
> +1
>
> > On Sun, Dec 22, 2019 at 8:28 AM Sebastian Samaruga <ssamarug@gmail.com>
> wrote:
> >>
> >> [The PragmaticWeb Research List]
> >> Hi. Having bothered a lot of times with my speculations regarding
> specifications and applications, this time I'll try to recap some status
> and, by the way, to wish everyone a happy holidays...
> >>
> >> Being just a bare Java / Web developer, mildly seasoned into the
> habitual frameworks and stacks for such platforms, I can no more than say
> that I'm obsessed with Semantic Web and, specifically, with its application
> in the fields of integration and declarative applications development.
> >>
> >> Sadly, for an aged, high school degree, bipolar disease diagnosed
> patient, I currently cannot "make my point" in the documentation I do
> regarding my work. I usually transcribe a couple of pages from my drafts
> weekly, thinking I've put in clear text some "important concepts". Then,
> later, not even myself can understand what I wrote. This "iterations" comes
> a long long way ago (aprox. since 2004). Apologizes for that.
> >>
> >> This "project" of mine, and all my attempts of specifying something may
> seem delirious, including for myself. But I'd really be glad if the
> opportunity comes and I'll be able to work on this kind of stuff seriously.
> Let me say that I didn't find any local job position regarding this field..
> >>
> >> That said, let me describe the sort of "solution" I do envision could
> be built. Let me say I lack of the previous knowledge necessary for
> building what my "intuition" thinks could be done (math, category theory,
> type theory, etc.). So I really gonna need some help for validation (or
> auditing) of whatever I've have done or to see if I'm in the correct path:
> >>
> >> Semantic / Knowledge enabled ESB (Enterprise Service Bus) solution bus
> addressing:
> >>
> >> Plugin of diverse applications, services and data sources for the
> setting of a syndication and virtualization layer via augmenting and
> matching plugged contexts with each other's data, information and knowledge
> by means of ontologies and semantics techniques.
> >>
> >> Render a SOA (Service Oriented Architecture) aggregating data, schema
> and behavior of plugged / connected sources in a declarative and
> discoverable manner: REST HATEOAS[1], HAL[2].
> >>
> >> Interactions involving more than one data source / backend (ERPs, CRMs,
> SCMs, BI / BigData / ML Pipelines or in-house applications) data or updates
> are view as a single operation over the corresponding consolidated entities
> and the services architecture expose a composite of interrelated use cases
> of the underlying aggregated back ends. Domains alignments may involve
> check preconditions or performing actions involving a (distributed)
> transaction.
> >>
> >> Solution Semantic features:
> >>
> >> Ontology Matching:
> >> For the interaction and syndication of different systems is necessary
> to be able to distinguish whether references to some data, schema or
> behavior refers to the same "entity".
> >>
> >> Alignment / Inference:
> >> Once ontology matching aligns equivalent entities there left to regard
> where, with some built "metamodel", which entities left to be "augmented"
> via ontologies, semantics, aggregation and Machine Learning.
> >>
> >> Activation / Dataflow:
> >> Implied behaviors. Given some "metamodel", reactive behavior is encoded
> and materialized according some sort of functional protocol interactions:
> streams, request / response Dataflow[3].
> >>
> >> So, for example, interactions in the (declaratively stated use cases)
> exposed and consumed functionally, are driven by a series of "descriptors"
> (as in [1] and [2]) maybe following a declarative approach of actors and
> roles like in DCI (Data, Context and Interactions)[4]. Thus, source models
> reflects this "facade" operations.
> >>
> >> References:
> >> [1]: https://en.m.wikipedia.org/wiki/HATEOAS
> >> [2]: https://en.m.wikipedia.org/wiki/Hypertext_Application_Language
> >> [3]: https://en.m.wikipedia.org/wiki/Dataflow
> >> [4]: https://en.m.wikipedia.org/wiki/Data,_context_and_interaction
> >>
> >> https://snxama.blogspot.com
> >> https://github.com/snxama/scrapbook
> >>
> >> Best Regards and Happy Holidays!
> >> Sebastián.
> >>
> >> _______________________________________________
> >> PragmaticWeb mailing list
> >> PragmaticWeb@lists.spline.inf.fu-berlin.de
> >> https://lists.spline.inf.fu-berlin.de/mailman/listinfo/pragmaticweb
>
>
>
> --
> Amirouche ~ https://hyper.dev
>

Received on Tuesday, 24 December 2019 23:34:12 UTC