types

Members

(static, constant) ET_LINK

Description:

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

Source:

• types.js, line 26

See:

• Entry#isLink

(static) ET_LINKREF

Description:

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

Source:

• types.js, line 41

See:

• Entry#isLinkReference

(static, constant) ET_LOCAL

Description:

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

Source:

• types.js, line 16

See:

• Entry#isLocal

(static) ET_REF

Description:

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

Source:

• types.js, line 35

See:

• Entry#getCachedExternalMetadata
• Entry#isReference

(static) GT_CONTEXT

Description:

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

Source:

• types.js, line 57

See:

• Entry#isContext
• Context

(static) GT_GRAPH

Description:

• The resource is a RDF graph.

Source:

• types.js, line 100

See:

• Entry#isGraph
• Graph

(static) GT_GROUP

Description:

• The resource is a group.

Source:

• types.js, line 79

See:

• Entry#isGroup
• Group

(static) GT_LIST

Description:

• The resource is a list.

Source:

• types.js, line 87

See:

• Entry#isList
• List

(static) GT_NONE

Description:

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

Source:

• types.js, line 49

See:

• Entry#isNone

(static) GT_PIPELINE

Description:

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

Source:

• types.js, line 114

See:

• Entry#isPipeline
• Pipeline

(static) GT_PIPELINERESULT

Description:

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

Source:

• types.js, line 122

See:

• Entry#isPipelineResult
• Pipeline

(static) GT_RESULTLIST

Source:

• types.js, line 93

See:

• Entry#isResultList

To Do:

• remains to be supported in this API

(static) GT_STRING

Description:

• The resource is a string.

Source:

• types.js, line 107

See:

• Entry#isString
• String

(static) GT_SYSTEMCONTEXT

Description:

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

Source:

• types.js, line 63

See:

• Entry#isSystemContext

(static) GT_USER

Description:

• The resource is a user.

Source:

• types.js, line 71

See:

• Entry#isUser
• User

(static) RT_INFORMATIONRESOURCE

Description:

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

Source:

• types.js, line 129

(static) RT_NAMEDRESOURCE

Description:

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

Source:

• types.js, line 141

(static) RT_RESOLVABLEINFORMATIONRESOURCE

Description:

• The resource is resolvable to another address.

Source:

• types.js, line 135

To Do:

• the API has little support for this type currently.

(static) RT_UNKNOWN

Description:

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

Source:

• types.js, line 149