mustrd 0.2.3__tar.gz → 0.2.5__tar.gz

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 (30) hide show
  1. {mustrd-0.2.3 → mustrd-0.2.5}/PKG-INFO +13 -20
  2. mustrd-0.2.3/README.adoc → mustrd-0.2.5/README.md +11 -18
  3. {mustrd-0.2.3 → mustrd-0.2.5}/pyproject.toml +2 -2
  4. {mustrd-0.2.3 → mustrd-0.2.5}/LICENSE +0 -0
  5. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/README.md +0 -0
  6. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/TestResult.py +0 -0
  7. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/__init__.py +0 -0
  8. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/logger_setup.py +0 -0
  9. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/model/catalog-v001.xml +0 -0
  10. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/model/mustrdShapes.ttl +0 -0
  11. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/model/mustrdTestOntology.ttl +0 -0
  12. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/model/mustrdTestShapes.ttl +0 -0
  13. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/model/ontology.ttl +0 -0
  14. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/model/test-resources/resources.ttl +0 -0
  15. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/model/triplestoreOntology.ttl +0 -0
  16. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/model/triplestoreshapes.ttl +0 -0
  17. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/mustrd.py +0 -0
  18. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/mustrdAnzo.py +0 -0
  19. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/mustrdGraphDb.py +0 -0
  20. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/mustrdRdfLib.py +0 -0
  21. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/mustrdTestPlugin.py +0 -0
  22. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/namespace.py +0 -0
  23. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/run.py +0 -0
  24. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/spec_component.py +0 -0
  25. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/steprunner.py +0 -0
  26. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/templates/md_ResultList_leaf_template.jinja +0 -0
  27. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/templates/md_ResultList_template.jinja +0 -0
  28. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/templates/md_stats_template.jinja +0 -0
  29. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/test/test_mustrd.py +0 -0
  30. {mustrd-0.2.3 → mustrd-0.2.5}/mustrd/utils.py +0 -0
{mustrd-0.2.3 → mustrd-0.2.5}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.1
2
2
  Name: mustrd
3
- Version: 0.2.3
3
+ Version: 0.2.5
4
4
  Summary: A Spec By Example framework for RDF and SPARQL, Inspired by Cucumber.
5
5
  Home-page: https://github.com/Semantic-partners/mustrd
6
6
  License: MIT
@@ -37,44 +37,43 @@ Requires-Dist: toml (>=0.10.2,<0.11.0)
37
37
  Requires-Dist: tomli (>=2.0.1,<3.0.0)
38
38
  Requires-Dist: urllib3 (==1.26.19)
39
39
  Project-URL: Repository, https://github.com/Semantic-partners/mustrd
40
- Description-Content-Type: text/plain
40
+ Description-Content-Type: text/markdown
41
41
 
42
- == Mustrd
42
+ # mustrd
43
43
 
44
- // tag::body[]
45
44
 
46
45
  image::https://github.com/Semantic-partners/mustrd/raw/python-coverage-comment-action-data/badge.svg[Coverage badge,link="https://github.com/Semantic-partners/mustrd/tree/python-coverage-comment-action-data"]
47
46
 
48
- === Why?
47
+ ### Why?
49
48
 
50
49
  How do you know your SPARQL, whether it's in a pipeline, or a query, is doing what you intend?
51
50
 
52
- As much as we love RDF and SPARQL and Semantic Tech in general, we found a small gap in tooling which would give us that certainty.
51
+ As much as we love RDF and SPARQL and Semantic Tech in general, we found a small gap in tooling to give us that certainty.
53
52
 
54
53
  We missed the powerful testing frameworks that have evolved in imperative languages that help ensure you've written code that does what you think it should.
55
54
 
56
- We wanted to be able to:
55
+ We wanted to be able to
57
56
 
58
57
  * setup data scenarios and ensure queries worked as expected
59
58
  * setup edge cases for queries and ensure they still work
60
- * isolate small sparql enrichment / transformation steps and to know we're only INSERTing what we intend
59
+ * isolate small sparql enrichment / transformation steps and know we're only INSERTing what we intend
61
60
 
62
61
  Enter MustRD.
63
62
 
64
- === What?
63
+ ### What?
65
64
 
66
65
  MustRD is a Spec-By-Example ontology, with a reference python implementation, inspired by the likes of Cucumber.
67
66
 
