Re: Is this feasible?

Dear Sebastian,
If the intended use is for business intelligence and use of universal digital dashboards I am interested. Get back to me offline.

Milton Ponson
GSM: +297 747 8280
PO Box 1154, Oranjestad
Aruba, Dutch Caribbean
Project Paradigm: A structured approach to bringing the tools for sustainable development to all stakeholders worldwide through collaborative research on applied mathematics, advanced modeling and creating ICT tools for development

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. 

    On Monday, September 26, 2016 1:20 AM, Sebastian Samaruga <ssamarug@gmail.com> wrote:
 

 Hi all, looking to see if what I've been thinking is feasible or even worth working on...What I'm currently working in what could be the end of the analysis phase of a project I've been in. It comprises basically of the following:1) Import RDFized data from heterogeneous data sources. Sync data sources with operations in the model.2) Nodes (peers) deployment architecture loaded with the data from each sources, share an Unified URI space (for aligned resources and triples). Functional API for augmentation, discovery and analysis.3) Type (classes) / relationship types, relationship instances / state flows (operations, rules, flows, events) inference over ‘raw’ RDF data from data sources.4) Align & Merge. Equivalent resources / triples from different ontologies merged according their meaning. Model by example.5) Order inference: inference over the order of events / operations occurred, occurring and that may occur according metadata aggregated from data sources. Enforce use case flows declaratively (model by example)6) Uniform API Ports: CRUD bindings to common protocols as REST (HATEOAS / OData), SOAP, LDP (Solid) and others.About (6) I know there are similarities with Solid / LDP and I'm considering to build over that implementations.What I'm basically looking forward is to have as much comments as possible if someone is willing to help me regarding the draft of the spec I'm currently sending as an attachment. There is also a Google doc if someone is interested in collaborating in this (rather incomplete) draft.I know this may look like a dump of (incomplete) ideas into paper. My main problems are my lack of experience in this kind of projects and lack of peers with which to be able to review the work done yet. So that's why I'm bothering you in this lists. Apologizes for that but I would like some kind of feedback for orientating myself into this journey.Regards,
Sebastián.


   

Received on Thursday, 29 September 2016 18:46:04 UTC