I

IAM (Identity and Access Management)

Cloud. AWS Identity and Access Management (IAM) is a web service that enables you to manage users and user permissions in AWS. With IAM, you can centrally manage users, security credentials such as access keys, and permissions that control access to AWS resources. For details, see IAM Roles for Amazon EC2.

IDP

See Identity Provider

Identity Provider (IDP)

Security. A server that authenticates and authorizes users then allows them to securely access its resources.

indexable path

MarkLogic. A path expression, limited to the subset of XML Path language (XPath) that can be used to define a path range index. See also Path Field and Path-Based Range Index Configuration in the XQuery and XSLT Reference Guide.

indexes for text and structure

Database. MarkLogic Server search supports a wide range of full-text features. These features include phrase search, boolean search, proximity, stemming, tokenization, decompounding, wildcarded searches, punctuation-sensitive search, diacritic-sensitive/insensitive searches, case-sensitive/insensitive searches, spelling correction functions, thesaurus functions, geospatial searches, advanced language and collation support, document quality settings, numerous relevance algorithms, individual term weighting, topic clustering, faceted navigation, custom-indexed fields, and much more. These features are all designed to build off of each other and work together in an extensible and flexible way.

inference

Semantics. You can do inference manually as part of an inference query or automatically using an inference engine. Given a set of data as triples and a set of rules (such as a ruleset), you can derive or discover new relationships and new facts. Inference can be done at query time (for each query, look at the data and ontology and ruleset(s), and expand the query appropriately), or at index time (on ingestion/index create new inferred triples). Whether the new relationships are explicitly added to the set of data, are returned at query time, or just influence the results, is an implementation issue. See forward-chaining inference, backward-chaining inference, and inferencing.

inference engine

Semantics. Software that performs inference. An inference engine may also be referred to as a reasoning engine, a reasoner, a semantic reasoner, or a rules engine.

inference query

Semantics. An inference query is any query (SPARQL, XQuery, JavaScript) that is affected by inference (that is, affected by some ruleset).

inference rule

Semantics. A rule that defines a set of triples to be inferred by some set of asserted triples, ontology triples, triples, and rulesets. You must have a ruleset to do inferencing.

inferencing

Semantics. Inferencing is the process of discovering new facts and relationships in your data using triples, an ontology, and ruleset(s). Inferencing can be done manually as part of an inference query, or automatically using an inference engine. See inference.

inferred triples

Semantics. In a system that does forward-chaining inference (a system that materializes new triples inferred from existing triples), inferred triples are those triples created by that inferencing. See also asserted triples and backward-chaining inference.

Ingestion

MarkLogic. The Data Hub (DH) process that uses an input flow to pull documents into the data hub.

Input flow

MarkLogic. The type of flow that processes each incoming document before it is written into MarkLogic. Input flows are invoked by MarkLogic content pump (mlcp), the Java Client API, or the REST Client API. See envelope pattern and “Envelope Pattern - Input Flows” in the Data Hub documentation.

input query

MarkLogic. When using MarkLogic Server as an input source, the query that generates input key-value pairs from the fragments/records in the input split.

input source

MarkLogic. A database, file system, or other system that provides input to a job. For example, a MarkLogic Server instance or Hadoop Distributed File System (HDFS) can be used as an input source.

input split

MarkLogic. The subset of the input data set assigned to a map task for processing. Split generation is controlled by the InputFormat subclass and configuration properties of a job.

input split query

MarkLogic. When using MarkLogic Server as an input source , the query that determines which content to include in each split. By default, the split query is built in. In advanced input mode, the split query is part of the job configuration.

InputFormat

Hadoop. The abstract superclass, org.apache.hadoop.mapreduce.InputFormat, of classes through which input splits and input key-value pairs are created for map tasks. The Apache Hadoop MapReduce API includes InputFormat subclasses for using HDFS as an input source. The MarkLogic Connector for Hadoop API provides InputFormat subclasses for using MarkLogic Server as an input source.

Instance

Cloud. The running system after an Amazon Machine Image (AMI) is launched. Instances remain running unless they fail or are terminated. When this happens, the data on the instance is no longer available. Once launched, an instance looks very much like a traditional host.

Instance Store (sometimes referred to as Ephemeral Storage)

Cloud. A fixed amount of storage space for an instance. An instance store is not designed to be a permanent storage solution. If an instance reboots, either intentionally or unintentionally, the data on the instance store will survive. If the underlying drive fails or the instance is terminated, the data will be lost.

Instance Type

Cloud. Defines the size of an Elastic Compute Cloud (EC2) instance. The MarkLogic Server instance types are shown in the table at the end of Step 5 in Creating a CloudFormation Stack using the AWS Console in MarkLogic Server on Amazon Web Services (AWS).

interpretive rewriter

HTTP server. An implementation of a “rewriter” that is specified in an interpreted language, like JavaScript or XQuery.

IRI (Internationalized Resource Identifier)

Web. An IRI is a compact string that is used for uniquely identifying resources in an RDF triple. IRIs may contain characters from the Universal Character Set (Unicode/ISO 10646), including Chinese or Japanese Kanji, Korean, Cyrillic characters, and so on. See also Uniform Resource Identifier (URI), Uniform Resource Locator (URL), and Uniform Resource Name (URN).