No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:Public Documentation}} | {{DISPLAYTITLE:Public Documentation}} | ||
== [ | == <u>[https://wiki.share-vde.org/wiki/ShareDoc:PublicDocumentation/Main_technological_components Main technological components]</u> == | ||
This section serves as a gateway to a comprehensive breakdown of key technological components that form the backbone of the LOD Platform. the technology that powers the Share Family system. This section provides an overview of crucial components and concepts integral to understanding the inner workings of our platform. | This section serves as a gateway to a comprehensive breakdown of key technological components that form the backbone of the LOD Platform. the technology that powers the Share Family system. This section provides an overview of crucial components and concepts integral to understanding the inner workings of our platform. | ||
Revision as of 15:25, 6 March 2024
Main technological components
This section serves as a gateway to a comprehensive breakdown of key technological components that form the backbone of the LOD Platform. the technology that powers the Share Family system. This section provides an overview of crucial components and concepts integral to understanding the inner workings of our platform.
User guides
Here you'll find user guides describing the LOD Platform and JCricket entity editor.
Release notes
This page gathers the release notes of the technical implementations.
This is a collection of Share Family API.
This technical documentation is valid for all tenants of the Share Family. However, in the documentation pages you will find examples showing only the namespace "svde.org". If your institution belongs to a tenant that is not svde.org, you have to run queries using the specific namespace of your tenant (e.g. natbib-lod.org, or pcc-lod.org, or kubikat-lod.org). Please remember to replace the namespace "svde.org" that appears in the examples with the namespace of your tenant (both for entity URIs and for attributes/properties URIs).
