types - Documentation

types

Source:

types.js, line 1

Types is a module containing the three different types: GraphType, EntryType and ResourceType shortened GT, ET and RT.

Members

(static, constant) ET_LINK

Source:

types.js, line 26

See:

Entry#isLink

Link EntryType implies that the resource is not maintained in the repository, rather the entry only provides a link to the resource. The metadata is still maintained in the repository though.

(static) ET_LINKREF

Source:

types.js, line 41

See:

Entry#isLinkReference

Similar to link and reference, only there is both local metadata and external metadata.

(static, constant) ET_LOCAL

Source:

types.js, line 16

See:

Entry#isLocal

Local entrytype implies that the resource is maintained in the repository. It can be an uploaded file, a list, a group, a user etc. The nature of the resource is determined by the graphtype.

(static) ET_REF

Source:

types.js, line 35

See:

Entry#getCachedExternalMetadata
Entry#isReference

Similar to link, only the metadata is also external to the repository. In many cases it is possible to access a locally cached version of the external metadata though.

(static) GT_CONTEXT

Source:

types.js, line 57

See:

Entry#isContext
Context

The resource is a context, i.e. a container for other entries.

(static) GT_GRAPH

Source:

types.js, line 100

See:

Entry#isGraph
Graph

The resource is a RDF graph.

(static) GT_GROUP

Source:

types.js, line 79

See:

Entry#isGroup
Group

The resource is a group.

(static) GT_LIST

Source:

types.js, line 87

See:

Entry#isList
List

The resource is a list.

(static) GT_NONE

Source:

types.js, line 49

See:

Entry#isNone

No graph type specified means that no knowledge of the resources character is known. Hence, no special treatment of the resource is expected. This is common when handling regular files, web resources or abstract entities.

(static) GT_PIPELINE

Source:

types.js, line 114

See:

Entry#isPipeline
Pipeline

The resource is a pipeline, e.g. an entry that can somehow be executed on the server side.

(static) GT_PIPELINERESULT

Source:

types.js, line 122

See:

Entry#isPipelineResult
Pipeline

The resource is a pipelineresult, e.g. the result of the execution of a pipeline on the server side.

(static) GT_RESULTLIST

Source:

types.js, line 93

See:

Entry#isResultList

To Do:

remains to be supported in this API

(static) GT_STRING

Source:

types.js, line 107

See:

Entry#isString
String

The resource is a string.

(static) GT_SYSTEMCONTEXT

Source:

types.js, line 63

See:

Entry#isSystemContext

The resource is one of the special context of this repository, e.g. _contexts or _principals.

(static) GT_USER

Source:

types.js, line 71

See:

Entry#isUser
User

The resource is a user.

(static) RT_INFORMATIONRESOURCE

Source:

types.js, line 129

The resource is available as a digital representation of some sort. Opposite to resources that have no representation, referred to as named.

(static) RT_NAMEDRESOURCE

Source:

types.js, line 141

The resource is not available digitally, i.e. it has now digital representation that can be transferred over a network.

(static) RT_RESOLVABLEINFORMATIONRESOURCE

Source:

types.js, line 135

To Do:

the API has little support for this type currently.

The resource is resolvable to another address.

(static) RT_UNKNOWN

Source:

types.js, line 149

It is unknown if the resource has a representation or not, typically this is the case when large amounts of resources are harvested from another system and it is not feasible to try to load them to check weather they have a digital representation or not. At least the check cannot be done initially and therefore the type is set to unknown.