-
Notifications
You must be signed in to change notification settings - Fork 0
/
003004.html
221 lines (208 loc) · 12.5 KB
/
003004.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
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE> [open-linguistics] Defining "Openness" for Linguistic Linked Open Data
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:open-linguistics%40lists.okfn.org?Subject=Re%3A%20%5Bopen-linguistics%5D%20Defining%20%22Openness%22%20for%20Linguistic%20Linked%0A%09Open%20Data&In-Reply-To=%3CCA%2BarSXjaqHPxmOu5Ci2rn4%3DZrMfj1MbGkqc%2BoT0uu4uPDTk3hg%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<style type="text/css">
pre {
white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */
}
</style>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="003003.html">
<LINK REL="Next" HREF="003006.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[open-linguistics] Defining "Openness" for Linguistic Linked Open Data</H1>
<B>Francis Bond</B>
<A HREF="mailto:open-linguistics%40lists.okfn.org?Subject=Re%3A%20%5Bopen-linguistics%5D%20Defining%20%22Openness%22%20for%20Linguistic%20Linked%0A%09Open%20Data&In-Reply-To=%3CCA%2BarSXjaqHPxmOu5Ci2rn4%3DZrMfj1MbGkqc%2BoT0uu4uPDTk3hg%40mail.gmail.com%3E"
TITLE="[open-linguistics] Defining "Openness" for Linguistic Linked Open Data">bond at ieee.org
</A><BR>
<I>Wed Jan 17 12:29:54 UTC 2018</I>
<P><UL>
<LI>Previous message: <A HREF="003003.html">[open-linguistics] Defining "Openness" for Linguistic Linked Open Data
</A></li>
<LI>Next message: <A HREF="003006.html">[open-linguistics] Defining "Openness" for Linguistic Linked Open Data
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3004">[ date ]</a>
<a href="thread.html#3004">[ thread ]</a>
<a href="subject.html#3004">[ subject ]</a>
<a href="author.html#3004">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>G'day,
I think it is very misleading to have a diagram called Linked Open Data
cloud if it is not in fact comprised of linked open data. We have a
simple solution: create two diagrams: (Linguistic) Linked Data which allows
all linked data and (Linguistic) Linked Open Data, for data that is open
according to the open definition. That way everyone can have what they
want :-). The two resources can link to each other somewhere in their
descriptions to make them both easily accessible.
As Victor pointed out, you need to be open to be LOD. I quote from [1]
"You can have 5-star Linked Data without it being open. However, if it
claims to be Linked Open Data then it does have to be open, to get any star
at all."
[1] <A HREF="https://www.w3.org/DesignIssues/LinkedData.html">https://www.w3.org/DesignIssues/LinkedData.html</A>
Yours,
On Wed, Jan 17, 2018 at 6:09 PM, Víctor Rodríguez Doncel <
<A HREF="https://lists.okfn.org/mailman/listinfo/open-linguistics">vrodriguez at fi.upm.es</A>> wrote:
><i> Dear Christian,
</I>><i>
</I>><i> Even if the very first star of the high-quality "5 star linked data" [1]
</I>><i> imposes that license must be open, there are some people who would like to
</I>><i> soften this requirement, making the O in LOD to simply mean "open format".
</I>><i> Furthermore, the European Union is striving towards establishing data
</I>><i> markets, where obviously licenses cannot be open and where linked data may
</I>><i> play a role (see how they are actively funding, right now, such research
</I>><i> projects).
</I>><i>
</I>><i> In my opinion, limiting the LLOD to strictly open datasets is a mistake,
</I>><i> as it would depict a reality only partially. The webpage at
</I>><i> <A HREF="http://linguistic-lod.org/llod-cloud">http://linguistic-lod.org/llod-cloud</A> already displays the cloud by
</I>><i> license; I cannot possibly imagine how to improve that...
</I>><i>
</I>><i> Regards,
</I>><i> Víctor
</I>><i>
</I>><i>
</I>><i> [1] <A HREF="https://www.w3.org/DesignIssues/LinkedData.html">https://www.w3.org/DesignIssues/LinkedData.html</A>
</I>><i>
</I>><i> [2] ICT-13-2018-2019: Supporting the emergence of data markets and the
</I>><i> data economy
</I>><i> <A HREF="https://ec.europa.eu/research/participants/portal/desktop/en">https://ec.europa.eu/research/participants/portal/desktop/en</A>
</I>><i> /opportunities/h2020/topics/ict-13-2018-2019.html
</I>><i>
</I>><i> El 16/01/2018 a las 13:32, Christian Chiarcos escribió:
</I>><i>
</I>>><i> Dear all,
</I>>><i>
</I>>><i> when we first began developing the Linguistic Linked Open Data cloud
</I>>><i> diagram, we followed a highly permissive approach on criteria for
</I>>><i> inclusion, with the idea to move if from an abstract vision to a set of
</I>>><i> actually usable resources -- in fact the first versions of the diagram
</I>>><i> (before the MLODE workshop in September 2012) are explicitly referred to as
</I>>><i> "drafts" because we included resources whose conversion to LOD had only
</I>>><i> been *promised* the time.
</I>>><i>
</I>>><i> However, the quality criteria have been continuously enforced since then.
</I>>><i> This includes availability, size, number of links, and an explicit
</I>>><i> definition of linguistic relevance as an entry criterion, so that these are
</I>>><i> now roughly equivalent with the LOD criteria.
</I>>><i>
</I>>><i> Along with that, we did *not* enforce an Open Definition-conformant
</I>>><i> license (<A HREF="http://opendefinition.org/licenses/">http://opendefinition.org/licenses/</A>). In particular, arguments
</I>>><i> have been brought forward to include non-commercial resources. One of the
</I>>><i> reasons is that many classical resources developed during the 1990s and
</I>>><i> early 2000s are released under "academic" licenses and that even today,
</I>>><i> entire sub-communities in linguistics tend to be very protective about
</I>>><i> their data. Encouraging noncommercial licenses is a viable compromise to
</I>>><i> reach out to these communities without compromising the idea of embracing
</I>>><i> openness altogether. We did have discussions about this from the very
</I>>><i> beginning, and there are good arguments for either view, but we did *not*
</I>>><i> manage to establish a consensus to exclude, in particular, NC-licensed data.
</I>>><i>
</I>>><i> For the moment, openness is (implicitly) defined as being in line with
</I>>><i> the LOD diagram, i.e., we inherit its view that "we take a liberal view of
</I>>><i> what we consider “open”. If the data is openly accessible from a network
</I>>><i> point of view – that is, it's not behind an authorization check or paywall"
</I>>><i> (<A HREF="http://lod-cloud.net/">http://lod-cloud.net/</A>). This approach can be criticized for good
</I>>><i> reasons, but it is an established and transparent practice that goes back
</I>>><i> to the original LOD diagram by Cyganiak and Jentzsch, and that has also
</I>>><i> been documented since then.
</I>>><i>
</I>>><i> Part of this documentation is that under <A HREF="http://linguistic-lod.org/llod">http://linguistic-lod.org/llod</A>
</I>>><i> -cloud, users can get an alternative visualization of the diagram with
</I>>><i> respect to licenses, and as can be easily seen, about half of the LLOD
</I>>><i> bubbles are non-commercial, three have no explicit license (which means a
</I>>><i> restrictive license, in Germany, at least), and three more are labeled as
</I>>><i> "closed" (which may in fact mean that different sub-resources have
</I>>><i> different licenses, e.g., Multext-East[<A HREF="http://nl.ijs.si/ME/V4/">http://nl.ijs.si/ME/V4/</A>], which
</I>>><i> includes CC-BY-SA and CC-BY-NC lexica as well as corpus data under a
</I>>><i> restricted/non-commercial license).
</I>>><i>
</I>>><i> However, this can be a problem for data providers who find their NC data
</I>>><i> in the (L)LOD diagram without being "Open" according to the Open
</I>>><i> Definition, as users of this data may get a wrong impression about their
</I>>><i> usage rights -- despite warnings such as "Before using any data, you should
</I>>><i> always check the publisher's website for the terms and conditions" (
</I>>><i> <A HREF="http://lod-cloud.net/">http://lod-cloud.net/</A>).
</I>>><i>
</I>>><i> The question now is what to do about this situation. Personally, I would
</I>>><i> prefer to roughly stay with the current practice for the LOD and LLOD
</I>>><i> diagrams for the moment, but to provide an explicit statement that *our*
</I>>><i> definition of openness exceeds beyond the Open Definition by including
</I>>><i> non-commercial/"academic" resources, because this is an explicit need in
</I>>><i> (parts of) our community. At the same time, given such a statement,
</I>>><i> resources with unclear (= restrictive) licenses should be removed from the
</I>>><i> diagram. As these are quantitatively marginal anyway, this should not
</I>>><i> affect the usability of LLOD resources and the diagram in comparison to its
</I>>><i> current state.
</I>>><i>
</I>>><i> In any case, this is for the immediate future only. At some point in the
</I>>><i> future, after intense lobbying among our peers and (hopefully) growing
</I>>><i> imporance of OpenDefinition-compliant licenses, we should certainly adopt a
</I>>><i> stricter definition, but for the moment, the growth in resources,
</I>>><i> demonstrating their use and developing applications of (L)LOD should --
</I>>><i> IMHO -- take priority over ideological purity until it is established as a
</I>>><i> conventional approach for (certain kinds of) linguistic data.
</I>>><i>
</I>>><i> This may be controversial, though, so, what do others think?
</I>>><i>
</I>>><i> Best,
</I>>><i> Christian
</I>>><i>
</I>><i>
</I>><i>
</I>><i> --
</I>><i> Víctor Rodríguez-Doncel
</I>><i> D3205 - Ontology Engineering Group (OEG)
</I>><i> Departamento de Inteligencia Artificial
</I>><i> ETS de Ingenieros Informáticos
</I>><i> Universidad Politécnica de Madrid
</I>><i>
</I>><i> Campus de Montegancedo s/n
</I>><i> Boadilla del Monte-28660 Madrid, Spain
</I>><i> Tel. (+34) 91336 3672
</I>><i> Skype: vroddon3
</I>><i>
</I>><i>
</I>><i> _______________________________________________
</I>><i> open-linguistics mailing list
</I>><i> <A HREF="https://lists.okfn.org/mailman/listinfo/open-linguistics">open-linguistics at lists.okfn.org</A>
</I>><i> <A HREF="https://lists.okfn.org/mailman/listinfo/open-linguistics">https://lists.okfn.org/mailman/listinfo/open-linguistics</A>
</I>><i> Unsubscribe: <A HREF="https://lists.okfn.org/mailman/options/open-linguistics">https://lists.okfn.org/mailman/options/open-linguistics</A>
</I>><i>
</I>
--
Francis Bond <<A HREF="http://www3.ntu.edu.sg/home/fcbond/">http://www3.ntu.edu.sg/home/fcbond/</A>>
Division of Linguistics and Multilingual Studies
Nanyang Technological University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <<A HREF="http://lists.okfn.org/pipermail/open-linguistics/attachments/20180117/ee276c49/attachment-0002.html">http://lists.okfn.org/pipermail/open-linguistics/attachments/20180117/ee276c49/attachment-0002.html</A>>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="003003.html">[open-linguistics] Defining "Openness" for Linguistic Linked Open Data
</A></li>
<LI>Next message: <A HREF="003006.html">[open-linguistics] Defining "Openness" for Linguistic Linked Open Data
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3004">[ date ]</a>
<a href="thread.html#3004">[ thread ]</a>
<a href="subject.html#3004">[ subject ]</a>
<a href="author.html#3004">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://lists.okfn.org/mailman/listinfo/open-linguistics">More information about the open-linguistics
mailing list</a><br>
</body></html>