> On 22 Mar 2024, at 18:53, Maatary Okouya <[email protected]> wrote: > > >> There is no single best practice for deployment. It depends on who is > >> responsible for what, the skills of the team, how many are on the > >> ontogists team, are external staff often used, how often ontologies need > >> to change, how tightly controlled/regulated the organization is, etc. > > We have currently 2 experts ontologist working on models on studio and > collaborating via Git. Our goal is simply to upload the work of the > ontologist as frequently as necessary to EDG Server, and have developers and > product owners consult the only. It support data contract discussion between > all the parties involved in the project. Ideally we wanted to go through git > integration, but it seems that it does not work since the File Asset Type has > been removed from EDG Server. Would have been nice to keep it as read only at > least. From what i have red online, it seems we only have the manual upload > possible as in extra step but git push. But we are not sure here exactly what > are the exact steps to follow. > > No external staff, the ontology currently is in active development, but very > soon about to settle and expected to change not that frequently. In term of > control/regulation, we are establishing the practice at the moment. s,
Seems like using Server Admin, Project Upload when your team gets to a “stable release” would work. Here’s a process we use for some customers that works for us: make a folder in git called something like myontologies.topbraidlive.org <http://myontologies.topbraidlive.org/> (call it what you want but adopt a convention and follow it) put your TTLs in the folder making sure they have rdf:type owl;Ontology statements zip the folder when ready to deploy to server Project Upload (from then on I usually use a the “Delete old project option and always completely replace everything, but that’s up to you, update is available) Settings, Includes will now show your ontologies under the “Other” category. That said, with two ontologist it see like just using the EDG server and workflows would work for your situation. Your two experts can share workflows and test them before committing them to the production copy allowing the “users” to see the result. Workflows are not 100% equivalent of git branches, but not a million miles away. If you are using git as a kind of backup or as shared corporate knowledge, then after the commit the ontologist can just Export RDF sorted TTL and update the git repo. Cheers, David > > On Friday, March 22, 2024 at 6:25:54 PM UTC David Price wrote: >> >>> On 22 Mar 2024, at 16:49, Maatary Okouya <[email protected] <>> wrote: >>> >>> >>> | Collections *are* the "user data” created and changed by users of an EDG >>> server, assuming they have the right role/permissions. >>> Ok, then in that logic, why would a user be allowed to create a collection >>> of type ontology ? This feels more like a software system by your >>> definition. They should only be able to create instance data no? Instance >>> of ontology or simply taxonomy. But i can also understand that as the >>> technology itself, difference between instance data and schema data can be >>> blur sometime. >> >> If an EDG user is an ontologist, then classes and properties are user data >> (i.e. data created by an EDG user). >> >> Sometimes an ontology is the end product for some EDG users. >> >> Sometimes the ontologies are used by a different set of EDG users to create >> instances in a Data Graph, for example. >> >> EDG is flexible … and the EDG UI is almost all "model-driven” driven by the >> fact that ontologies are also a kind of data. >> >>> The all workflow thingy, feels to me like collaborative ontology editing. >> >> Workflows are for editing anything in EDG collections, not just ontologies. >> >>> >>> In any case at this point, I would like to be able to deploy the ontologies >>> we create with EDG Studio to EDG Server, not for user to edit user data (on >>> top of it), but simply to consult the ontologies. What the best workflow >>> for that ? doesn't the Git integration enable that ? >> >> There is no single best practice for deployment. It depends on who is >> responsible for what, the skills of the team, how many are on the ontogists >> team, are external staff often used, how often ontologies need to change, >> how tightly controlled/regulated the organization is, etc. >> >> Cheers, >> David >> >> >>> >>> On Sunday, March 10, 2024 at 11:10:13 AM UTC Maatary Okouya wrote: >>>> Understood. thank you >>>> >>>> On Sunday, March 10, 2024 at 9:45:04 AM UTC David Price wrote: >>>>> >>>>>> On 10 Mar 2024, at 06:35, Maatary Okouya <[email protected] <>> wrote: >>>>>> >>>>>> Then what is really the rational for having files and collection ? I >>>>>> work with studio mostly, Files are perfect for me. I just want to make >>>>>> sure that i fully graps the philosophy here. Files did not exist in >>>>>> previous version, why was it added ? >>>>> >>>>> Put simply, Studio/Files is how developers/ontologists deliver a software >>>>> system, and Collections are how users create and manage data using that >>>>> software system. >>>>> >>>>> Studio was built for EDG server-supporting developers, ontologists, etc. >>>>> who need to build and test ontologies, scripts, etc. before they get >>>>> deployed to an EDG server as a “project” for use by the users of that EDG >>>>> server. >>>>> >>>>> Files is a feature for those developers that understands SPARQL, SHACL, >>>>> etc. and so is better than using an external source code editor on TTL >>>>> files, for example. Files is not intended to be a feature available on >>>>> operational EDG servers due to security and system support/uptime risks. >>>>> >>>>> >>>>> The graphs deployed to an EDG server as a “project” are not “user data” >>>>> so we don’t want users changing them. >>>>> >>>>> Collections *are* the "user data” created and changed by users of an EDG >>>>> server, assuming they have the right role/permissions. >>>>> >>>>> Cheers, >>>>> David >>>>> >>>>> UK +44 (0) 7788 561308 <tel:+44%207788%20561308> >>>>> US +1 (336) 283-0808 <tel:(336)%20283-0808> >>>>> >>>>>> >>>>>> On Saturday, March 9, 2024 at 3:15:12 PM UTC David Price wrote: >>>>>>> “wrapping” files is not a good way to think about this. The EDG >>>>>>> behaviour between collections and files is normal owl:imports. >>>>>>> >>>>>>> EDG Files contain a named graph. So do collections, and collections can >>>>>>> include (i.e. owl:imports) a graph that happens to be in a file or a >>>>>>> collection. >>>>>>> >>>>>>> If you change graph in a File at any point in time, then those changes >>>>>>> are visible immediately in all including collections (accepting that >>>>>>> caches may need to be refreshed for any currently in-use collections >>>>>>> via a page reload for example). >>>>>>> >>>>>>> FYI there are a few “special” files in EDG - api.ttl files contents are >>>>>>> made visible via a software mechanism rather than owl:imports. These >>>>>>> usually contain SPARQL Functions, for example, which are really >>>>>>> “software” not "data model” or “data”. See >>>>>>> >>>>>>> https://archive.topquadrant.com/doc/latest/ext/process.html#working-with-extension-files >>>>>>> >>>>>>> which is part of >>>>>>> >>>>>>> https://archive.topquadrant.com/doc/latest/ext/index.html >>>>>>> >>>>>>> Cheers, >>>>>>> David >>>>>>> >>>>>>> UK +44 (0) 7788 561308 <tel:+44%207788%20561308> >>>>>>> US +1 (336) 283-0808 <tel:(336)%20283-0808> >>>>>>> >>>>>>> >>>>>>>> On 9 Mar 2024, at 14:29, Maatary Okouya <[email protected] <>> wrote: >>>>>>>> >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> When wrapping Files, into EDG Collection. Does it become a completely >>>>>>>> separate entity e.g. ontology, or the two can be kept in sync, as in >>>>>>>> what change on files is propagate to the ontology wrapped ? >>>>>>>> >>>>>>>> I guess my question is about understanding the intended behavior >>>>>>>> >>>>>>> >>>>>>>> -- >>>>>>>> The topics of this mailing list include TopBraid EDG and related >>>>>>>> technologies such as SHACL. >>>>>>>> To post to this group, send email to [email protected] <> >>>>>>>> --- >>>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "TopBraid Suite Users" group. >>>>>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>>>>> an email to [email protected] <>. >>>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/msgid/topbraid-users/80f75b5d-564c-4c2b-ae3e-923be77f3a8an%40googlegroups.com >>>>>>>> >>>>>>>> <https://groups.google.com/d/msgid/topbraid-users/80f75b5d-564c-4c2b-ae3e-923be77f3a8an%40googlegroups.com?utm_medium=email&utm_source=footer>. >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> The topics of this mailing list include TopBraid EDG and related >>>>>> technologies such as SHACL. >>>>>> To post to this group, send email to [email protected] <> >>>>>> --- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "TopBraid Suite Users" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>>> an email to [email protected] <>. >>>>> >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/topbraid-users/188d2eea-dd43-479a-b646-eba1ac4a4452n%40googlegroups.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/topbraid-users/188d2eea-dd43-479a-b646-eba1ac4a4452n%40googlegroups.com?utm_medium=email&utm_source=footer>. >>>>> >>> >>> >>> -- >>> The topics of this mailing list include TopBraid EDG and related >>> technologies such as SHACL. >>> To post to this group, send email to [email protected] <> >>> --- >>> You received this message because you are subscribed to the Google Groups >>> "TopBraid Suite Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected] <>. >> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/topbraid-users/0fce4b0b-295a-431f-b07a-5de98c5bcc8bn%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/topbraid-users/0fce4b0b-295a-431f-b07a-5de98c5bcc8bn%40googlegroups.com?utm_medium=email&utm_source=footer>. >> >> >> UK +44 (0) 7788 561308 <tel:+44%207788%20561308> >> US +1 (336) 283-0808 <tel:(336)%20283-0808> >> > > > -- > The topics of this mailing list include TopBraid EDG and related technologies > such as SHACL. > To post to this group, send email to [email protected] > --- > You received this message because you are subscribed to the Google Groups > "TopBraid Suite Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/35dc24c3-dcc9-4a8d-8c4d-b78d72e5fa91n%40googlegroups.com > > <https://groups.google.com/d/msgid/topbraid-users/35dc24c3-dcc9-4a8d-8c4d-b78d72e5fa91n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- The topics of this mailing list include TopBraid EDG and related technologies such as SHACL. To post to this group, send email to [email protected] --- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/1F9C52AA-497F-48C9-BD37-BD8C79B41EF2%40topquadrant.com.
