I'm Andrew and work with RDF-based APIs. I am currently a co-chair of the OSLC project under OASIS: https://open-services.net/. OSLC is a standard that builds on top of W3C LDP (well, actually it's LDP that was built off OSLC; also OSLC Shapes were an initial inspiration for what would later become SHACL) to integrate system engineering tools (think automotive and other industrial domains). I am also a project lead for Eclipse Lyo, an SDK for developing OSLC services using JAX-RS. Jena user. Happy to join the community! I have been following https://gitter.im/linkeddata/chat in the past but chats are not much of my thing. Also been subscribed to email@example.com but it's mostly getting academic ads these days.
Hey Andrew, welcome! Still not much going on here but I hope this will gradually change :)
Great to see you joining, I started reading into OSLC recently and I definitely plan to start using that as well, there is some interest from that side in the Swiss Government. I just had a look at the Lyo side, if I get that correctly I can use that to start documenting the architecture and information model. That sounds pretty much like what we are looking for right now. We build a completely RDF driven data cataloging and documentation system that integrates pretty much any kind of data source. It should become open source as well. What is the status of Lyo, still early stage or used in production already?
I started reading into OSLC recently and I definitely plan to start using that as well, there is some interest from that side in the Swiss Government.
That's great to hear, we are always happy to see more users, especially such large ones. If there are new domains to be covered, you and any interested parties are welcome to join our weekly calls on Thu 16:00 CET.
What is the status of Lyo, still early stage or used in production already?
Regarding Lyo, it is used in production since ca. 2014 (you can see the release table on Eclipse) and we still get requests from users stuck on quite old versions of Lyo in production. It's not web scale yet and recently we've been looking at some performance issues but we have quite a strict policy on breaking changes and take security issues seriously.
if I get that correctly I can use that to start documenting the architecture and information model.
Now, it's important to note that Lyo the framework (mainly to support JAX-RS development of OSLC servers) is different from Lyo Designer the modelling and code generation tool. That tool is going through more rapid development and may introduce breaking changes from time to time. Just to note, everything you model using the tool is stored in accordance to the metamodel. For example, we use that to generate OSLC Shapes (with some user requests to allow generating SHACL shapes instead) from the domain models (@jadelkhoury I think those are really old screenshots that need updating!).
We build a completely RDF driven data cataloging and documentation system that integrates pretty much any kind of data source. It should become open source as well.
This is fantastic! Are you talking about https://zazuko.com/products/ontology-manager/? I took a look around and it seems to have an even lower barrier for RDF modelling than our tool. You can take a look at a typical RDF vocabulary and OSLC shapes modeled with our tool. For now it will require some Eclipse EMF code to work with but we were looking at native RDF export too (right now we produce Java POJOs with Lyo annotations that bridge POJOs and Jena Models).
You may also be interested in OSLC TRS, a persistent log of RDF resource changes, allowing to build event-based systems with Linked Data. Conceptually it's in the same niche as W3C LDN (but persistent) and W3C WebSub (but more focused on creation/modification/deletion of RDF resources directly).