2
1
0

my query sparql failed because dbp:name in all artist page have been deleted ... why??? 


The queries worked  well until yesterday

    CommentAdd your comment...

    3 answers

    1.  
      4
      3
      2

      iirc this is a feature, not a bug.

      Previously, facts that have been mapped occurred twice: (1) in the dbo-namespace (or foaf:name in this case) (mapped triples) and (2) in the dbp-namespace (raw data). This was misleading for many users (in particular for properties like dbo:birthPlace vs dbp:birthplace, dbp:placeofbirth, etc.).

      Now, in order to solve this information duplication the mapped triples do not occur in the raw data anymore. Hence, triples using the dbp-properties indicate a missing mapping. Users are encouraged to use the mapped properties, as these are of higher quality.

        CommentAdd your comment...
      1.  
        3
        2
        1

        Please use foaf:name instead:


        prefix dbc:<http://dbpedia.org/resource/Category:>
        prefix dct:<http://purl.org/dc/terms/>
        SELECT *
        WHERE{
        ?x dct:subject dbc:English_rock_singers.
        OPTIONAL{?x dbp:name ?name.}
        OPTIONAL{?x foaf:name ?fname.}
        }


        But you are right the lack of dbp:name needs to be investigated.

        Best

          CommentAdd your comment...
        1.  
          1
          0
          -1

          Right you are, I thought along the same lines, just wasn't sure.

            CommentAdd your comment...