Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Examples on Principle 8 #30

Open
giovannidegani opened this issue Aug 16, 2024 · 3 comments
Open

Examples on Principle 8 #30

giovannidegani opened this issue Aug 16, 2024 · 3 comments
Assignees
Labels
principle 8 Principe 8: Control

Comments

@giovannidegani
Copy link

Is there any more recommended literature on principle 8 around control ?

I would love to understand how that could be implemented in practice and some best practices around it

@jgeluk
Copy link
Member

jgeluk commented Aug 16, 2024

Hi Giovanni, very good question thank you.

Control comes in many forms. In we use the EKG Maturity Model as a guiding framework (https://maturiy.ekgf.org) to define "maturity levels" (i.e. levels of expectation), then at the lower levels, the average Knowledge Graph (let alone an Enterprise Knowledge Graph) will not provide much control beyond access control at the SPARQL endpoint and/or at the UI endpoint.

However, at higher levels of maturity one would expect more advanced levels of control in various areas, not only access control (advanced context-specific entitlement computation) but also controls for regulatory compliance or "policy enforcement". Those types of control can (in my opinion), at least at enterprise scale, only be enabled and enforced by having a smart EKG architecture that has a service layer that sits in front of all your backend sources, not only semantic graph databases aka triplestores but any other type of source as well, they can all provide their piece of the overall Enterprise Knowledge Graph.

That service layer is one of the topics that we're discussing in the EKGF community. We will soon start with a new workgroup called "EKGF Architecture Workgroup" which will discuss exactly that service layer and its requirements. So far every EKG project I've been involved in over the years builds their own equivalent of that service layer. It's time for standardisation and vendor products.

Cheers
Jacobus Geluk
Co-chair EKGF (see https://www.omg.org/communities/enterprise-knowledge-graph-forum.htm)

@jgeluk
Copy link
Member

jgeluk commented Aug 16, 2024

If you mail me at [email protected] I can send you a draft document that explains that EKG architecture.

@giovannidegani
Copy link
Author

thanks @jgeluk , I've sent you an e-mail 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
principle 8 Principe 8: Control
Projects
None yet
Development

No branches or pull requests

6 participants