+1 

I've actually noticed that DBpedia's interpretation of the encoded URI
versus the unencoded URI has switched occasionally.

This is a fairly serious problem for data that links to DBpedia, forcing
the need to edit DBpedia URIs in local data whenever the change occurs, in
addition, of course, to the issues pointed out by Rupert below...

A huge thanks, 

Aaron


On 5/12/11 12:42 PM, "Thomas Steiner" <[email protected]> wrote:

>+1 for this getting fixed, please! Minor source of confusion, but
>probably easy to fix.
>
>Thanks!
>
>Best,
>Tom
>
>On Thu, May 12, 2011 at 18:20, Rupert Westenthaler
><[email protected]> wrote:
>> Hi all
>>
>> I recently discovered, that DBpedia unnecessarily encodes '(' and ')'
>> in URLs to '%28' and '%29' because both
>>  RFC 1738  Uniform Resource Locators (URL)
>>  RFC 2396  (URI Generic Syntax) and
>> define that "(" and ")" can be normally used within URLs.
>>
>> For most of the cases requests with the unencoded variant of the URL
>> would not return any results
>> e.g.
>>  http://dbpedia.org/resource/Family_%28biology%29
>>  http://dbpedia.org/resource/Family_(biology) -> not found
>> Wikipedia allows access with both variants.
>>
>> In some cases DBpedia provides different information for both variants
>> of the URL
>> e.g.
>>  http://dbpedia.org/page/Republican_Party_%28United_States%29
>>  http://dbpedia.org/page/Republican_Party_(United_States)
>>
>> As far as I can say this affects all URLs that use '(' and ')'
>>
>> A similar thing is also the case for URLs that include an "#"
>> e.g.
>>  http://dbpedia.org/resource/Midfielder%23Winger is an own Resource
>>  http://dbpedia.org/resource/Midfielder#Winger returns the contents
>> for Midfielder
>>
>> best
>> Rupert
>>
>> --
>> | Rupert Westenthaler             [email protected]
>> | Bodenlehenstraße 11                             ++43-699-11108907
>> | A-5500 Bischofshofen
>>
>> 
>>-------------------------------------------------------------------------
>>-----
>> Achieve unprecedented app performance and reliability
>> What every C/C++ and Fortran developer should know.
>> Learn how Intel has extended the reach of its next-generation tools
>> to help boost performance applications - inlcuding clusters.
>> http://p.sf.net/sfu/intel-dev2devmay
>> _______________________________________________
>> Dbpedia-discussion mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
>>
>
>
>
>-- 
>Thomas Steiner, Research Scientist, Google Inc.
>http://blog.tomayac.com, http://twitter.com/tomayac
>
>--------------------------------------------------------------------------
>----
>Achieve unprecedented app performance and reliability
>What every C/C++ and Fortran developer should know.
>Learn how Intel has extended the reach of its next-generation tools
>to help boost performance applications - inlcuding clusters.
>http://p.sf.net/sfu/intel-dev2devmay
>_______________________________________________
>Dbpedia-discussion mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion



------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Dbpedia-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion

Reply via email to