- From: Stephen D Green <stephengreenubl@g...>
- To: Frank Steimke <f-steimke@b...>
- Date: Fri, 18 Feb 2022 07:35:51 +0000
The Open World assumption is indeed a problem. You can remove an OWL ontology from a reasoner, when it is out of date. Is that enough? In a real world scenario with GDPR, etcetera, we need to make facts expire or replace old facts with new ones. If I circulate an ontology in a business world such as public procurement, and then publish a new component of that ontology, how can I be sure that everyone has implemented it by a certain date when the previous version becomes invalid?
Valid points. But how does it all compare to no ontologies at all, just tacit or implicit assumptions?
The topics of the sematic web are still relatively new to me. I
am trying to understand the different standards and technologies.
I came across two articles that are very skeptical about OWL, and
recommend SHACL instead.
* Why I Don’t Use OWL Anymore www.topquadrant.com/owl-blog/
* Why I Use SHACL For Defining Ontology Models www.topquadrant.com/shacl-blog/
Since i have no own experience, i am unable to make a judgement
yet. What do you think about the critical statements about OWL?
Frank Steimke
Am 17.02.22 um 10:23 schrieb Stephen D
Green:
Why RDF? Why not OWL?
On Thu, 17 Feb 2022 at
09:09, Hans-Juergen Rennau < hrennau@y...>
wrote:
A very interesting point, which I read
as this: if you take responsibility for large-scale
data modeling, think twice before daring to do it
without being backed by an RDF view of the things you
are dealing with.
Large-scale data modeling is, of course,
the work of a very small group of people. On the other
hand, what is of immediate and practical importance
for a major part of development work is APIs. As you
did not mention them, I suppose there are no important
NIEM-related APIs which are based on RDF. If indeed
not, this would even be a little surprising - could
not graph patterns be important for users of NIEM
encoded data?
Am Mittwoch, 16. Februar 2022, 23:46:18 MEZ hat
Webb Roberts < webb@w...>
Folgendes geschrieben:
On Feb 15, 2022, at 05:16, Hans-Juergen
Rennau < hrennau@y...>
wrote:
Thank you, Webb. One
question: was the alignment of XML
and RDF important for the use
of the data? Such importance can be
easily imagined - e.g. graph queries
revealing patterns difficult to
detect without a graph
representation - but if it has been
actually experienced is of course a
different question.
I would say that NIEM's alignment
between XML and RDF is *very* important
for use of the data.
XML and XML Schema don't address a lot
of issues fundamental to understanding
data. What does a block of XML mean? What
does type extension mean? What does an
element containing another element mean?
By defining the interpretation of NIEM
data based on RDF, we get a real semantic
model that explains a lot about the
meaning of any given block of data.
But a lot of people don't care about
that level of detail about the meaning of
data — it's too philosophical, too
esoteric.
For them, the XML data looks like a
straightforward use of XML - elements with
sub-elements, types with base types,
IDREFs linking to IDs - all clearly named
and not too hard to understand.
However, the rigor that the XML–RDF
alignment provided helped to ensure that a
lot of things were done in a consistent
manner across a very large number of data
definitions. And that diligence helps make
a big pile of data understandable. The
alignment to RDF benefits everyone who
uses it, even those who don't care at all
about RDF.
--
--
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
|