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: 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
    • assignable

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

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