pyegeria 5.3.9.9.2__py3-none-any.whl → 5.3.9.9.4__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (55) hide show
  1. md_processing/__init__.py +49 -0
  2. md_processing/commands.json +3252 -0
  3. md_processing/dr_egeria_inbox/archive/dr_egeria_intro.md +254 -0
  4. md_processing/dr_egeria_inbox/archive/dr_egeria_intro_more_terms.md +696 -0
  5. md_processing/dr_egeria_inbox/archive/dr_egeria_intro_part1.md +254 -0
  6. md_processing/dr_egeria_inbox/archive/dr_egeria_intro_part2.md +298 -0
  7. md_processing/dr_egeria_inbox/archive/dr_egeria_intro_part3.md +608 -0
  8. md_processing/dr_egeria_inbox/archive/dr_egeria_intro_part4.md +94 -0
  9. md_processing/dr_egeria_inbox/archive/freddie_intro.md +284 -0
  10. md_processing/dr_egeria_inbox/archive/freddie_intro_orig.md +275 -0
  11. md_processing/dr_egeria_inbox/archive/test-term.md +110 -0
  12. md_processing/dr_egeria_inbox/cat_test.md +100 -0
  13. md_processing/dr_egeria_inbox/data_field.md +54 -0
  14. md_processing/dr_egeria_inbox/data_spec.md +77 -0
  15. md_processing/dr_egeria_inbox/data_spec_test.md +2406 -0
  16. md_processing/dr_egeria_inbox/data_test.md +86 -0
  17. md_processing/dr_egeria_inbox/dr_egeria_intro_categories.md +168 -0
  18. md_processing/dr_egeria_inbox/dr_egeria_intro_part1.md +280 -0
  19. md_processing/dr_egeria_inbox/dr_egeria_intro_part2.md +313 -0
  20. md_processing/dr_egeria_inbox/dr_egeria_intro_part3.md +1073 -0
  21. md_processing/dr_egeria_inbox/dr_egeria_isc1.md +44 -0
  22. md_processing/dr_egeria_inbox/glossary_creation_experiment.ipynb +341 -0
  23. md_processing/dr_egeria_inbox/glossary_test1.md +324 -0
  24. md_processing/dr_egeria_inbox/rel.md +8 -0
  25. md_processing/dr_egeria_inbox/sb.md +119 -0
  26. md_processing/dr_egeria_inbox/search_test.md +39 -0
  27. md_processing/dr_egeria_inbox/solution-components.md +154 -0
  28. md_processing/dr_egeria_inbox/solution_blueprints.md +118 -0
  29. md_processing/dr_egeria_inbox/synonym_test.md +42 -0
  30. md_processing/dr_egeria_inbox/t1.md +0 -0
  31. md_processing/dr_egeria_inbox/t2.md +268 -0
  32. md_processing/dr_egeria_outbox/processed-2025-05-15 19:52-data_test.md +94 -0
  33. md_processing/dr_egeria_outbox/processed-2025-05-16 07:39-data_test.md +88 -0
  34. md_processing/dr_egeria_outbox/processed-2025-05-17 16:01-data_field.md +56 -0
  35. md_processing/dr_egeria_outbox/processed-2025-05-18 15:51-data_test.md +103 -0
  36. md_processing/dr_egeria_outbox/processed-2025-05-18 16:47-data_test.md +94 -0
  37. md_processing/dr_egeria_outbox/processed-2025-05-19 07:14-data_test.md +96 -0
  38. md_processing/dr_egeria_outbox/processed-2025-05-19 07:20-data_test.md +100 -0
  39. md_processing/dr_egeria_outbox/processed-2025-05-19 07:22-data_test.md +88 -0
  40. md_processing/md_commands/__init__.py +3 -0
  41. md_processing/md_commands/blueprint_commands.py +303 -0
  42. md_processing/md_commands/data_designer_commands.py +1182 -0
  43. md_processing/md_commands/glossary_commands.py +1144 -0
  44. md_processing/md_commands/project_commands.py +163 -0
  45. md_processing/md_processing_utils/__init__.py +4 -0
  46. md_processing/md_processing_utils/common_md_proc_utils.py +724 -0
  47. md_processing/md_processing_utils/common_md_utils.py +172 -0
  48. md_processing/md_processing_utils/extraction_utils.py +486 -0
  49. md_processing/md_processing_utils/md_processing_constants.py +112 -0
  50. md_processing/md_processing_utils/message_constants.py +19 -0
  51. {pyegeria-5.3.9.9.2.dist-info → pyegeria-5.3.9.9.4.dist-info}/METADATA +1 -2
  52. {pyegeria-5.3.9.9.2.dist-info → pyegeria-5.3.9.9.4.dist-info}/RECORD +55 -5
  53. {pyegeria-5.3.9.9.2.dist-info → pyegeria-5.3.9.9.4.dist-info}/LICENSE +0 -0
  54. {pyegeria-5.3.9.9.2.dist-info → pyegeria-5.3.9.9.4.dist-info}/WHEEL +0 -0
  55. {pyegeria-5.3.9.9.2.dist-info → pyegeria-5.3.9.9.4.dist-info}/entry_points.txt +0 -0
