Table of Content
There seems to be problems with the modelling or the RDF representation of cartoon characters, console game characters and stuffed toys. Click here for details. Here is an example in RDF.
The person "W. Håkon" is referred by two different identifiers, respectively ending by "Håkon" and "Håkon". This may be due to different spellings in the exploited souce files. However, should the '&' in "å" (the escaping of 'å') be escaped itself?
Should numbers be encoded as URLs, using the URL of TAP?
Dates should not be encoded as URLs (using the URL of TAP) and should not include spaces. The URL of TAP should also not be used as prefix for other URLs.
Property values often include spaces (' ' and '\r', i.e. ^M) before or after the actual value. However, this is easy to filter out.
Why are some types of media objects instance of daml:Class or tap:ProductType? Since all media objects are products, tap:MediaObject could be instance of tap:ProductType. However, it is better to use subtype links (and hence first-order classes) than instance links (and hence second-order classes) for organizing types (since that simplifies navigation and inferencing).