-
Notifications
You must be signed in to change notification settings - Fork 2
/
bookHtml003.html
75 lines (68 loc) · 3.98 KB
/
bookHtml003.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="generator" content="hevea 2.23">
<link rel="stylesheet" type="text/css" href="book.css"><link rel="stylesheet" type="text/css" href="bookHtml.css">
<title>Foreword by Phil Archer</title>
</head>
<body>
<a href="bookHtml002.html"><img src="previous_motif.gif" alt="Previous"></a>
<a href="index.html"><img src="contents_motif.gif" alt="Up"></a>
<a href="bookHtml004.html"><img src="next_motif.gif" alt="Next"></a>
<hr>
<header>
<a href="http://book.validatingrdf.com">Validating RDF data</a>
<img src="cover.jpg"></img>
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-112019120-1"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-112019120-1');
</script>
</header>
<h1 class="chapter" id="sec7">Foreword by Phil Archer</h1>
<p>“Anyone can say anything about anything,” says the mantra for the
Semantic Web. More formally, the Semantic Web adopts the Open World
Assumption: just because your data encodes a set of facts, that doesn’t
mean there aren’t other facts stated elsewhere about the same thing.
All of which is fine and part of the design of RDF which supports the
creation of a graph at Web scale, but in a lot of practical
applications you just need to know whether the triples you’ve ingested
match what you were expecting; you need validation. You might think of
it as a defined subset of the whole graph, or maybe a profile,
providing a huge boost to interoperability between disparate systems.
If you can validate the data you’ve received then you can process it
with confidence, using more terse code, perhaps with more performant
queries. I don’t accept that RDF is hard, certainly no harder than any
other Web technology; what is hard is thinking in graphs. Keeping in
your head that this node supports these properties and has
relationships with those other nodes becomes complex for anything other
than trivial datasets. The validation techniques set out in this book
provide a means to tame that complexity, to set out for humans and
machines exactly what the structure of the data is or should be. That’s
got to be helpful and, incidentally, ties in with new work now under
way at W3C on dataset exchange. In my role at W3C I watched as the
SHACL and ShEx camps tried hard to converge on a single method: they
couldn’t, hence the two different approaches. Both are described in
detail here with copious examples, which is just what you need to get
started. How can you choose between the two methods? Chapter <a href="bookHtml013.html#ch7">7</a> gives a
detailed comparison and allows you to make your own choice. Whichever
you choose, this is the book you need to make sense of RDF validation.</p><p><br>
<br>
Phil Archer, Former W3C Data Strategist<br>
July 2017</p><footer>
<iframe src="https://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fbook.validatingrdf.com%2F&width=100&layout=standard&action=like&size=small&show_faces=true&share=true&height=80&appId=8170400788" width="100" height="80" style="border:none;overflow:hidden" scrolling="no" frameborder="0" allowTransparency="true"></iframe>
<a class="twitter-share-button" text="Validating RDF data book" href="https://twitter.com/intent/tweet?text=Validating%20RDF%20data%20book&?via=jelabra&hastags=shex,shacl,validatingrdfbook" data-size="large">Tweet</a>
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
<!-- Go to www.addthis.com/dashboard to customize your tools -->
<script type="text/javascript" src="//s7.addthis.com/js/300/addthis_widget.js#pubid=ra-5a51d2b6b0d22f0a"></script>
</footer>
<hr>
<a href="bookHtml002.html"><img src="previous_motif.gif" alt="Previous"></a>
<a href="index.html"><img src="contents_motif.gif" alt="Up"></a>
<a href="bookHtml004.html"><img src="next_motif.gif" alt="Next"></a>
</body>
</html>