# description
A prompt for creating or editing document content.

# properties.type.$comment
This is a special property analogous to JSON-LD's `@type` keyword.

# properties.id.$comment
This is a special property analogous to JSON-LD's `@id` keyword.

# properties.identifiers.description
Any kind of identifier for any kind of Thing.

# properties.identifiers.$comment
Some identifiers have specific properties e.g the `issn` property for
the `Periodical` type. These should be used in preference to this
property which is intended for identifiers that do not yet have a
specific property. Identifiers can be represented as strings, but
using a `PropertyValue` will usually be better because it allows
for `propertyID` (i.e. the type of identifier).

# properties.doi.description
The work's Digital Object Identifier (https://doi.org/).

# properties.about.$comment
Consistent with https://schema.org/about, this property allows for
linking to one of more `Thing` nodes. This could for example include
a `Person` (e.g for a bibliography) or a `DefinedTerm` (e.g. for
subject areas the creative work relates to).

# properties.abstract.description
A short description that summarizes a `CreativeWork`.

# properties.provenance.description
A summary of the provenance of the content within the work.

# properties.contributors.description
A secondary contributor to the `CreativeWork`.

# properties.editors.$comment
Note that, consistent with schema.org, this property can only include
a `Person`, unlike `authors` and `maintainers` which can also include
`Organization`.

# properties.maintainers.$comment
A maintainer of a `Dataset`, `SoftwareApplication`, or other `CreativeWork`.
A maintainer is a `Person` or `Organization` that manages contributions to,
and/or publication of, some (typically complex) artifact. It is common for
distributions of software and data to be based on "upstream" sources.
When maintainer is applied to a specific version of something e.g. a particular
version or packaging of a Dataset, it is always possible that the upstream
source has a different maintainer. The `isBasedOn` property can be used to
indicate such relationships between datasets to make the different maintenance
roles clear. Similarly in the case of software, a package may have dedicated
maintainers working on integration into software distributions such as Ubuntu,
as well as upstream maintainers of the underlying work.

# properties.dateAccepted.$comment
This is not yet a schema.org property but the term is used
[in Dublin Core](http://purl.org/dc/terms/dateAccepted).

# properties.funders.description
People or organizations that funded the `CreativeWork`.

# properties.fundedBy.description
Grants that funded the `CreativeWork`; reverse of `fundedItems`.

# properties.fundedBy.$comment
This follows the proposal [here](https://github.com/schemaorg/schemaorg/issues/2258)
for a property that is the reverse of `fundedItems`.
It is an any because a `CreativeWork` may have been funded through more than
one `Grant`.

# properties.genre.description
Genre of the creative work, broadcast channel or group.

# properties.keywords.description
Keywords or tags used to describe this content. Multiple entries in a keywords list are typically delimited by commas.

# properties.isPartOf.description
An item or other CreativeWork that this CreativeWork is a part of.

# properties.licenses.description
License documents that applies to this content, typically indicated by URL.

# properties.parts.description
Elements of the collection which can be a variety of different elements, such as Articles, Datatables, Tables and more.

# properties.references.description
References to other creative works, such as another publication, web page, scholarly article, etc.

# properties.text.description
The textual content of this creative work.

# properties.version.$comment
In this case `string` is listed as an alternative before `number` to
avoid semantic version numbers e.g. `1.0` being parsed, and subsequently
encoded, as `1` thereby resulting in loss of information.

# properties.executionMode.description
Under which circumstances the node should be executed.

# properties.compilationDigest.description
A digest of the content, semantics and dependencies of the node.

# properties.compilationMessages.description
Messages generated while compiling the code.

# properties.executionDigest.description
The `compilationDigest` of the node when it was last executed.

# properties.executionTags.description
Tags in the code which affect its execution.

# properties.executionCount.description
A count of the number of times that the node has been executed.

# properties.executionCount.$comment
Intended to increment with each successive execution of the node, including across sessions.
Note that this differs to the `execution_count` in Jupyter Notebook format which is
the "code cell's prompt number" and which resets at the start of each new session.

# properties.executionRequired.description
Whether, and why, the code requires execution or re-execution.

# properties.executionStatus.description
Status of the most recent, including any current, execution.

# properties.executionInstance.description
The id of the kernel instance that performed the last execution.

# properties.executionInstance.$comment
Used to help identify whether execution is required due to the last execution
being in a difference instance (e.g. after a kernel restart).

# properties.executionEnded.description
The timestamp when the last execution ended.

# properties.executionMessages.description
Messages emitted while executing the node.

# properties.instructionTypes.description
The types of instructions that the prompt supports

# properties.nodeTypes.description
The types of nodes that the prompt supports

# properties.nodeCount.description
The number of nodes that the prompt supports

# properties.nodeCount.$comment
Use a string to indicate a range of possible node counts e.g. "1+" for one
or more nodes, "1-5" for one to five nodes.

# properties.queryPatterns.description
Regular expressions used to match the prompt with a user query