Last edited 6 days ago
by Anna Lionetti

ShareDoc:PublicDocumentation: Difference between revisions

mNo edit summary
No edit summary
Line 5: Line 5:


== [[ShareDoc:PublicDocumentation/User guides|User guides]] ==
== [[ShareDoc:PublicDocumentation/User guides|User guides]] ==
* [https://wiki.share-vde.org/wiki/ShareDoc:LOD-PlatformUXguide LOD Platform UX guide]: user guide for the LOD Platform entity discovery web interface (aka “discovery portal”)
Here you'll find user guides describing the LOD Platofrm and JCricket entity editor.
* [https://wiki.share-vde.org/wiki/ShareDoc:JCricketGuide JCricket UX guide]: user guide for the JCricket entity editor


== [[ShareDoc:PublicDocumentation/Release notes|Release notes]] ==
== [[ShareDoc:PublicDocumentation/Release notes|Release notes]] ==
This page gathers the release notes of the technical implementations.
This page gathers the release notes of the technical implementations.


== [[ShareDoc:PublicDocumentation/APIs|Share-VDE API: Technical documentation]] ==
== [[ShareDoc:PublicDocumentation/APIs|Share Family API: Technical documentation]] ==
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).
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).
=== General ===
* [[ShareDoc:Domain Model|The Share-VDE Domain Model]]
* [[ShareDoc:The PostMan Collection|How to import the Share-VDE API Collection]]
* [[ShareDoc:API documentation|Share-VDE API: cross-cutting concepts]]
* [[ShareDoc:Auth|Share-VDE API: Authentication]]
* [[ShareDoc:Query Languages|Share-VDE API: Query Languages]]
* [[ShareDoc:Simple Search|Share-VDE API: Simple Search]]
=== REST ===
* [[ShareDoc:RESTFul API|Share-VDE REST API]]
* [[ShareDoc:ShareVDEAndTheSemanticWeb|Share-VDE and the Semantic Web]]
* [[ShareDoc:Content Negotiation|Share-VDE REST API: Content Negotiation]]
=== GraphQL ===
* [[ShareDoc:GraphQL API|Share-VDE GraphQL API]]
* [[ShareDoc:Subject API|Share-VDE GraphQL API: Subjects]]

Revision as of 08:41, 22 February 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 Platofrm 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 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).