Skip to content

Commit 8b9259b

Browse files
Merge pull request #3 from libremfg/develop
Fix v2.0.0 documentation examples
2 parents 1df56a5 + 34d6df9 commit 8b9259b

File tree

3 files changed

+2579
-11
lines changed

3 files changed

+2579
-11
lines changed

Docs/content/posts/version-v2.0.0.md

+29-11
Original file line numberDiff line numberDiff line change
@@ -28,24 +28,36 @@ Based on the works of https://github.com/MESAInternational/B2MML-BatchML.
2828

2929
## Quick start
3030

31-
Start out by importing the schema and using it in your JSON documents.
31+
Start out by importing the schema and using it in your JSON documents. As an example:
3232

3333
```
34-
"$schema": "{{< siteurl >}}schemas/"
34+
"$schema": "{{< siteurl >}}schemas/v2.0.0.equipment.schema.json"
3535
```
3636

37-
Here is an example using the JSON schema in a `NotifyWorkDefined` message.
37+
Here is an example using the JSON schema in a `ProcessEquipment` message.
3838

3939
```json
4040
{
41-
"$schema": "{{< siteurl >}}schemas/",
42-
"NotifyWorkDefined": {
43-
"ApplicationArea": {},
44-
"DataArea": {
45-
"Notify": {},
46-
"WorkDefined": {
47-
41+
"$schema": "https://json.libremfg.ai/schemas/v2.0.0.equipment.schema.json",
42+
"ProcessEquipment": {
43+
"@releaseID": "1",
44+
"ApplicationArea": {
45+
"CreationDateTime": "2021-01-01T00:00:00Z",
46+
"Sender": {
47+
"LogicalID": "Rhize Manufacutring Data Hub"
4848
}
49+
},
50+
"DataArea": {
51+
"Process": {},
52+
"Equipment": [
53+
{
54+
"ID": "Acme Inc.",
55+
"Description": [
56+
"Acme Inc. Manufacturing Line 1"
57+
],
58+
"EquipmentLevel": "Enterprise"
59+
}
60+
]
4961
}
5062
}
5163
}
@@ -57,4 +69,10 @@ Refactored the v1.0.0.base.schema.json JSON file by separating it into multiple
5769

5870
Implemented several automated scripts to assist in refactoring. While these scripts are tailored for specific use cases, they can generally be disregarded outside of those particular scenarios.
5971

60-
In Version 2.0.0, a JSON Schema validator is used for verification, replacing the previous Lint-based approach. This update compiles and validates schemas through the use of scripts, specifically compileSchemas.js, located in scripts, and validate.mjs.
72+
In Version 2.0.0, a JSON Schema validator is used for verification, replacing the previous Lint-based approach. This update compiles and validates schemas through the use of scripts, specifically compileSchemas.js, located in scripts, and validate.mjs.
73+
74+
## Object Schema File Table
75+
76+
Use the search functionality of your browser to find an object of interet.
77+
78+
{{< table/propertiesV200 >}}

0 commit comments

Comments
 (0)