see Comments Magnus below
Gustav II Adolf
- see also blogpost metadatacheck-kulturnavorg
Some of the best examples in K-samsök come from LSH. Let's take Gustav II Adolf as an example:— Marcus Smith (@carwash) October 25, 2019
Kringla: https://t.co/cjtbz6Zgy8
URI: https://t.co/0KVdJPrQNY
Links: https://t.co/qA9beDbdP4
Moar links: https://t.co/0cNvJuy0rn
Below some comments from me Magnus and I feel I see too many strings i.e. this is no good metadata and has to be redone. Things you lose not having Linked data
- Easy translation
- Easy way of explaining e.g. birth location Stockholms slott as you cant easy tell this is same as Wikidata Q750444
- you get no relation to Wikipedia articles in > 30 languages link
- People doing research will have a problem finding objects with just strings.
See workshop in Uppsala were I was sitting with domain experts and identified all locations in the text with same as example - string Tegian
same as - pleiades.stoa.org/places/570707
- which means we can understand it is same as
- Q645234 same as
- alvin-place:5645
- By having strings for locations you cant generate maps easy. Compare the result of how a book page annotated with locations can be displayed on a map
<?xml version="1.0" encoding="utf-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:ns0="http://kulturarvsdata.se/ksamsok#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:ns1="http://purl.org/vocab/bio/0.1/"
xmlns:ns2="http://www.cidoc-crm.org/rdfs/cidoc-crm#P12B.">
<rdf:Description rdf:about="http://kulturarvsdata.se/LSH/agents/9534">
<rdf:type rdf:resource="http://kulturarvsdata.se/ksamsok#Entity"/>
<ns0:ksamsokVersion>1.1</ns0:ksamsokVersion>
<ns0:serviceName>agents</ns0:serviceName>
<ns0:mediaType>text/html</ns0:mediaType>
<ns0:itemLicense rdf:resource="http://kulturarvsdata.se/resurser/License#cc0"/>
<ns0:itemLicenseUrl rdf:resource="http://creativecommons.org/publicdomain/zero/1.0/"/>
<ns0:url>http://emuseumplus.lsh.se/eMuseumPlus?service=ExternalInterface&module=artist&objectId=9534&viewType=detailView</ns0:url>
<ns0:dataQuality rdf:resource="http://kulturarvsdata.se/resurser/DataQuality#raw"/>
<ns0:serviceOrganization>LSH</ns0:serviceOrganization>
<ns0:buildDate>2019-03-12</ns0:buildDate>
<ns0:createdDate>2010-02-15</ns0:createdDate>
<ns0:lastChangedDate>2016-08-23</ns0:lastChangedDate>
<ns0:itemSuperType rdf:resource="http://kulturarvsdata.se/resurser/EntitySuperType#agent"/>
<ns0:itemType rdf:resource="http://kulturarvsdata.se/resurser/EntityType#person"/>
<ns0:itemLabel>Gustav II Adolf av Sverige</ns0:itemLabel>
Comment 1 Magnus: No language tag as we speak about museums I think we should have systems we should support the most spoken languages in Sweden like Arabic, Somalia... etc... and maybe also for tourists chinese....
<foaf:fullName>Gustav II Adolf av Sverige</foaf:fullName>
Comment 2 Magnus: kung is string not things compare Wikidata
Q12097
By using strings we lose
1) Possibility to translate in an easy way e.g. Wikidata has King in xxx number languages like thai
พระราชา, chinese 王 , japanese 王, somali language Boqortooyo
2) Not having things and same as WD you will have no easy way of explaing the word compare using THINGS same as Wikidata and link you have articles in 95 languages Q12097#sitelinks-wikipedia
3) If other tools should do a search they have to understand that you have used Word "kung" in this field instead of saying give me all objects with title same as Q12097
<foaf:title>kung</foaf:title>
<foaf:name>Gustaf II Adolf</foaf:name>
<foaf:name>Gustavus Adolphus Magnus</foaf:name>
<foaf:name>Lejonet från Norden - der Löwe aus der Mitternacht</foaf:name>
<foaf:name>GIIA</foaf:name>
<foaf:name>Gustavus Adolphus</foaf:name>
<foaf:gender>M</foaf:gender>
Comment 3 Magnus: M is also string not things
<ns0:nameId>9534</ns0:nameId>
<ns0:nameAuth>LSH</ns0:nameAuth>
<ns0:isDescribedBy rdf:resource="http://sv.wikipedia.org/wiki/Gustaf_II_Adolf"/>
Comment 4 Magnus: Minor comment would like to see Wikidata Q number used as is more stable. Articles in Wikipedia gets new names....
<ns1:parent rdf:resource="http://kulturarvsdata.se/LSH/agents/16107"/>
<ns1:parent rdf:resource="http://kulturarvsdata.se/LSH/agents/16565"/>
<ns1:child rdf:resource="http://kulturarvsdata.se/LSH/agents/7140"/>
<ns1:child rdf:resource="http://kulturarvsdata.se/LSH/agents/12098"/>
<ns2:was_present_at rdf:resource="http://kulturarvsdata.se/LSH/events/858"/>
<ns2:was_present_at rdf:resource="http://kulturarvsdata.se/LSH/events/2708"/>
<ns2:was_present_at rdf:resource="http://kulturarvsdata.se/LSH/events/3382"/>
<ns2:was_present_at rdf:resource="http://kulturarvsdata.se/LSH/events/3461"/>
<ns0:context>
<ns0:Context>
<ns0:contextSuperType rdf:resource="http://kulturarvsdata.se/resurser/ContextSuperType#create"/>
<ns0:contextType rdf:resource="http://kulturarvsdata.se/resurser/ContextType#start"/>
<ns0:fromTime>1594</ns0:fromTime>
Comment 5
User:Salgo60/ListeriaNobelData3.... all russian people are normally born using Gregorian calendar date i.e. we get different data * Ivan Petrovich Pavlov Nobel prize 296 born 1849-09-14 (xsd:date)Magnus: Having dates with no calendar is fragile.... we get a lots of errors see how we are comparing Wikidata with Nobel prize people see
* Ivan Petrovich Pavlov Wikidata Q42985#P569
14 september 1849 Gregorian calendarcompare English Wikipedia they explain it in text
26 September [O.S. 14 September] 1849 – 27 February 1936)
<ns0:placeName>Stockholms slott</ns0:placeName>
Comment 6 Magnus:
Stockholms slott is string not things
compare Wikidata graph about Stockholms slott Things
<ns0:countryName>Sverige</ns0:countryName>
Comment 7 Magnus: Same string problem should be same an object and e.g. same as Q34
</ns0:Context>
</ns0:context>
<ns0:context>
<ns0:Context>
<ns0:contextSuperType rdf:resource="http://kulturarvsdata.se/resurser/ContextSuperType#cease"/>
<ns0:contextType rdf:resource="http://kulturarvsdata.se/resurser/ContextType#stop"/>
<ns0:toTime>1632</ns0:toTime>
</ns0:Context>
</ns0:context>
<ns0:itemName>
<ns0:ItemName>
<ns0:type>Namn</ns0:type>
<ns0:name>Gustav II Adolf av Sverige</ns0:name>
</ns0:ItemName>
</ns0:itemName>
Comment 8 Magnus: Feels you repeat foaf:name
<ns0:presentation rdf:parseType="Literal">
<pres:item xmlns:pres="http://kulturarvsdata.se/presentation#">
<pres:version>1.1</pres:version>
<pres:id>9534</pres:id>
<pres:entityUri>http://kulturarvsdata.se/LSH/agents/9534</pres:entityUri>
<pres:itemLabel>Gustav II Adolf av Sverige</pres:itemLabel>
Comment 9 Magnus: Name is repeated again... feels odd
<pres:representations><pres:representation ="RDF">http://kulturarvsdata.se/LSH/agents/9534</pres:representation>
<pres:representation ="HTML">http://kulturarvsdata.se/LSH/agents/html/9534</pres:representation>
<pres:representation ="XML">http://kulturarvsdata.se/LSH/agents/xml/9534</pres:representation></pres:representations>
<pres:organization>LSH</pres:organization>
<pres:organizationShort>LSH</pres:organizationShort>
Comment 10 Magnus: pres:organization has LSH as string no thing. I would prefer an object
<pres:service>agents</pres:service>
<pres:dataQuality>Rådata</pres:dataQuality>
<pres:buildDate>2019-03-12</pres:buildDate></pres:item></ns0:presentation>
</rdf:Description>
</rdf:RDF>
Comment 11 Magnus: We have no relations in the file to children/ father / mother
Comment 12 Magnus: no sources for facts see my loge thoughts on that
Comment 13 Magnus: no Authority data as VIAF, GND, LIRIS
compare sv:Wikipedia
WorldCat • VIAF: 10637323 • LCCN: n80056899 • ISNI: 0000 0001 1021 0464 • GND: 118543733
• LIBRIS: wt79b47f42nbg14 • SUDOC: 02769397X • BNF: cb11968139b (data)
• BIBSYS: 90545687 • NLA: 35927709 • NDL: 00852585
• NKC: jn20011211166 • SBL: 13316
The idea with Authority data is to identify people if I find some facts a another place and it says this person is VIAF 10637323 then I know that this person is same as
http://kulturarvsdata.se/LSH/agents/9534
My comments see https://t.co/InsMmovxns— Magnus Sälgö (@salgo60) October 26, 2019
In general I feel we have too many STRINGS which is bad.... as Google killed Freebase and gave the data to Wikidata see https://t.co/69UFe7NhFo maybe a more #linked approach with less metadata to maintain is maybe the way forward...
Inga kommentarer:
Skicka en kommentar