68
67
  It's designed to be triplestore/SPARQL engine agnostic (aren't open standards *wonderful*!).
69
68
 
70
- === What it is NOT
69
+ ### What it is NOT
71
70
  MustRD is nothing to do with SHACL, or an alternative to it. In fact, we use SHACL for some of our features.
72
71
 
73
72
  SHACL provides validation around data.
74
73
 
75
74
  MustRD provides validation around data transformations.
76
75
 
77
- === How?
76
+ ### How?
78
77
  You define your specs in ttl, or trig files.
79
78
  We use the SBE approach of *Given*, *When*, *Then* to define starting dataset, an action, and a set of expectations. We build up a set of data.
80
79
  Then, depending on whether your SPARQL is a CONSTRUCT, SELECT or a INSERT/DELETE, we run it, and compare results against a set of expectations (*Then*) that are defined in the same way as a *Given* .
@@ -85,20 +84,14 @@ Alternatively, you could define your *Then*
85
84
  * in a higher-order expectation language like you will be used to in various platforms, a set of expectations.
86
85
 
87
86
 
88
- === When?
87
+ ### When?
89
88
 
90
89
  Soon. It's a work in progress, and we're building the things *we* need for the projects we work on at multiple clients, with multiple vendor stacks.
91
90
  We already think it's useful, but it might not meet *your* needs, out of the box.
92
91
 
93
92
  We invite you to try it, see where it doesn't fit, and raise an issue, or even better, a PR! If you need something custom, please check out our consultancy rates, and we might be able to prioritise a new feature for you.
94
93
 
95
- == Support
96
- We're a specialist consultancy in Semantic Tech, we're putting this out in case it's useful, but if you need more support, kindly contact our business team on info@semanticpartners.com
94
+ ## Support
95
+ We're a specialist consultancy in Semantic Tech, we're putting this out in case it's useful, but if you need more support, kindly contact our business team on info@semanticpartners.com, or mustrd@semanticpartners.com
97
96
 
98
- // tag::body[]
99
-
100
- include::GETSTARTED.adoc[Get started]
101
-
102
- Developer doc:
103
- include::mustrd/README.adoc[tags=body]
104
97
 
mustrd-0.2.3/README.adoc → mustrd-0.2.5/README.md RENAMED
@@ -1,39 +1,38 @@
1
- == Mustrd
1
+ # mustrd
2
2
 
3
- // tag::body[]
4
3
 
5
4
  image::https://github.com/Semantic-partners/mustrd/raw/python-coverage-comment-action-data/badge.svg[Coverage badge,link="https://github.com/Semantic-partners/mustrd/tree/python-coverage-comment-action-data"]
6
5
 
7
- === Why?
6
+ ### Why?
8
7
 
9
8
  How do you know your SPARQL, whether it's in a pipeline, or a query, is doing what you intend?
10
9
 
11
- As much as we love RDF and SPARQL and Semantic Tech in general, we found a small gap in tooling which would give us that certainty.
10
+ As much as we love RDF and SPARQL and Semantic Tech in general, we found a small gap in tooling to give us that certainty.
12
11
 
13
12
  We missed the powerful testing frameworks that have evolved in imperative languages that help ensure you've written code that does what you think it should.
14
13
 
15
- We wanted to be able to:
14
+ We wanted to be able to
16
15
 
17
16
  * setup data scenarios and ensure queries worked as expected
18
17
  * setup edge cases for queries and ensure they still work
19
- * isolate small sparql enrichment / transformation steps and to know we're only INSERTing what we intend
18
+ * isolate small sparql enrichment / transformation steps and know we're only INSERTing what we intend
20
19
 
21
20
  Enter MustRD.
22
21
 
23
- === What?
22
+ ### What?
24
23
 
25
24
  MustRD is a Spec-By-Example ontology, with a reference python implementation, inspired by the likes of Cucumber.
26
25
 
27
26
  It's designed to be triplestore/SPARQL engine agnostic (aren't open standards *wonderful*!).
28
27
 
29
- === What it is NOT
28
+ ### What it is NOT
30
29
  MustRD is nothing to do with SHACL, or an alternative to it. In fact, we use SHACL for some of our features.
31
30
 
32
31
  SHACL provides validation around data.
33
32
 
34
33
  MustRD provides validation around data transformations.
35
34
 
36
- === How?
35
+ ### How?
37
36
  You define your specs in ttl, or trig files.
