Это видео недоступно.
Сожалеем об этом.
HTML-код
- Опубликовано: 28 окт 2020
- This is the first part of a three-part lecture that introduces RDF. To get started, we learn about the basic shape of RDF graphs and cover some technicalities related to the use of IRIs as identifiers in RDF.
► Lecture slides for download: iccl.inf.tu-dresden.de/web/KG... (Lecture 2)
► Related problem sheet to test your knowledge: Exercise 1
► Current and previous versions of the lecture: iccl.inf.tu-dresden.de/web/Kn...
Very comprehensive. Thank you!
In the example of Coffee the verb part "born in" could have multiples answers. I ask if would be a better expression for restrict the answer (concept). I saw an example about using Neo4j that the matter was basket ball players and an interesting example: "A PLAYER" "played for" "A team". and the "played for" had an attribute of "contract value" and this attributes lives on the link and not on the node. I had never saw that and would like when it is a case of putting attributes on links and when put on nodes. Does exist some king of normalization?
Especially like the coffee filter example graph! 🙂 And for the first time ever, I saw the *real* purpose of # anchor chars in IRIs explained. Even the RDF(S) specifications simply use them without explaining this background. Great!
😃Very interesting lecture
Thanks Professor, very informative lecture
absolutely fantastic
Dankeschön :)
Geile Vorlesung Prof!
I love the topic and the presentation seems thorough. However, as someone with background in programming, it feels a bit long winded, and I think that introducing the RDF prefixes earlier would have made the slides easier to read.
Creating IRIs, are point 4 and 5 contradictory? Don't use http(s) unless there is a real webpage on the url. Otherwise use none as the scheme?
Or skip the iri grap and simply use the package name thing from Java.
At the top level there could be one namespace, so labels are short and human readable.