Event

Caliper Event

  • @context
    enum
    const:  
    http://purl.imsglobal.org/ctx/caliper/v1p2
    required
    values
    • http://purl.imsglobal.org/ctx/caliper/v1p2
  • action
    Type: stringenum
    required
    values
    • Abandoned
    • Accepted
    • Activated
    • Added
    • Archived
  • actor
    required

    Base type for all Caliper entities

    • id
      required

      An IRI can be either:

      1. A URI (any valid URI scheme)
      2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
      • Type: string Pattern: ^[a-z][a-z0-9+.-]*:Format: url

        An IRI can be either:

        1. A URI (any valid URI scheme)
        2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
    • type
      Type: stringenum
      required
      values
      • Entity
      • Agent
      • Person
      • SoftwareApplication
      • Organization
    • dateCreated
      Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

      the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

    • dateModified
      Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

      the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

    • description
      Type: string
    • extensions
      Type: object
    • name
      Type: string
    • otherIdentifiers
      Type: array
  • eventTime
    Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time
    required

    the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

  • id
    required

    An IRI can be either:

    1. A URI (any valid URI scheme)
    2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
    • Type: string Pattern: ^[a-z][a-z0-9+.-]*:Format: url

      An IRI can be either:

      1. A URI (any valid URI scheme)
      2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
  • object
    required

    • Base type for all Caliper entities

      • id
        required

        An IRI can be either:

        1. A URI (any valid URI scheme)
        2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
        • Type: string Pattern: ^[a-z][a-z0-9+.-]*:Format: url

          An IRI can be either:

          1. A URI (any valid URI scheme)
          2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
      • type
        required
      • antiPatternType
        Type: string
      • dateCreated
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • dateModified
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • description
        Type: string
      • endedAtTime
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • extensions
        Type: object
      • name
        Type: string
      • otherIdentifiers
        Type: array
      • reason
        Type: string
      • startedAtTime
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

  • type
    Type: stringenum
    required
    values
    • AssessmentEvent
    • AssessmentItemEvent
    • AssignableEvent
    • GradeEvent
    • MediaEvent
  • edApp

    • Base type for all Caliper entities

      • id
        required

        An IRI can be either:

        1. A URI (any valid URI scheme)
        2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
        • Type: string Pattern: ^[a-z][a-z0-9+.-]*:Format: url

          An IRI can be either:

          1. A URI (any valid URI scheme)
          2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
      • type
        required
      • dateCreated
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • dateModified
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • description
        Type: string
      • extensions
        Type: object
      • host
        Type: string
      • ipAddress
        Type: string
      • name
        Type: string
      • otherIdentifiers
        Type: array
      • userAgent
        Type: string
      • version
        Type: string
  • extensions
    Type: object
    • propertyName
      Type: anything
  • federatedSession

    • Base type for all Caliper entities

      • id
        required

        An IRI can be either:

        1. A URI (any valid URI scheme)
        2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
        • Type: string Pattern: ^[a-z][a-z0-9+.-]*:Format: url

          An IRI can be either:

          1. A URI (any valid URI scheme)
          2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
      • type
        required
      • client

        • Base type for all Caliper entities

          • id
            required

            An IRI can be either:

            1. A URI (any valid URI scheme)
            2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
          • type
            required
          • dateCreated
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

          • dateModified
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

          • description
            Type: string
          • extensions
            Type: object
          • host
            Type: string
          • ipAddress
            Type: string
          • name
            Type: string
          • otherIdentifiers
            Type: array
          • userAgent
            Type: string
          • version
            Type: string
      • dateCreated
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • dateModified
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • description
        Type: string
      • duration
        Type: string Pattern: ^PT(?:[0-9]+H)?(?:[0-9]+M)?(?:[0-9]+(?:\\.[0-9]+)?S)?$
      • endedAtTime
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • extensions
        Type: object
      • messageParameters
        Type: object
      • name
        Type: string
      • otherIdentifiers
        Type: array
      • startedAtTime
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • user

        • Base type for all Caliper entities

          • id
            required

            An IRI can be either:

            1. A URI (any valid URI scheme)
            2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
          • type
            required
          • dateCreated
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

          • dateModified
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

          • description
            Type: string
          • extensions
            Type: object
          • name
            Type: string
          • otherIdentifiers
            Type: array
  • generated

    • Base type for all Caliper entities

      • id
        required

        An IRI can be either:

        1. A URI (any valid URI scheme)
        2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
        • Type: string Pattern: ^[a-z][a-z0-9+.-]*:Format: url

          An IRI can be either:

          1. A URI (any valid URI scheme)
          2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
      • type
        required
      • attempt

        • Base type for all Caliper entities

          • id
            required

            An IRI can be either:

            1. A URI (any valid URI scheme)
            2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
          • type
            required
          • assignable
          • assignee
          • count
            Type: integer

            Integer numbers.

          • dateCreated
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

          • dateModified
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

          • description
            Type: string
          • duration
            Type: string Pattern: ^PT(?:[0-9]+H)?(?:[0-9]+M)?(?:[0-9]+(?:\\.[0-9]+)?S)?$
          • endedAtTime
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

          • extensions
            Type: object
          • name
            Type: string
          • otherIdentifiers
            Type: array
          • startedAtTime
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • dateCreated
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • dateModified
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • description
        Type: string
      • duration
        Type: string Pattern: ^PT(?:[0-9]+H)?(?:[0-9]+M)?(?:[0-9]+(?:\\.[0-9]+)?S)?$
      • endedAtTime
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • extensions
        Type: object
      • name
        Type: string
      • otherIdentifiers
        Type: array
      • startedAtTime
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

  • group

    • Base type for all Caliper entities

      • id
        required

        An IRI can be either:

        1. A URI (any valid URI scheme)
        2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
        • Type: string Pattern: ^[a-z][a-z0-9+.-]*:Format: url

          An IRI can be either:

          1. A URI (any valid URI scheme)
          2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
      • type
        required
      • dateCreated
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • dateModified
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • description
        Type: string
      • extensions
        Type: object
      • members
        Type: array
      • name
        Type: string
      • otherIdentifiers
        Type: array
      • subOrganizationOf
        Empty object
  • membership

    • Base type for all Caliper entities

      • id
        required

        An IRI can be either:

        1. A URI (any valid URI scheme)
        2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
        • Type: string Pattern: ^[a-z][a-z0-9+.-]*:Format: url

          An IRI can be either:

          1. A URI (any valid URI scheme)
          2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
      • type
        required
      • dateCreated
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • dateModified
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • description
        Type: string
      • extensions
        Type: object
      • member

        • Base type for all Caliper entities

          • id
            required

            An IRI can be either:

            1. A URI (any valid URI scheme)
            2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
          • type
            required
          • dateCreated
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

          • dateModified
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

          • description
            Type: string
          • extensions
            Type: object
          • name
            Type: string
          • otherIdentifiers
            Type: array
      • name
        Type: string
      • organization

        • Base type for all Caliper entities

          • id
            required

            An IRI can be either:

            1. A URI (any valid URI scheme)
            2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
          • type
            required
          • dateCreated
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

          • dateModified
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

          • description
            Type: string
          • extensions
            Type: object
          • members
            Type: array
          • name
            Type: string
          • otherIdentifiers
            Type: array
          • subOrganizationOf
      • otherIdentifiers
        Type: array
      • roles
        Type: array string[] · LisRole[]enum
        values
        • Administrator
        • Administrator#Administrator
        • Administrator#Developer
        • Administrator#ExternalDeveloper
        • Administrator#ExternalSupport
      • status
        Type: stringenum
        values
        • Active
        • Inactive
  • profile
    Type: stringenum
    values
    • GeneralProfile
    • AnnotationProfile
    • AssessmentProfile
    • AssignableProfile
    • FeedbackProfile
  • referrer

    Base type for all Caliper entities

    • id
      required

      An IRI can be either:

      1. A URI (any valid URI scheme)
      2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
      • Type: string Pattern: ^[a-z][a-z0-9+.-]*:Format: url

        An IRI can be either:

        1. A URI (any valid URI scheme)
        2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
    • type
      Type: stringenum
      required
      values
      • Entity
      • Agent
      • Person
      • SoftwareApplication
      • Organization
    • dateCreated
      Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

      the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

    • dateModified
      Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

      the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

    • description
      Type: string
    • extensions
      Type: object
    • name
      Type: string
    • otherIdentifiers
      Type: array
  • session

    • Base type for all Caliper entities

      • id
        required

        An IRI can be either:

        1. A URI (any valid URI scheme)
        2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
        • Type: string Pattern: ^[a-z][a-z0-9+.-]*:Format: url

          An IRI can be either:

          1. A URI (any valid URI scheme)
          2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
      • type
        required
      • client

        • Base type for all Caliper entities

          • id
            required

            An IRI can be either:

            1. A URI (any valid URI scheme)
            2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
          • type
            required
          • dateCreated
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

          • dateModified
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

          • description
            Type: string
          • extensions
            Type: object
          • host
            Type: string
          • ipAddress
            Type: string
          • name
            Type: string
          • otherIdentifiers
            Type: array
          • userAgent
            Type: string
          • version
            Type: string
      • dateCreated
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • dateModified
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • description
        Type: string
      • duration
        Type: string Pattern: ^PT(?:[0-9]+H)?(?:[0-9]+M)?(?:[0-9]+(?:\\.[0-9]+)?S)?$
      • endedAtTime
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • extensions
        Type: object
      • name
        Type: string
      • otherIdentifiers
        Type: array
      • startedAtTime
        Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

        the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

      • user

        • Base type for all Caliper entities

          • id
            required

            An IRI can be either:

            1. A URI (any valid URI scheme)
            2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
          • type
            required
          • dateCreated
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

          • dateModified
            Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

            the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

          • description
            Type: string
          • extensions
            Type: object
          • name
            Type: string
          • otherIdentifiers
            Type: array
  • target

    Base type for all Caliper entities

    • id
      required

      An IRI can be either:

      1. A URI (any valid URI scheme)
      2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
      • Type: string Pattern: ^[a-z][a-z0-9+.-]*:Format: url

        An IRI can be either:

        1. A URI (any valid URI scheme)
        2. A URN in the format "urn:uuid:" where UUID is a version 4 UUID
    • type
      Type: stringenum
      required
      values
      • Entity
      • Agent
      • Person
      • SoftwareApplication
      • Organization
    • dateCreated
      Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

      the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

    • dateModified
      Type: string Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{3}Z$Format: date-time

      the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

    • description
      Type: string
    • extensions
      Type: object
    • name
      Type: string
    • otherIdentifiers
      Type: array