38
37
  We use the SBE approach of *Given*, *When*, *Then* to define starting dataset, an action, and a set of expectations. We build up a set of data.
39
38
  Then, depending on whether your SPARQL is a CONSTRUCT, SELECT or a INSERT/DELETE, we run it, and compare results against a set of expectations (*Then*) that are defined in the same way as a *Given* .
@@ -44,19 +43,13 @@ Alternatively, you could define your *Then*
44
43
  * in a higher-order expectation language like you will be used to in various platforms, a set of expectations.
45
44
 
46
45
 
47
- === When?
46
+ ### When?
48
47
 
49
48
  Soon. It's a work in progress, and we're building the things *we* need for the projects we work on at multiple clients, with multiple vendor stacks.
50
49
  We already think it's useful, but it might not meet *your* needs, out of the box.
51
50
 
52
51
  We invite you to try it, see where it doesn't fit, and raise an issue, or even better, a PR! If you need something custom, please check out our consultancy rates, and we might be able to prioritise a new feature for you.
53
52
 
54
- == Support
55
- We're a specialist consultancy in Semantic Tech, we're putting this out in case it's useful, but if you need more support, kindly contact our business team on info@semanticpartners.com
53
+ ## Support
54
+ We're a specialist consultancy in Semantic Tech, we're putting this out in case it's useful, but if you need more support, kindly contact our business team on info@semanticpartners.com, or mustrd@semanticpartners.com
56
55
 
57
- // tag::body[]
58
-
59
- include::GETSTARTED.adoc[Get started]
60
-
61
- Developer doc:
62
- include::mustrd/README.adoc[tags=body]
{mustrd-0.2.3 → mustrd-0.2.5}/pyproject.toml RENAMED
@@ -1,6 +1,6 @@
1
1
  [tool.poetry]
2
2
  name = "mustrd"
3
- version = "0.2.3"
3
+ version = "0.2.5"
4
4
  description = "A Spec By Example framework for RDF and SPARQL, Inspired by Cucumber."
5
5
  authors = ["John Placek <john.placek@semanticpartners.com>",
6
6
  "Juliane Piñeiro-Winkler <juliane.pineiro-winkler@semanticpartners.com>",
@@ -15,7 +15,7 @@ classifiers = [
15
15
  "Topic :: Software Development :: Testing",
16
16
  "Topic :: Utilities",
17
17
  ]
18
- readme = "README.adoc"
18
+ readme = "README.md"
19
19
  license = "MIT License"
20
20
  repository = "https://github.com/Semantic-partners/mustrd"
21
21
 
{mustrd-0.2.3 → mustrd-0.2.5}/LICENSE RENAMED
File without changes
{mustrd-0.2.3 → mustrd-0.2.5}/mustrd/README.md RENAMED
File without changes
{mustrd-0.2.3 → mustrd-0.2.5}/mustrd/TestResult.py RENAMED
File without changes
{mustrd-0.2.3 → mustrd-0.2.5}/mustrd/__init__.py RENAMED
File without changes
{mustrd-0.2.3 → mustrd-0.2.5}/mustrd/logger_setup.py RENAMED
File without changes
{mustrd-0.2.3 → mustrd-0.2.5}/mustrd/model/ontology.ttl RENAMED
File without changes
{mustrd-0.2.3 → mustrd-0.2.5}/mustrd/mustrd.py RENAMED
File without changes
{mustrd-0.2.3 → mustrd-0.2.5}/mustrd/mustrdAnzo.py RENAMED
File without changes
{mustrd-0.2.3 → mustrd-0.2.5}/mustrd/mustrdGraphDb.py RENAMED
File without changes
{mustrd-0.2.3 → mustrd-0.2.5}/mustrd/mustrdRdfLib.py RENAMED
File without changes
{mustrd-0.2.3 → mustrd-0.2.5}/mustrd/namespace.py RENAMED
File without changes
{mustrd-0.2.3 → mustrd-0.2.5}/mustrd/run.py RENAMED
File without changes
{mustrd-0.2.3 → mustrd-0.2.5}/mustrd/spec_component.py RENAMED
File without changes
{mustrd-0.2.3 → mustrd-0.2.5}/mustrd/steprunner.py RENAMED
File without changes
{mustrd-0.2.3 → mustrd-0.2.5}/mustrd/utils.py RENAMED
File without changes