@adobe/jsonschema2md
Version:
Validate and document complex JSON Schemas the easy way.
43 lines (24 loc) • 1.89 kB
Markdown
# Untitled undefined type in Subdir Schema
```txt
https://example.com/schemas/subdir/subdir#/definitions/content
```
| Abstract | Extensible | Status | Identifiable | Custom Properties | Additional Properties | Access Restrictions | Defined In |
| :------------------ | ---------- | -------------- | ------------ | :---------------- | --------------------- | ------------------- | --------------------------------------------------------------------------------------------- |
| Can be instantiated | No | Unknown status | No | Forbidden | Allowed | none | [subdir.schema.json\*](../generated-schemas/subdir/subdir.schema.json "open original schema") |
## content Type
unknown
# undefined Properties
| Property | Type | Required | Nullable | Defined by |
| :-------- | -------- | -------- | -------------- | :---------------------------------------------------------------------------------------------------------------------------------------- |
| [id](#id) | `string` | Optional | cannot be null | [Subdir](subdir-definitions-content-properties-id.md "https://example.com/schemas/subdir/subdir#/definitions/content/properties/id") |
## id
A unique identifier given to every addressable thing.
`id`
- is optional
- Type: `string`
- cannot be null
- defined in: [Subdir](subdir-definitions-content-properties-id.md "https://example.com/schemas/subdir/subdir#/definitions/content/properties/id")
### id Type
`string`
### id Constraints
**URI**: the string must be a URI, according to [RFC 3986](https://tools.ietf.org/html/rfc4291 "check the specification")