https://example.com/schemas/definitions
This is an example of using a definitions
object within a schema.
It is imported using allOf
and $ref
.
And the description has line breaks.
So.
Many.
Line.
Bre-
aks.
Everything is better with a quote.
Abstract | Extensible | Status | Identifiable | Custom Properties | Additional Properties | Access Restrictions | Defined In |
---|---|---|---|---|---|---|---|
Cannot be instantiated | Yes | Unknown status | Unknown identifiability | Forbidden | Allowed | none | definitions.schema.json |
object
(Definitions)
all of
Reference this group by using
{"$ref":"https://example.com/schemas/definitions#/definitions/myid"}
Property | Type | Required | Nullable | Defined by |
---|---|---|---|---|
id | string |
Optional | cannot be null | Definitions |
@id | string |
Required | cannot be null | Definitions |
meta:id | string |
Optional | cannot be null | Definitions |
A unique identifier given to every addressable thing.
id
- is optional
- Type:
string
- cannot be null
- defined in: Definitions
string
URI reference: the string must be a URI reference, according to RFC 3986
An id
with an @
in front of it. The @
stands for "dot com"
@id
- is required
- Type:
string
- cannot be null
- defined in: Definitions
string
URI: the string must be a URI, according to RFC 3986
An about ids. It is meta. If you are confused, send an email to the address specified in this property value.
meta:id
- is optional
- Type:
string
- cannot be null
- defined in: Definitions
string
email: the string must be an email address, according to RFC 5322, section 3.4.1