This document lays out the requirements for Predicate Improvement Process submissions, as detailed in the Predicate Improvement Process document.

Required in all submissions

• Field Name
• Field type:
  • “entity”
  • “text”
  • “integer”
  • “date”
  • “url”
• Number of values accepted:
  • “single”
  • “multiple”
• Tooltip description:
  • short description of the predicate (300 characters or less)
• Full description:
  • full description of the predicate (expected to be between a couple sentences or a couple paragraphs, depending on complexity)
• Examples of proper use:
  • text explaining acceptable usage of the predicate
• Examples of incorrect use:
  • text explaining incorrect usage of the predicate

Where values must be in specified list

If the predicate will only allow values from a specified list of allowed values (enumerated list, or enum), the following fields must be specified.

• Enum = “true”
• Values:
  • A list of allowed values. This will either be a list of text values or Golden entity IDs.

URLs in specified formats

If the predicate aims to capture data on urls in specified formats, it is best to capture this using the “text” field type and the following fields.

• Format as URL = “true”
• URL format: “<url string>”
  • example: “https://open.spotify.com/artist/{:id}” to generate the url for an artist on Spotify given the artist ID.