@@ -0,0 +1,268 @@
1
+ # Demonstrating updates and additions
2
+
3
+ This document was derived from the processing of the file dr_egeria_intro.md; All of the Dr.Egeria statements have been
4
+ preserved (including the generated attributes such as the unique GUIDs) and the explanatory text has been replaced.
5
+
6
+ In this document we will add glossary categories, update existing terms to categorize them, and add some new terms that
7
+ further explain dr.egeria. This document is being written off-line (actually on a plane) - demonstrating one of the
8
+ intriguing features of dr.egeria - because its just text, it can be edited anywhere and anytime that there is a text
9
+ editor. Dr.Egeria files can be emailed, sent via text message, slack or maintained in a `git` repository.
10
+ It's just text with markdown annotations.
11
+
12
+ Ok, let's get started. First, we have the `Update Glossary` command below. There is nothing new we need to add at this
13
+ point so we can just leave it as-is. When this document is processed it will apply updates but if there are none,
14
+ It doesn't matter.
15
+
16
+
17
+ ---
18
+
19
+
20
+ # Update Glossary
21
+
22
+ ## Glossary Name
23
+
24
+ Egeria-Markdown
25
+
26
+ ## Description
27
+ Glossary to describe the vocabulary of Dr.Egeria - an Egeria Markdown language to support the exchange of metadata in a Markdown form.
28
+ Dr.Egeria allows users to input metadata using any text entry system that supports the entry of standard Markdown
29
+ notation and through post-processing
30
+ commands, validates the Egeria content and allows the requests to be sent to Egeria.
31
+
32
+ ## Language
33
+ English
34
+
35
+ ## Usage
36
+ 1. (optional) load an example or template for the type of object from Egeria.
37
+ 2. Create a new document (perhaps from a template) and edit it, adding in the content with the Dr.Egeria controlled Markdown language.
38
+ 3. Process the document to validate and display it before you submit it, Validation may annotate your document with recommendations and potential issues.
39
+ 4. Submit the document to Egeria using the Dr.Egeria commands.
40
+
41
+ ## Qualified Name
42
+ Glossary::Egeria-Markdown
43
+
44
+ ## Guid
45
+ 5878850f-0fc5-484d-8426-511c18615a66
46
+
47
+
48
+
49
+ Ok, now let's create a couple of glossary categories. They will be:
50
+
51
+ * **Writing Dr.Egeria Markdown** - where we describe elements of the Dr.Egeria language as terms within the category.
52
+ * **Processing Dr.Egeria Markdown** - where we describe the commands for processing Dr.Egeria.
53
+
54
+
55
+ Glossary categories have the following attributes:
56
+
57
+ | Attribute Name | Input Required? | Generated/Default? | Unique? | Notes |
58
+ |:-|:-|:-|:-|:-|
59
+ | Category Name | Yes | No | No | A display name (informal name). |
60
+ | Owning Glossary | Yes | No | Yes | This is the qualified name of the glossary that owns this category. |
61
+ | Description | No | No | No | A textual description of this category |
62
+ | Qualified Name | No | Yes | Yes | The qualified name can either be provided by the user or generated. If generated, a pattern is followed. |
63
+ | GUID | No | Yes | Yes | GUIDs are always generated by Egeria. They are meant for automation, not people. |
64
+
65
+ Qualified Names can either be user specified or generated. If generated the following the form:
66
+ `{local-qualifier}:{type}:{display name}`
67
+
68
+ * Local-Qualifier is an optional string that can be useful to both disambiguate similar names and to add some local context. Local qualifiers could be set to organization names, functions, business context, etc. The settings for a local qualifier is set either by setting the environment variable `EGERIA_LOCAL_QUALIFIER` or by passing in a parameter when executing one of the Dr.Egeria enabled commands. This could also be set for a team by an Egeria administrator.
69
+
70
+
71
+
72
+ # Update Categories
73
+
74
+ ## Category Name
75
+
76
+ Writing Dr.Egeria Markdown
77
+
78
+ ## Description
79
+ These terms describe the elements of the Dr.Egeria Markdown language and how to use them.
80
+
81
+ ## In Glossary
82
+ Glossary::Egeria-Markdown
83
+
84
+ ## Qualified Name
85
+ Category:Writing-Dr.Egeria-Markdown
86
+
87
+ ## Guid
88
+ c5ba25df-f7b1-4ecf-913a-c5c83a03d63a
89
+
90
+
91
+ ---
92
+
93
+
94
+
95
+
96
+ # Update Categories
97
+
98
+ ## Category Name
99
+
100
+ Processing Dr.Egeria Markdown
101
+
102
+ ## Description
103
+ These terms describe commands to process Dr.Egeria Markdown.
104
+
105
+ ## In Glossary
106
+ Glossary::Egeria-Markdown
107
+
108
+ ## Qualified Name
109
+ Category:Processing-Dr.Egeria-Markdown
110
+
111
+ ## Guid
112
+ 1f13ec0d-e0ad-4327-bc1c-58e4174dd950
113
+
114
+
115
+ ---
116
+
117
+
118
+
119
+ Ok now, let's add categories to some of the terms. Let's review the attributes of a term:
120
+
121
+ | Attribute Name | Input Required? | Generated/Default? | Unique? | Notes |
122
+ |:----------------| :- | :- | :- | :-|
123
+ | Term Name | Yes | No | No | A display name (informal name). |
124
+ | Owning Glossary | Yes | No | Yes | This is the qualified name of the glossary that owns this term. |
125
+ | Categories | No | No | Yes | This is the qualified (unique) name of the category. Multiple categories can be assigned, separated by a `,` or line. |
126
+ | Description | No | No | No | A textual description of this term |
127
+ | Qualified Name | No | Yes | Yes | The qualified name can either be provided by the user or generated. If generated, a pattern is followed. |
128
+ | GUID | No | Yes | Yes | GUIDs are always generated by Egeria. They are meant for automation, not people. |
129
+
130
+
131
+
132
+ # Update Term
133
+
134
+ ## Term Name
135
+
136
+ Command
137
+
138
+ ## Summary
139
+ Commands are how a user of the Freddie markdown language requests an action.
140
+
141
+ ## In Glossary
142
+ Glossary::Egeria-Markdown
143
+
144
+ ## Categories
145
+ Category:Processing-Dr.Egeria-Markdown
146
+ , Category:Writing-Dr.Egeria-Markdown
147
+
148
+ ## Status
149
+ DRAFT
150
+
151
+ ## Description
152
+ Commands are how a user can request Egeria to take an action such as Create or Update an Egeria element. Freddie
153
+ provides
154
+ a limited (but growing) set of commands. Freddie commands align with the pyegeria 'hey-egeria' command line interface.
155
+
156
+ ## Examples
157
+ Create Glossary or
158
+ Update Glossary or
159
+ Create Term or
160
+ Update Term
161
+
162
+ ## Usage
163
+ Commands are used in the Freddie Egeria markdown language.
164
+
165
+ ## Published Version
166
+ 0.1
167
+
168
+ ## Qualified Name
169
+ Term:Command
170
+
171
+ ## Guid
172
+ f59ca92e-9021-42bb-ae20-68fbbed57a86
173
+
174
+
175
+ ---
176
+
177
+
178
+
179
+ # Update Term
180
+
181
+ ## Term Name
182
+
183
+ Source
184
+
185
+ ## Summary
186
+ Source of the markdown content.
187
+
188
+ ## In Glossary
189
+ Glossary::Egeria-Markdown
190
+
191
+ ## Categories
192
+ Category:Processing-Dr.Egeria-Markdown
193
+
194
+ ## Status
195
+ DRAFT
196
+
197
+ ## Description
198
+ Source of the markdown content - could be jupyter or plain markdown file.
199
+
200
+ ## Examples
201
+ None
202
+
203
+ ## Usage
204
+ None
205
+
206
+ ## Version
207
+ 0.1
208
+
209
+ ## Qualified Name
210
+ Term:Source
211
+
212
+ ## Guid
213
+ fec76950-8a4b-4f20-9032-2b3775adee2c
214
+
215
+
216
+ ---
217
+
218
+
219
+
220
+ # Update Term
221
+
222
+ ## Term Name
223
+
224
+ Directive
225
+
226
+ ## Summary
227
+ A directive defines how the command is to be processed.
228
+
229
+ ## In Glossary
230
+ Glossary::Egeria-Markdown
231
+
232
+ ## Categories
233
+ Category:Processing-Dr.Egeria-Markdown
234
+
235
+ ## Status
236
+ DRAFT
237
+
238
+ ## Description
239
+ Directives are one of:
240
+ * display - just display what we've found
241
+ * validate - check the validity of the requested action
242
+ * process - process the requested action
243
+ * review?
244
+
245
+ ## Examples
246
+ None
247
+
248
+ ## Usage
249
+ None
250
+
251
+ ## Published Version
252
+ 0.2
253
+
254
+ ## Qualified Name
255
+ Term:Directive
256
+
257
+ ## Guid
258
+ fa716e1d-bd97-44e7-b64c-594cb8c2867c
259
+
260
+
261
+ ---
262
+
263
+
264
+ # Provenance
265
+
266
+ * t2.md Derived from processing file dr_egeria_intro_part2.md on 2025-03-20 15:06
267
+
268
+ ---
@@ -0,0 +1,94 @@
1
+
2
+
3
+
4
+
5
+
6
+
7
+ Data Specification for the Teddy Bear Drop Foot Clinical Trial
8
+
9
+ # foo Update Data Specification
10
+
11
+ ## Data Specification
12
+
13
+
14
+ Data Specification for the Teddy Bear Drop Foot Clinical Trial
15
+ >woof
16
+ ## Description
17
+ >Meow -
18
+
19
+ Principle data requirements for Teddy Bear Drop Foot Clinical Trial.
20
+
21
+
22
+
23
+
24
+ # Fpp Create Data Dictionary
25
+ ## Name
26
+ Clinical Trial Data Dictionary
27
+
28
+ ## Description
29
+ A data dictionary for clinical trial data elements.
30
+
31
+
32
+
33
+
34
+ ___
35
+
36
+
37
+
38
+ TBDF-Incoming Weekly Measurement Data
39
+
40
+
41
+ # Update Data Structure Form - created at 2025-05-15 19:52
42
+ Data Structure found from the search string: `<class 'filter'>`
43
+
44
+ # Update Data Structure
45
+
46
+ ## Data Structure Name
47
+
48
+ TBDF-Incoming Weekly Measurement Data
49
+
50
+ ## Description
51
+ This describes the weekly measurement data for each patient for the Teddy Bear drop foot clinical trial
52
+
53
+ ## Qualified Name
54
+ DataStruct::TBDF-Incoming Weekly Measurement Data
55
+
56
+ ## Namespace
57
+
58
+
59
+ ## Version Identifier
60
+
61
+
62
+ ## Guid
63
+ d71c7ee2-b414-4c8f-bf9b-b16bd3601855
64
+
65
+
66
+
67
+ WWT-Incoming Weekly Measurement Data
68
+
69
+ # Foo Update Data Structure
70
+
71
+ ## Qualified Name
72
+ DataStruct::WWT-Incoming Weekly Measurement Data
73
+
74
+ ## GUID
75
+ ae221834-a3a6-4f32-ac94-110dff761b49
76
+
77
+ ## Data Structure
78
+
79
+ WWT-Incoming Weekly Measurement Data
80
+
81
+
82
+ ## Description
83
+ A collection of data fields that form a data structure.
84
+
85
+
86
+ ## In Data Specification
87
+
88
+
89
+
90
+ ## Qualified Name
91
+
92
+ # Provenance
93
+
94
+ * Results from processing file data_test.md on 2025-05-15 19:52
@@ -0,0 +1,88 @@
1
+
2
+
3
+
4
+
5
+
6
+
7
+ Data Specification for the Teddy Bear Drop Foot Clinical Trial
8
+
9
+ # foo Update Data Specification
10
+
11
+ ## Data Specification
12
+
13
+
14
+ Data Specification for the Teddy Bear Drop Foot Clinical Trial
15
+ >woof
16
+ ## Description
17
+ >Meow -
18
+
19
+ Principle data requirements for Teddy Bear Drop Foot Clinical Trial.
20
+
21
+
22
+
23
+
24
+ # Fpp Create Data Dictionary
25
+ ## Name
26
+ Clinical Trial Data Dictionary
27
+
28
+ ## Description
29
+ A data dictionary for clinical trial data elements.
30
+
31
+
32
+
33
+
34
+ ___
35
+
36
+
37
+
38
+ TBDF-Incoming Weekly Measurement Data
39
+
40
+ # Update Data Structure
41
+
42
+ ## GUID
43
+ d71c7ee2-b414-4c8f-bf9b-b16bd3601855
44
+
45
+ ## Data Structure
46
+
47
+ TBDF-Incoming Weekly Measurement Data
48
+
49
+ ## Description
50
+ This describes the weekly measurement data for each patient for the Teddy Bear drop foot clinical trial
51
+
52
+ ## In Data Specification
53
+ Data Specification for the Teddy Bear Drop Foot Clinical Trial
54
+
55
+
56
+ ## Qualified Name
57
+
58
+
59
+ ___
60
+
61
+ WWT-Incoming Weekly Measurement Data
62
+
63
+ # Foo Update Data Structure
64
+
65
+ ## Qualified Name
66
+ DataStruct::WWT-Incoming Weekly Measurement Data
67
+
68
+ ## GUID
69
+ ae221834-a3a6-4f32-ac94-110dff761b49
70
+
71
+ ## Data Structure
72
+
73
+ WWT-Incoming Weekly Measurement Data
74
+
75
+
76
+ ## Description
77
+ A collection of data fields that form a data structure.
78
+
79
+
80
+ ## In Data Specification
81
+
82
+
83
+
84
+ ## Qualified Name
85
+
86
+ # Provenance
87
+
88
+ * Results from processing file data_test.md on 2025-05-16 07:39
@@ -0,0 +1,56 @@
1
+
2
+ # Update Collection
3
+
4
+ ## Collection Name
5
+
6
+
7
+
8
+ ## Description
9
+ Angle rotation of the left leg from vertical
10
+
11
+ ## Qualified Name
12
+ DataField::AngleLeftField
13
+
14
+ ## Classifications
15
+
16
+
17
+ ## Collection Type
18
+
19
+
20
+ ## Guid
21
+ 8aa5bef9-3a20-4160-a579-6e63b4db7f67
22
+
23
+
24
+
25
+
26
+ # Update Collection
27
+
28
+ ## Collection Name
29
+
30
+
31
+
32
+ ## Description
33
+ Unique identifier of the patient
34
+
35
+ ## Qualified Name
36
+ DataField::PatientId
37
+
38
+ ## Classifications
39
+
40
+
41
+ ## Collection Type
42
+
43
+
44
+ ## Guid
45
+ a698b362-a781-41c6-9e6e-bde6fe3a1737
46
+
47
+
48
+
49
+ ## In Data Dictionary
50
+
51
+ None
52
+
53
+
54
+ # Provenance
55
+
56
+ * Results from processing file data_field.md on 2025-05-17 16:01
@@ -0,0 +1,103 @@
1
+
2
+
3
+
4
+
5
+
6
+
7
+ Data Specification for the Teddy Bear Drop Foot Clinical Trial
8
+
9
+ # Create Data Specification
10
+
11
+ ## Data Specification
12
+
13
+
14
+ Data Specification for the Teddy Bear Drop Foot Clinical Trial
15
+ >woof
16
+ ## Description
17
+ >Meow -
18
+
19
+ Principle data requirements for Teddy Bear Drop Foot Clinical Trial.
20
+
21
+
22
+
23
+
24
+
25
+ ___
26
+
27
+ # Create Data Dictionary
28
+ ## Name
29
+ Clinical Trial Data Dictionary
30
+
31
+ ## Description
32
+ A data dictionary for clinical trial data elements.
33
+
34
+
35
+
36
+
37
+ ___
38
+
39
+ ___
40
+
41
+
42
+
43
+
44
+ TBDF-Incoming Weekly Measurement Data
45
+
46
+
47
+ # Update Data Structure Form - created at 2025-05-18 15:51
48
+ Data Structure found from the search string: `<class 'filter'>`
49
+
50
+ # Update Data Structure
51
+
52
+ ## Data Structure Name
53
+
54
+ TBDF-Incoming Weekly Measurement Data
55
+
56
+ ## Description
57
+ This describes the weekly measurement data for each patient for the Teddy Bear drop foot clinical trial
58
+
59
+ ## Qualified Name
60
+ DataStruct::TBDF-Incoming Weekly Measurement Data
61
+
62
+ ## Namespace
63
+
64
+
65
+ ## Version Identifier
66
+
67
+
68
+ ## Guid
69
+ 3eb5d206-6d3f-4b61-8f45-d7fbc05a870e
70
+
71
+
72
+
73
+ WWT-Incoming Weekly Measurement Data
74
+
75
+
76
+ # Update Data Structure Form - created at 2025-05-18 15:51
77
+ Data Structure found from the search string: `<class 'filter'>`
78
+
79
+ # Update Data Structure
80
+
81
+ ## Data Structure Name
82
+
83
+ WWT-Incoming Weekly Measurement Data
84
+
85
+ ## Description
86
+ A collection of data fields that form a data structure.
87
+
88
+ ## Qualified Name
89
+ DataStruct::WWT-Incoming Weekly Measurement Data
90
+
91
+ ## Namespace
92
+
93
+
94
+ ## Version Identifier
95
+
96
+
97
+ ## Guid
98
+ d3c0eb7f-476f-4649-a09c-f8ee39c0dfb9
99
+
100
+
101
+ # Provenance
102
+
103
+ * Results from processing file data_test.md on 2025-05-18 15:51
@@ -0,0 +1,94 @@
1
+
2
+
3
+
4
+
5
+
6
+
7
+ Data Specification for the Teddy Bear Drop Foot Clinical Trial
8
+
9
+ # Create Data Specification
10
+
11
+ ## Data Specification
12
+
13
+
14
+ Data Specification for the Teddy Bear Drop Foot Clinical Trial
15
+ >woof
16
+ ## Description
17
+ >Meow -
18
+
19
+ Principle data requirements for Teddy Bear Drop Foot Clinical Trial.
20
+
21
+
22
+
23
+
24
+
25
+ ___
26
+
27
+ # Create Data Dictionary
28
+ ## Name
29
+ Clinical Trial Data Dictionary
30
+
31
+ ## Description
32
+ A data dictionary for clinical trial data elements.
33
+
34
+
35
+
36
+
37
+ ___
38
+
39
+ ___
40
+
41
+
42
+
43
+
44
+ TBDF-Incoming Weekly Measurement Data
45
+
46
+ # Update Data Structure
47
+
48
+ ## GUID
49
+ 3eb5d206-6d3f-4b61-8f45-d7fbc05a870e
50
+
51
+ ## Data Structure
52
+
53
+ TBDF-Incoming Weekly Measurement Data
54
+
55
+ ## Description
56
+ This describes the weekly measurement data for each patient for the Teddy Bear drop foot clinical trial
57
+
58
+ ## In Data Specification
59
+ Data Specification for the Teddy Bear Drop Foot Clinical Trial
60
+
61
+
62
+ ## Qualified Name
63
+
64
+
65
+ ___
66
+
67
+ WWT-Incoming Weekly Measurement Data
68
+
69
+ # Update Data Structure
70
+
71
+ ## Qualified Name
72
+ DataStruct::WWT-Incoming Weekly Measurement Data
73
+
74
+ ## GUID
75
+ ae221834-a3a6-4f32-ac94-110dff761b49
76
+
77
+ ## Data Structure
78
+
79
+ WWT-Incoming Weekly Measurement Data
80
+
81
+
82
+ ## Description
83
+ A collection of data fields that form a data structure.
84
+
85
+
86
+ ## In Data Specification
87
+
88
+
89
+
90
+ ## Qualified Name
91
+
92
+ # Provenance
93
+
94
+ * Results from processing file data_test.md on 2025-05-18 16:47