Last edited 5 months ago
by Serena Cericola

ShareDoc:PublicDocumentation: Difference between revisions

No edit summary
No edit summary
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{DISPLAYTITLE:Public Documentation}}
{{DISPLAYTITLE:Public Documentation}}


== [https://wiki.share-vde.org/wiki/ShareDoc:PublicDocumentation/Main_technological_components Main technological components] ==
== [https://wiki.share-vde.org/wiki/ShareDoc:PublicDocumentation/LODPlatform The LOD Platform technology] ==
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 '''[[ShareDoc:PublicDocumentation/LODPlatform|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, including [[ShareDoc:PublicDocumentation/LODPlatform/EntityEditor|'''JCricket Entity Editor and Shared Cataloguing Tool''']].


== [https://wiki.share-vde.org/wiki/ShareDoc:PublicDocumentation/User_guides User guides] ==
== [https://wiki.share-vde.org/wiki/ShareDoc:PublicDocumentation/User_guides User guides] ==
Line 11: Line 11:


== [https://wiki.share-vde.org/wiki/ShareDoc:PublicDocumentation/APIs Share Family API: Technical documentation] ==
== [https://wiki.share-vde.org/wiki/ShareDoc:PublicDocumentation/APIs Share Family API: Technical documentation] ==
This is a collection of Share Family API.
This is a collection of Share Family APIs.


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).
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). 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).

Latest revision as of 13:40, 30 May 2024


The LOD Platform technology

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, including JCricket Entity Editor and Shared Cataloguing Tool.

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.

Share Family API: Technical documentation

This is a collection of Share Family APIs.

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). 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).