Re: [Dbpedia-dutch] Lists

[Roland C. <met...@gm...>]

Hi Gerard,

After a look at the mapping I realize we talk about Lists while we mean
Tables. I noticed the concept List exists, the concept ListItems doesn't
... Imho we should speak of Tables and Rows. In general a table
represents a collection of triples about a subject, in case of the
'Wikipedia sjabloon tabelrij etc.' the right order of the triple is row,
column, intersection. The coherence of the collection of triples is
defined by the subject of the table, i.e. metadata for each row in the
table and should be mapped to a subject property of the Table/List. So a
Table/List is about ArchitecturalStructure and it should have a
dcterms:subject relation to this class. Then the Table contains Rows
(which should also be qualified as such!) each row represents the same
subject as the Table. At this moment each Row in the mappings is typed
directly as ArchitecturalStructure [1] which may be convenient now but
may provide ambiguity in the long run. Some (or many) rows may already
have an URI when a dedicated Wikipedia page is in place!).

Best,
Roland

[1]
http://mappings.dbpedia.org/index.php/Mapping_nl:Tabelrij_erfgoed_Vlaanderen


On 10-03-14 11:49, Kuys, Gerard wrote:
> Hi Roland,
>
> I have to ruminate on this. Could you provide an example?
>
> Regards,
>
> Gerard
> ________________________________________
> Van: Roland Cornelissen [met...@gm...]
> Verzonden: maandag 10 maart 2014 11:45
> Aan: Kuys, Gerard; dbp...@li...
> Onderwerp: Re: [Dbpedia-dutch] Lists
>
> Hi Gerard,
>
> An instance of the class List should have a subject property defining
> the subject (type) of the List, imho.
> This way the instance of a List could be specified having multiple
> subjects like Nijmegen and ArchitecturalStructure making the description
> of the list accurate.
> The subject of the ListItems is not necessarily inherited from List,
> only the defining rdf:type should be specified in the List for all
> ListItems.
> Not sure if we need structure or rules for this: We can say that if a
> List contains one subject it defines the type of ListItems, but if
> there's more subjects an additional indicator is needed...
>
> Best,
> Roland
>
>
> On 10-03-14 11:19, Kuys, Gerard wrote:
>> Hi,
>>
>> I agree, that a list should be typed to a List. However, there is a mapping mechanism that should grant that every Item in the List should be transformed into a resource of the proper type. So, for instance, there is the template 'Tabelrij rijksmonument' which makes sure that a query like:
>>
>> PREFIX dbpedia-owl: <http://dbpedia.org/ontology/>
>> PREFIX foaf: <http://xmlns.com/foaf/0.1/>
>>
>> SELECT DISTINCT  (str(?monNr) AS ?Nr)
>>                  (str(?mon) AS ?Rijksmonument)
>>                  (str(?adr) AS ?naam)
>>                  (str(?jaar) AS ?bouwjaar)
>> WHERE
>>
>> {
>>     ?lijst dbpedia-owl:wikiPageID 1666607 .   # Om niet in de knoei te komen met de haakjes van 'Nijmegen_(plaats)'
>>     ?lijstMonument dbpedia-owl:listItemOf ?lijst .
>>     OPTIONAL { ?lijstMonument foaf:name ?mon }
>>     OPTIONAL { ?lijstMonument dbpedia-owl:address ?adr }
>>     OPTIONAL { ?lijstMonument dbpedia-owl:yearOfConstruction ?jaar }
>>     OPTIONAL { ?lijstMonument dbpedia-owl:codeNationalMonument ?monNr }
>>
>> }
>>
>> will return a set of ArchitecturalStructures (which is the classification that will fit all list items). Now, the problem for me, is to attach the right template to the right list. How can I make sure, that the 'Lijst van rijksmonumenten op begraafplaats Soestbergen' will return a set of GraveMonuments or at the very least a set of ArchitecturalStructures?
>>
>> Regards,
>>
>> Gerard
>>
>>
>> ________________________________________
>> Van: Roland Cornelissen [met...@gm...]
>> Verzonden: maandag 10 maart 2014 9:40
>> Aan: dbp...@li...
>> Onderwerp: [Dbpedia-dutch] Lists
>>
>> Hi,
>>
>> I noticed errors in extracted lists from Wikipedia;
>>
>> First of all: when a list from Wikipedia is extracted to DBpedia it gets
>> rdf:type dbpedia-owl:Place (etc.). See for example [1]. This is not the
>> right type, it is a list and not a place, therefore I think the rdf:type
>> of an extracted list should be dbpedia-owl:List [2].
>>
>> Second one: Values contained in the list should be extracted as separate
>> resources where each resource contains it's own properties (which is 1
>> row in the list or table).
>> To have all values in rows directly attributed to the list makes no
>> sense which is the case now...
>>
>> Third (which is a more generic problem) : the latitude and longitude
>> values that are extracted should be geo:lat and geo:long (xsd:float),
>> now those are just numbers and don't contain decimal degrees following
>> wgs84. I have seen this in other places too. We need to fix the
>> coordinates imho.
>>
>> Thanks,
>> Roland
>>
>> [1] http://nl.dbpedia.org/page/Lijst_van_onroerend_erfgoed_in_Riemst
>> [2] http://dbpedia.org/ontology/List
>> [3] www.w3.org/2003/01/geo/wgs84_pos
>>
>> ------------------------------------------------------------------------------
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and their
>> applications. Written by three acclaimed leaders in the field,
>> this first edition is now available. Download your free book today!
>> http://p.sf.net/sfu/13534_NeoTech
>> _______________________________________________
>> Dbpedia-dutch mailing list
>> Dbp...@li...
>> https://lists.sourceforge.net/lists/listinfo/dbpedia-dutch
>>
>> Disclaimer
>> Dit bericht met eventuele bijlagen is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Indien u niet de bedoelde ontvanger bent, wordt u verzocht de afzender te waarschuwen en dit bericht met eventuele bijlagen direct te verwijderen en/of te vernietigen. Het is niet toegestaan dit bericht en eventuele bijlagen te vermenigvuldigen, door te sturen, openbaar te maken, op te slaan of op andere wijze te gebruiken. Ordina N.V. en/of haar groepsmaatschappijen accepteren geen verantwoordelijkheid of aansprakelijkheid voor schade die voortvloeit uit de inhoud en/of de verzending van dit bericht.
>>
>> This e-mail and any attachments are confidential and are solely intended for the addressee. If you are not the intended recipient, please notify the sender and delete and/or destroy this message and any attachments immediately. It is prohibited to copy, to distribute, to disclose or to use this e-mail and any attachments in any other way. Ordina N.V. and/or its group companies do not accept any responsibility nor liability for any damage resulting from the content of and/or the transmission of this message.
>
> Disclaimer
> Dit bericht met eventuele bijlagen is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Indien u niet de bedoelde ontvanger bent, wordt u verzocht de afzender te waarschuwen en dit bericht met eventuele bijlagen direct te verwijderen en/of te vernietigen. Het is niet toegestaan dit bericht en eventuele bijlagen te vermenigvuldigen, door te sturen, openbaar te maken, op te slaan of op andere wijze te gebruiken. Ordina N.V. en/of haar groepsmaatschappijen accepteren geen verantwoordelijkheid of aansprakelijkheid voor schade die voortvloeit uit de inhoud en/of de verzending van dit bericht.
>
> This e-mail and any attachments are confidential and are solely intended for the addressee. If you are not the intended recipient, please notify the sender and delete and/or destroy this message and any attachments immediately. It is prohibited to copy, to distribute, to disclose or to use this e-mail and any attachments in any other way. Ordina N.V. and/or its group companies do not accept any responsibility nor liability for any damage resulting from the content of and/or the transmission of this message.