mdld-parse 0.9.3 → 0.9.4
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.
- package/dist/docs/Guide.md +660 -166
- package/dist/docs/guide-m.md +56 -0
- package/dist/docs/one-page.md +322 -0
- package/dist/examples/Status-SHACL.md +8 -10
- package/dist/examples/demo/journal.md +110 -9
- package/dist/examples/demo/minimal.md +18 -6
- package/dist/examples/demo/project.md +90 -7
- package/dist/examples/demo/prov.md +107 -0
- package/dist/examples/demo/rdf.md +69 -0
- package/dist/examples/demo/recipe.md +79 -15
- package/dist/examples/demo/research.md +110 -30
- package/dist/examples/demo/shacl.md +161 -0
- package/dist/examples/demo/space-mission.md +109 -28
- package/dist/examples/demo/tasks.md +175 -0
- package/dist/examples/demo/xsd.md +91 -0
- package/dist/index.html +686 -260
- package/dist/index.js +469 -247
- package/package.json +2 -2
- package/dist/examples/prov-o.md +0 -2367
- package/dist/examples/rdf.md +0 -827
- package/dist/examples/shacl.md +0 -3399
|
@@ -0,0 +1,56 @@
|
|
|
1
|
+
# MD-LD User Guide
|
|
2
|
+
|
|
3
|
+
This document will guide you from the start to proficiency in MD-LD authoring.
|
|
4
|
+
|
|
5
|
+
## 1. First annotation, primary subject definition
|
|
6
|
+
|
|
7
|
+
~~~md
|
|
8
|
+
# Alice's Journal
|
|
9
|
+
|
|
10
|
+
Hi! My name is Alice Smith. This is my personal semantic journal.
|
|
11
|
+
~~~
|
|
12
|
+
|
|
13
|
+
This is a regular Markdown note. It is transparent for MD-LD parser. Now let's add our first annotation. We can think of it as like we have a set of special highlighters that we use to mark important parts of the text. So first line is the choice of particular set of markers and in the `##` header you can see our first `{}` curly braces annotation.
|
|
14
|
+
|
|
15
|
+
~~~md
|
|
16
|
+
[my] <tag:alice.smith@example.org,2026:>
|
|
17
|
+
|
|
18
|
+
# Alice's Journal
|
|
19
|
+
|
|
20
|
+
## Alice {=my:person/alice .prov:Person label}
|
|
21
|
+
|
|
22
|
+
Hi! My name is Alice Smith. This is my personal semantic journal.
|
|
23
|
+
~~~
|
|
24
|
+
|
|
25
|
+
Now we have used our personal identifier for Alice - `tag:alice.smith@example.org,2026:person/alice` - it gets unfolded from the short `my:` value with the base IRI set in the first line. This declared that Alice is a person with a label "Alice". Our first point in the knowledge graph. We use built-in PROV-O standard ontology that is designed to describe relations between agents, entities and activities. A `prov:Person` is a kind of `prov:Agent`. `label` is also added as a literal property to have a nice short name for display in graph visualizations. Not having a prefix assumes use the default `@vocab` - `rdfs:`. So `label` is a shortcut for `rdfs:label` to ease friction at labeling things. Then the node on the graph will show cleanly as `Alice` in most graph visualizers and interfaces.
|
|
26
|
+
|
|
27
|
+
## 2. Context, authority, prefixes
|
|
28
|
+
|
|
29
|
+
First step is to get the concept of namespaces for building knowledge graphs. Everything in the graph - be it subjects, predicates or objects - each of them have unique identifiers - IRI. An IRI may be defined in multiple ways. Most straightforward is the use of URL as IRI. You can see this in all W3C ontologies definitions, that are included as default context in MD-LD. These prefixes may be used without declaration:
|
|
30
|
+
|
|
31
|
+
```md
|
|
32
|
+
[rdf] <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
|
|
33
|
+
[rdfs] <http://www.w3.org/2000/01/rdf-schema#>
|
|
34
|
+
[xsd] <http://www.w3.org/2001/XMLSchema#>
|
|
35
|
+
[sh] <http://www.w3.org/ns/shacl#>
|
|
36
|
+
[prov] <http://www.w3.org/ns/prov#>
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
These are 5 core ontologies - collections of interconnected terms - that lay foundation to the expressive knowledge graphs. You can open the links and read about the terms available in each ontology.
|
|
40
|
+
|
|
41
|
+
|
|
42
|
+
So how do we create an IRI? If you have a web-site or you prefer to use some external authority like your company domain or your own social media account - just use the URL link as IRI and it's good to go - `# Alice {=https://example.org/person/alice .prov:Person label}`
|
|
43
|
+
|
|
44
|
+
|
|
45
|
+
But what if you don't have a domain or just want a local personal namespaced IRI? just use the RFC 4151 format that allows to create private namespace with domain/email or any other authority you may provide - be it an ID in some system or a cryptographic key. The IRI assembles as follows - starts with `tag:`, then we put the authority - domain, email or other, then `,2026-05-04:` - the time when the authority was active. You can also provide only year or only year and month - then it will be assumed that you were owning the authority on 1st day of the month/year. Then you may add a custom subspace `journal/` and here you go - your own tag-based namespace is ready for use.
|
|
46
|
+
|
|
47
|
+
`[journal] <tag:alice.smith@example.org,2026:journal/>`
|
|
48
|
+
|
|
49
|
+
This is your first important line of MD-LD - a prefix declaration - a choice of that particular highlighter color that we need to build or own knowledge graphs.
|
|
50
|
+
|
|
51
|
+
When you write `[prefix]` it holds the short version of the IRI in `<IRI>` and it allows us to author complex IRIs without repeating long strings every time. To generate `http://www.w3.org/ns/prov#Entity` we can use shorter version - `prov:Entity` - 'prov:' is built-in. For everything else - don't forget to declare all prefixes first. This is the key feature of MD-LD - each note is self-contained and can be understood without any external context.
|
|
52
|
+
|
|
53
|
+
|
|
54
|
+
|
|
55
|
+
|
|
56
|
+
|
|
@@ -0,0 +1,322 @@
|
|
|
1
|
+
# MD-LD One Page Guide
|
|
2
|
+
|
|
3
|
+
**Semantic Markdown, no guessing, no magic**
|
|
4
|
+
|
|
5
|
+
MD-LD lets you **add meaning without breaking Markdown**.
|
|
6
|
+
Add `{...}` → you get an RDF graph.
|
|
7
|
+
Delete `{...}` → plain Markdown remains.
|
|
8
|
+
|
|
9
|
+
Everything semantic is **explicit**, **local**, and **traceable**.
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## 0. Mental model (read once)
|
|
14
|
+
|
|
15
|
+
MD-LD always writes **triples**:
|
|
16
|
+
|
|
17
|
+
```
|
|
18
|
+
Subject ──predicate──▶ Object / Literal
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
That’s it.
|
|
22
|
+
|
|
23
|
+
At any annotation `{...}`, there may be:
|
|
24
|
+
|
|
25
|
+
| Symbol | Meaning |
|
|
26
|
+
| ------ | ---------------------------------------------------- |
|
|
27
|
+
| **S** | current subject (IRI) |
|
|
28
|
+
| **O** | object IRI (from link, image, or `{+iri}`) |
|
|
29
|
+
| **L** | literal text (from the attached Markdown span/block) |
|
|
30
|
+
|
|
31
|
+
No subject → no triple
|
|
32
|
+
No guessing → no triple
|
|
33
|
+
No `{...}` → no semantics
|
|
34
|
+
|
|
35
|
+
---
|
|
36
|
+
|
|
37
|
+
## 1. Start with a document that *already is* a graph
|
|
38
|
+
|
|
39
|
+
Always declare a subject first.
|
|
40
|
+
|
|
41
|
+
```md
|
|
42
|
+
[alice] <tag:alice@example.com,2026:>
|
|
43
|
+
|
|
44
|
+
# Walnut Bread {=alice:walnut-bread .Recipe name}
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
This emits:
|
|
48
|
+
|
|
49
|
+
```turtle
|
|
50
|
+
tag:alice@example.com,2026:walnut-bread
|
|
51
|
+
a schema:Recipe ;
|
|
52
|
+
schema:name "Walnut Bread" .
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
**Why this matters**
|
|
56
|
+
|
|
57
|
+
* Your note is already an addressable node
|
|
58
|
+
* Everything that follows attaches to it
|
|
59
|
+
* This is how “casual notes” become “knowledge”
|
|
60
|
+
|
|
61
|
+
---
|
|
62
|
+
|
|
63
|
+
### 1.1. Prefix Folding: Build Your Namespace
|
|
64
|
+
|
|
65
|
+
Create hierarchical namespaces by referencing previous prefixes:
|
|
66
|
+
|
|
67
|
+
```md
|
|
68
|
+
# Your domain authority
|
|
69
|
+
[my] <tag:mymail@domain.com,2026:>
|
|
70
|
+
|
|
71
|
+
# Build the hierarchy
|
|
72
|
+
[j] <my:journal:>
|
|
73
|
+
[p] <my:property:>
|
|
74
|
+
[c] <my:class:>
|
|
75
|
+
|
|
76
|
+
# Use in content
|
|
77
|
+
# 2026-01-27 {=j:2026-01-27 .c:Event p:date ^^xsd:date}
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
**Resolves to:**
|
|
81
|
+
- `j:2026-01-27` → `tag:mymail@domain.com,2026:journal:2026-01-27`
|
|
82
|
+
- `c:Event` → `tag:mymail@domain.com,2026:class:Event`
|
|
83
|
+
- `p:date` → `tag:mymail@domain.com,2026:property:date`
|
|
84
|
+
|
|
85
|
+
Perfect for personal knowledge graphs without external dependencies.
|
|
86
|
+
|
|
87
|
+
---
|
|
88
|
+
|
|
89
|
+
## 2. Value carriers (what can hold meaning)
|
|
90
|
+
|
|
91
|
+
Only these Markdown forms can emit values:
|
|
92
|
+
|
|
93
|
+
**Inline**
|
|
94
|
+
|
|
95
|
+
* `[text] {...}`
|
|
96
|
+
* `*text* {...}`, `**text** {...}`
|
|
97
|
+
* `` `code` {...}``
|
|
98
|
+
|
|
99
|
+
**Block**
|
|
100
|
+
|
|
101
|
+
* Headings
|
|
102
|
+
* List items
|
|
103
|
+
* Blockquotes
|
|
104
|
+
* Code blocks (fence with `{...}`)
|
|
105
|
+
|
|
106
|
+
If `{...}` cannot clearly attach → **nothing is emitted**.
|
|
107
|
+
|
|
108
|
+
---
|
|
109
|
+
|
|
110
|
+
## 3. The three predicate forms (the whole algebra)
|
|
111
|
+
|
|
112
|
+
Every triple is written using **one of three predicate shapes**:
|
|
113
|
+
|
|
114
|
+
| Form | Emits |
|
|
115
|
+
| ----- | ------- |
|
|
116
|
+
| `p` | `S → L` |
|
|
117
|
+
| `?p` | `S → O` |
|
|
118
|
+
| `!p` | `O → S` |
|
|
119
|
+
|
|
120
|
+
Nothing else exists.
|
|
121
|
+
|
|
122
|
+
### Example — all three at once
|
|
123
|
+
|
|
124
|
+
```md
|
|
125
|
+
[alice] <tag:alice@example.com,2026:>
|
|
126
|
+
|
|
127
|
+
[Bread] {name}
|
|
128
|
+
[Walnut] {+alice:walnut ?hasIngredient}
|
|
129
|
+
[Recipe](https://en.wikipedia.org/wiki/Recipe) {!hasPart}
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
Never use shortened CURIE in regular Markdown links. They must be valid URLs for the browser to navigate to.
|
|
133
|
+
|
|
134
|
+
---
|
|
135
|
+
|
|
136
|
+
## 4. Literals are always local
|
|
137
|
+
|
|
138
|
+
Text comes **only** from the attached carrier.
|
|
139
|
+
|
|
140
|
+
```md
|
|
141
|
+
[2024] {published ^^xsd:gYear}
|
|
142
|
+
[Delicious bread] {description @en}
|
|
143
|
+
```
|
|
144
|
+
|
|
145
|
+
No datatype or language is ever inferred.
|
|
146
|
+
|
|
147
|
+
---
|
|
148
|
+
|
|
149
|
+
## 5. Object IRIs (links or `{+iri}`)
|
|
150
|
+
|
|
151
|
+
Objects exist only if explicitly present.
|
|
152
|
+
|
|
153
|
+
```md
|
|
154
|
+
[alice] <tag:alice@example.com,2026:>
|
|
155
|
+
|
|
156
|
+
[Walnuts](tag:alice@example.com,2026:walnut) {?ingredient}
|
|
157
|
+
```
|
|
158
|
+
|
|
159
|
+
or
|
|
160
|
+
|
|
161
|
+
```md
|
|
162
|
+
[Walnuts] {+alice:walnut ?ingredient}
|
|
163
|
+
```
|
|
164
|
+
|
|
165
|
+
Same graph. Different ergonomics.
|
|
166
|
+
|
|
167
|
+
---
|
|
168
|
+
|
|
169
|
+
## 6. Lists = pure Markdown structure, explicit annotations only
|
|
170
|
+
|
|
171
|
+
Lists have **no semantic scope**. Each item must have explicit annotations.
|
|
172
|
+
|
|
173
|
+
```md
|
|
174
|
+
[alice] <tag:alice@example.com,2026:>
|
|
175
|
+
|
|
176
|
+
Ingredients: {=alice:recipe .Container}
|
|
177
|
+
|
|
178
|
+
- Walnuts {+alice:walnut ?member .alice:Ingredient name}
|
|
179
|
+
- Flour {+alice:flour ?member .alice:Ingredient name}
|
|
180
|
+
- Water {+alice:water ?member .alice:Ingredient name}
|
|
181
|
+
```
|
|
182
|
+
|
|
183
|
+
Result: clean, explicit graph. No implicit semantics.
|
|
184
|
+
|
|
185
|
+
### List Item Requirements
|
|
186
|
+
|
|
187
|
+
**✅ DO - Items with explicit subjects emit semantics:**
|
|
188
|
+
```md
|
|
189
|
+
- **Flour** {=alice:flour} # Clean subject
|
|
190
|
+
- **Walnuts** {=alice:walnuts} # Clean subject
|
|
191
|
+
```
|
|
192
|
+
|
|
193
|
+
|
|
194
|
+
**Critical Rule**: **All list items must have explicit subject (`{=iri}` or `{+iri}`) to emit semantics.**
|
|
195
|
+
|
|
196
|
+
**Valid Alternatives for Additional Information:**
|
|
197
|
+
|
|
198
|
+
**✅ Nested Lists (Pure Structure)**
|
|
199
|
+
```md
|
|
200
|
+
- **Flour** {=alice:flour}
|
|
201
|
+
Properties:
|
|
202
|
+
- **Organic** {+alice:organic ?alice:hasProperty .alice:Property label}
|
|
203
|
+
```
|
|
204
|
+
|
|
205
|
+
**✅ Separate Sections**
|
|
206
|
+
```md
|
|
207
|
+
- **Flour** {=alice:flour}
|
|
208
|
+
|
|
209
|
+
## Flour Description {=alice:flour}
|
|
210
|
+
[*Important*] {priority .Important}
|
|
211
|
+
```
|
|
212
|
+
|
|
213
|
+
**Why?** Lists are **pure Markdown structure**. This keeps them predictable and streaming-safe.
|
|
214
|
+
|
|
215
|
+
---
|
|
216
|
+
|
|
217
|
+
## 7. Fragments = structured documents
|
|
218
|
+
|
|
219
|
+
Fragments turn sections into addressable nodes.
|
|
220
|
+
|
|
221
|
+
```md
|
|
222
|
+
[alice] <tag:alice@example.com,2026:>
|
|
223
|
+
|
|
224
|
+
## Instructions {=#steps .HowTo}
|
|
225
|
+
|
|
226
|
+
### Mixing {=#step-1 .HowToStep rdfs:label}
|
|
227
|
+
|
|
228
|
+
> Mix ingredients {text}
|
|
229
|
+
|
|
230
|
+
### Baking {=#step-2 .HowToStep rdfs:label}
|
|
231
|
+
|
|
232
|
+
> Bake for 45 minutes {text}
|
|
233
|
+
```
|
|
234
|
+
|
|
235
|
+
Emits:
|
|
236
|
+
|
|
237
|
+
```turtle
|
|
238
|
+
tag:alice@example.com,2026:walnut-bread#steps a schema:HowTo .
|
|
239
|
+
tag:alice@example.com,2026:walnut-bread#step-1 a schema:HowToStep ; rdfs:label "Mixing" ; schema:text "Mix ingredients" .
|
|
240
|
+
tag:alice@example.com,2026:walnut-bread#step-2 a schema:HowToStep ; rdfs:label "Baking" ; schema:text "Bake for 45 minutes" .
|
|
241
|
+
```
|
|
242
|
+
|
|
243
|
+
Fragments always attach to the **current subject base**.
|
|
244
|
+
|
|
245
|
+
---
|
|
246
|
+
|
|
247
|
+
## 8. Blockquotes = descriptions, abstracts, notes
|
|
248
|
+
|
|
249
|
+
```md
|
|
250
|
+
> A dense, rustic bread with toasted walnuts. {description}
|
|
251
|
+
```
|
|
252
|
+
|
|
253
|
+
Readable prose → structured data.
|
|
254
|
+
|
|
255
|
+
---
|
|
256
|
+
|
|
257
|
+
## 9. Code blocks are first-class values
|
|
258
|
+
|
|
259
|
+
````md
|
|
260
|
+
[alice] <tag:alice@example.com,2026:>
|
|
261
|
+
|
|
262
|
+
```txt {=alice:walnut-bread#formula .Recipe text}
|
|
263
|
+
500g flour
|
|
264
|
+
300ml water
|
|
265
|
+
```
|
|
266
|
+
````
|
|
267
|
+
|
|
268
|
+
Code content becomes a literal.
|
|
269
|
+
Language fences stay intact.
|
|
270
|
+
|
|
271
|
+
---
|
|
272
|
+
|
|
273
|
+
## 10. Reverse relations (write from either side)
|
|
274
|
+
|
|
275
|
+
```md
|
|
276
|
+
[alice] <tag:alice@example.com,2026:>
|
|
277
|
+
|
|
278
|
+
Used in: {!hasIngredient}
|
|
279
|
+
|
|
280
|
+
- Salad {=alice:salad}
|
|
281
|
+
````
|
|
282
|
+
|
|
283
|
+
Same graph. Different narrative flow.
|
|
284
|
+
|
|
285
|
+
---
|
|
286
|
+
|
|
287
|
+
## 11. What MD-LD never does
|
|
288
|
+
|
|
289
|
+
* ❌ No implicit meaning
|
|
290
|
+
* ❌ No blank nodes
|
|
291
|
+
* ❌ No inferred subjects
|
|
292
|
+
* ❌ No structural guessing
|
|
293
|
+
* ❌ No multi-pass parsing
|
|
294
|
+
* ❌ **No semantic list propagation**
|
|
295
|
+
|
|
296
|
+
Every triple is **authored**, not derived.
|
|
297
|
+
|
|
298
|
+
---
|
|
299
|
+
|
|
300
|
+
## 12. Why this scales (humans + agents)
|
|
301
|
+
|
|
302
|
+
Because MD-LD is:
|
|
303
|
+
|
|
304
|
+
* **Streaming-parseable**
|
|
305
|
+
* **Round-trip safe**
|
|
306
|
+
* **Text-preserving**
|
|
307
|
+
* **SPARQL-addressable**
|
|
308
|
+
|
|
309
|
+
Agents can:
|
|
310
|
+
|
|
311
|
+
* align facts via SPARQL
|
|
312
|
+
* add/remove triples
|
|
313
|
+
* serialize changes back into Markdown
|
|
314
|
+
without breaking prose, layout, or intent.
|
|
315
|
+
|
|
316
|
+
Your document becomes a **shared semantic surface**, not a data export.
|
|
317
|
+
|
|
318
|
+
---
|
|
319
|
+
|
|
320
|
+
## One sentence summary
|
|
321
|
+
|
|
322
|
+
> **MD-LD is RDF you can read, write, diff, query, and share—without ever leaving Markdown.**
|
|
@@ -6,28 +6,26 @@ A controlled vocabulary.
|
|
|
6
6
|
|
|
7
7
|
---
|
|
8
8
|
|
|
9
|
-
#
|
|
9
|
+
# Task Shape {=ex:TaskShape .sh:NodeShape label}
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
Targets all [Task] {+ex:Task ?sh:targetClass} instances to have at least one [status] {+#status ?sh:property sh:name}.
|
|
12
12
|
|
|
13
|
-
## Status Property {
|
|
13
|
+
## Status Property {=#status .sh:PropertyShape}
|
|
14
14
|
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
Required: [1] {sh:minCount ^^xsd:integer}
|
|
15
|
+
Has at least [1] {sh:minCount ^^xsd:integer} [status] {+ex:status ?sh:path} value.
|
|
18
16
|
|
|
19
17
|
---
|
|
20
18
|
|
|
21
19
|
# Test Data
|
|
22
20
|
|
|
23
|
-
##
|
|
21
|
+
## Task with status {=ex:task-valid .ex:Task label}
|
|
24
22
|
|
|
25
|
-
|
|
23
|
+
[active] {+ex:Active ?ex:status}
|
|
26
24
|
|
|
27
|
-
|
|
25
|
+
This record should pass validation.
|
|
28
26
|
|
|
29
27
|
---
|
|
30
28
|
|
|
31
|
-
##
|
|
29
|
+
## Task without a status {=ex:task-invalid .ex:Task label}
|
|
32
30
|
|
|
33
31
|
This record should fail validation - missing required status.
|
|
@@ -1,18 +1,119 @@
|
|
|
1
|
-
[
|
|
1
|
+
[j] <tag:alice@example.com,2026:journal:>
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
# Personal Journal {=j:index .prov:Collection label}
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Daily journal with proper PROV-O provenance and temporal structure.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Includes records for [2026] {+j:2026/index ?prov:hadMember}.
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
## Year 2026 {=j:2026/index .prov:Activity .prov:Collection label}
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
This is all notes made in 2026 collection. It includes monthly collections:
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
- January {+j:2026/01/index ?prov:hadMember}
|
|
14
|
+
- February {+j:2026/02/index ?prov:hadMember}
|
|
15
|
+
- March {+j:2026/03/index ?prov:hadMember}
|
|
16
|
+
- April {+j:2026/04/index ?prov:hadMember}
|
|
17
|
+
- May {+j:2026/05/index ?prov:hadMember}
|
|
14
18
|
|
|
15
|
-
|
|
19
|
+
## May 2026 {=j:2026/05/index .prov:Activity .prov:Collection label}
|
|
16
20
|
|
|
17
|
-
|
|
21
|
+
Started: [2026-05-01T00:00:00+04:00] {prov:startedAtTime ^^xsd:dateTime}
|
|
22
|
+
|
|
23
|
+
We have 5 weeks in May - [1-3] {+j:2026/05/week-1/index ?prov:hadMember}, [4-10] {+j:2026/05/week-2/index ?prov:hadMember}, [11-17] {+j:2026/05/week-3/index ?prov:hadMember}, [18-24] {+j:2026/05/week-4/index ?prov:hadMember}, [25-31] {+j:2026/05/week-5/index ?prov:hadMember}.
|
|
24
|
+
|
|
25
|
+
======
|
|
26
|
+
|
|
27
|
+
#### 06 May 2026 {=j:2026/05/06/index .prov:Activity label}
|
|
28
|
+
|
|
29
|
+
It's our first record in [week 2] {+j:2026/05/week-2/index ?prov:wasInformedBy}.
|
|
30
|
+
|
|
31
|
+
Complete day with activities, locations, and emotional state.
|
|
32
|
+
|
|
33
|
+
Started: [2026-05-06T08:00:00+04:00] {prov:startedAtTime ^^xsd:dateTime}
|
|
34
|
+
Ended: [2026-05-06T23:30:00+04:00] {prov:endedAtTime ^^xsd:dateTime}
|
|
35
|
+
|
|
36
|
+
Includes these activities: [morning] {+#morning !prov:wasInformedBy}, [afternoon] {+#afternoon !prov:wasInformedBy} and [social] {+#social !prov:wasInformedBy}.
|
|
37
|
+
|
|
38
|
+
### Morning Activities {=#morning .prov:Activity label}
|
|
39
|
+
|
|
40
|
+
I had a [walk] {+#walk ?prov:wasInformedBy} and a [coffee] {+#coffee-prep ?prov:wasInformedBy}.
|
|
41
|
+
|
|
42
|
+
**Morning Walk** {=#walk .prov:Activity label}
|
|
43
|
+
- Duration: [45] {j:duration ^^xsd:integer} minutes
|
|
44
|
+
- Distance: [2.5] {j:distance ^^xsd:decimal} miles
|
|
45
|
+
- Location: [Central Park] {+j:place/central-park .prov:Location ?prov:atLocation}
|
|
46
|
+
- Equipment: [Running Shoes] {+j:shoes/running ?prov:used}
|
|
47
|
+
- Generated: [Heart Rate Data] {+j:2026/05/06/hr-data ?prov:generated}
|
|
48
|
+
|
|
49
|
+
**Coffee Preparation** {=#coffee-prep .prov:Activity ?prov:used}
|
|
50
|
+
- Location: [Home] {+j:place/home ?prov:atLocation}
|
|
51
|
+
- Resources: [Coffee Beans] {+j:coffee/beans ?prov:used}, [Water] {+j:coffee/water ?prov:used}
|
|
52
|
+
- Generated: [Morning Coffee] {+#morning-coffee ?prov:generated}
|
|
53
|
+
|
|
54
|
+
### Afternoon Activities {=#afternoon .prov:Activity label}
|
|
55
|
+
|
|
56
|
+
**Reading Session** {=#reading .prov:Activity}
|
|
57
|
+
- Book: [Dune] {+j:dune-book .prov:Entity ?prov:used}
|
|
58
|
+
- Pages: [42] {j:pages ^^xsd:integer}
|
|
59
|
+
- Duration: [2] {j:hours ^^xsd:integer}
|
|
60
|
+
- Generated: [Reading Notes] {+j:reading-notes ?prov:generated}
|
|
61
|
+
|
|
62
|
+
**Work Session** {+j:work .prov:Activity ?prov:used}
|
|
63
|
+
- Task: [API Documentation] {+j:api-docs .prov:Entity ?prov:used}
|
|
64
|
+
- Duration: [3] {j:hours ^^xsd:integer}
|
|
65
|
+
- Generated: [Documentation Updates] {+j:doc-updates ?prov:generated}
|
|
66
|
+
|
|
67
|
+
### Social Interactions {=#social .prov:Activity label}
|
|
68
|
+
|
|
69
|
+
**Coffee Meeting** {+j:coffee-meeting .prov:Activity ?prov:used}
|
|
70
|
+
- Associated with: [Sam] {+j:sam .prov:Person ?prov:wasAssociatedWith}
|
|
71
|
+
- Location: [Local Cafe] {+j:cafe .prov:Location ?prov:atLocation}
|
|
72
|
+
- Duration: [30] {j:minutes ^^xsd:integer}
|
|
73
|
+
- Topic: [Career Changes] {j:topic}
|
|
74
|
+
|
|
75
|
+
## Emotional State Tracking {=#emotional-state .prov:Entity label}
|
|
76
|
+
|
|
77
|
+
Daily mood and energy levels with temporal context.
|
|
78
|
+
|
|
79
|
+
### Mood Data {=j:mood-data .prov:Entity label}
|
|
80
|
+
Date: [2026-05-06] {j:date ^^xsd:date}
|
|
81
|
+
Mood: [happy] {j:mood}
|
|
82
|
+
Energy level: [8] {j:energy ^^xsd:integer} out of 10
|
|
83
|
+
Stress level: [2] {j:stress ^^xsd:integer} out of 10
|
|
84
|
+
|
|
85
|
+
### Location History {=j:location-history .prov:Entity label}
|
|
86
|
+
Places visited with frequency and context.
|
|
87
|
+
|
|
88
|
+
Locations:
|
|
89
|
+
- [Central Park] {+j:central-park ?j:visited} - [3] {j:visitCount ^^xsd:integer} times this week
|
|
90
|
+
- [Local Cafe] {+j:cafe ?j:visited} - [2] {j:visitCount ^^xsd:integer} times this week
|
|
91
|
+
- [Home Office] {+j:home-office ?j:visited} - [5] {j:visitCount ^^xsd:integer} days this week
|
|
92
|
+
|
|
93
|
+
## Week 2 May 2026 {=j:2026/05/week-2/index .prov:Activity .prov:Collection label}
|
|
94
|
+
|
|
95
|
+
Started: [2026-05-04T00:00:00+04:00] {prov:startedAtTime ^^xsd:dateTime}
|
|
96
|
+
|
|
97
|
+
Aggregated activities and patterns for the week.
|
|
98
|
+
|
|
99
|
+
Started: [2026-05-06T23:00:00Z] {prov:startedAtTime ^^xsd:dateTime}
|
|
100
|
+
Ended: [2026-05-06T23:15:00Z] {prov:endedAtTime ^^xsd:dateTime}
|
|
101
|
+
|
|
102
|
+
### Activities Summary
|
|
103
|
+
Total activities: [6] {j:totalActivities ^^xsd:integer}
|
|
104
|
+
Reading time: [5] {j:readingHours ^^xsd:integer} hours
|
|
105
|
+
Work time: [8] {j:workHours ^^xsd:integer} hours
|
|
106
|
+
Exercise time: [3] {j:exerciseHours ^^xsd:integer} hours
|
|
107
|
+
|
|
108
|
+
### Goals Progress
|
|
109
|
+
Weekly goals: [Set on Monday] {j:weeklyGoals}
|
|
110
|
+
Completed: [4] {j:goalsCompleted ^^xsd:integer} out of 5
|
|
111
|
+
Carry over: [1] {j:goalsCarryOver ^^xsd:integer} goal
|
|
112
|
+
|
|
113
|
+
This demonstrates:
|
|
114
|
+
- Proper PROV-O activity chains
|
|
115
|
+
- Temporal properties with XSD
|
|
116
|
+
- Location and emotional tracking
|
|
117
|
+
- Activity aggregation and summarization
|
|
118
|
+
- Social interaction modeling
|
|
18
119
|
|
|
@@ -1,11 +1,23 @@
|
|
|
1
|
-
[my] <tag:alice@example.com,2026
|
|
1
|
+
[my] <tag:alice@example.com,2026:minimal/>
|
|
2
2
|
|
|
3
|
-
#
|
|
3
|
+
# Simple Note {=my:note .prov:Entity label}
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
DOI: [10.1234/ml.2024] {+https://doi.org/10.1234/ml.2024 ?my:doi}
|
|
5
|
+
This demonstrates basic MD-LD annotation patterns.
|
|
7
6
|
|
|
8
|
-
|
|
7
|
+
## Basic Properties
|
|
9
8
|
|
|
10
|
-
|
|
9
|
+
Title: [Hello World] {my:title}
|
|
10
|
+
Status: *draft* {my:status}
|
|
11
|
+
Priority: **medium** {my:priority}
|
|
12
|
+
|
|
13
|
+
## Typed Values
|
|
14
|
+
|
|
15
|
+
Created: `2026-05-06` {my:created ^^xsd:date}
|
|
16
|
+
Count: `42` {my:count ^^xsd:integer}
|
|
17
|
+
Rating: __4.5__ {my:rating ^^xsd:decimal}
|
|
18
|
+
Active: **true** {my:active ^^xsd:boolean}
|
|
19
|
+
|
|
20
|
+
## Simple Link
|
|
21
|
+
|
|
22
|
+
Related to: [Example Project] {+my:example-project ?my:relatedTo .prov:Project label}
|
|
11
23
|
|
|
@@ -1,15 +1,98 @@
|
|
|
1
1
|
[proj] <tag:alice@example.com,2026:project/>
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
# Website Redesign {=proj:website .prov:Project label}
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Website redesign project for Q2 2026 with modern responsive design.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
## Project Metadata {=proj:website-meta .prov:Entity label}
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
Budget: [$25,000] {proj:budget ^^xsd:decimal}
|
|
10
|
+
Start date: [2026-06-01] {proj:startDate ^^xsd:date}
|
|
11
|
+
End date: [2026-08-31] {proj:endDate ^^xsd:date}
|
|
12
|
+
Status: [planning] {proj:status}
|
|
10
13
|
|
|
11
|
-
|
|
14
|
+
## Team Formation Activity {=proj:team-formation .prov:Activity label}
|
|
12
15
|
|
|
13
|
-
|
|
16
|
+
Started: [2026-05-15T09:00:00Z] {prov:startedAtTime ^^xsd:dateTime}
|
|
17
|
+
Associated with: [Alice Johnson] {+proj:alice .prov:Person ?prov:wasAssociatedWith} as Project Manager
|
|
18
|
+
Plan: [Q2 Website Plan] {+proj:q2-plan .prov:Plan ?prov:hadPlan}
|
|
14
19
|
|
|
15
|
-
|
|
20
|
+
Generated: [Team Structure] {+proj:team-structure ?prov:generated}
|
|
21
|
+
|
|
22
|
+
## Team Members
|
|
23
|
+
|
|
24
|
+
### Project Manager {=proj:alice .prov:Person label}
|
|
25
|
+
|
|
26
|
+
Name: [Alice Johnson] {rdfs:label}
|
|
27
|
+
Email: [alice@example.com] {proj:email}
|
|
28
|
+
Role: [Project Manager] {proj:role}
|
|
29
|
+
|
|
30
|
+
### Lead Developer {=proj:bob .prov:Person label}
|
|
31
|
+
|
|
32
|
+
Name: [Bob Smith] {rdfs:label}
|
|
33
|
+
Email: [bob@example.com] {proj:email}
|
|
34
|
+
Role: [Lead Developer] {proj:role}
|
|
35
|
+
|
|
36
|
+
### UX Designer {=proj:carol .prov:Person label}
|
|
37
|
+
|
|
38
|
+
Name: [Carol Davis] {rdfs:label}
|
|
39
|
+
Email: [carol@example.com] {proj:email}
|
|
40
|
+
Role: [UX Designer] {proj:role}
|
|
41
|
+
|
|
42
|
+
## Project Tasks
|
|
43
|
+
|
|
44
|
+
### Design Phase {=proj:design-phase .prov:Activity label}
|
|
45
|
+
|
|
46
|
+
Started: [2026-06-01] {prov:startedAtTime ^^xsd:date}
|
|
47
|
+
Ended: [2026-06-15] {prov:endedAtTime ^^xsd:date}
|
|
48
|
+
|
|
49
|
+
Tasks:
|
|
50
|
+
- [User Research] {+proj:user-research .proj:Task ?prov:used} - interviews and surveys
|
|
51
|
+
- [Wireframes] {+proj:wireframes .proj:Task ?prov:used} - low-fidelity layouts
|
|
52
|
+
- [High-fidelity Mockups] {+proj:mockups .proj:Task ?prov:used} - detailed designs
|
|
53
|
+
|
|
54
|
+
Generated: [Design Documentation] {+proj:design-docs ?prov:generated}
|
|
55
|
+
|
|
56
|
+
### Development Phase {=proj:dev-phase .prov:Activity label}
|
|
57
|
+
|
|
58
|
+
Started: [2026-06-16] {prov:startedAtTime ^^xsd:date}
|
|
59
|
+
Ended: [2026-07-30] {prov:endedAtTime ^^xsd:date}
|
|
60
|
+
|
|
61
|
+
Tasks:
|
|
62
|
+
- [Frontend Development] {+proj:frontend .proj:Task ?prov:used} - React components
|
|
63
|
+
- [Backend API] {+proj:backend .proj:Task ?prov:used} - Node.js services
|
|
64
|
+
- [Database Schema] {+proj:database .proj:Task ?prov:used} - PostgreSQL design
|
|
65
|
+
|
|
66
|
+
Generated: [Working Prototype] {+proj:prototype ?prov:generated}
|
|
67
|
+
|
|
68
|
+
## Project Relationships
|
|
69
|
+
|
|
70
|
+
### Dependencies {=proj:dependencies .rdfs:Resource label}
|
|
71
|
+
|
|
72
|
+
The project depends on:
|
|
73
|
+
- [Design System] {+proj:design-system ?proj:requires}
|
|
74
|
+
- [API Documentation] {+proj:api-docs ?proj:requires}
|
|
75
|
+
|
|
76
|
+
### Stakeholders {=proj:stakeholders .rdfs:Resource label}
|
|
77
|
+
|
|
78
|
+
Key stakeholders:
|
|
79
|
+
- [Marketing Department] {+proj:marketing ?proj:stakeholder .prov:Organization}
|
|
80
|
+
- [Customer Support] {+proj:support ?proj:stakeholder .prov:Organization}
|
|
81
|
+
|
|
82
|
+
## Delegation Pattern
|
|
83
|
+
|
|
84
|
+
### Development Delegation {=proj:dev-delegation .prov:Delegation ?prov:qualifiedDelegation}
|
|
85
|
+
|
|
86
|
+
Alice delegates frontend development to specialized team.
|
|
87
|
+
|
|
88
|
+
Delegate: [Alice] {+proj:alice ?prov:delegate}
|
|
89
|
+
Responsible: [Frontend Team] {+proj:frontend-team .prov:Organization ?prov:responsible}
|
|
90
|
+
Activity: [Frontend Development] {+proj:frontend-dev .prov:Activity ?prov:hadActivity}
|
|
91
|
+
Role: [Development Lead] {+proj:dev-lead .prov:Role ?prov:hadRole}
|
|
92
|
+
|
|
93
|
+
This demonstrates:
|
|
94
|
+
- Complete PROV-O provenance chains
|
|
95
|
+
- Project lifecycle with phases
|
|
96
|
+
- Team formation and delegation
|
|
97
|
+
- Proper temporal properties
|
|
98
|
+
- Cross-ontology integration
|