- From: Rob McCool <robm@robm.com>
- Date: Thu, 7 Aug 2003 18:08:42 -0700
- To: "Richard H. McCullough" <rhm@cdepot.net>
- Cc: public-rdf-tap@w3.org, KR-language <KR-language@YahooGroups.com>
> 1. As I do more TAP examples, I see more examples > such as > > FashionModelMacPherson,Elle > ActorMacPherson,Elle > > which should be declared > > FashionModelMacPherson,Elle owl:sameAs ActorMacPherson,Elle > > So, the big question is: will TAP support such > *essential* OWL constructs, or will TAP stick > with just the RDF/RDFS constructs? The plan is to stick with RDF/RDFS and have a post-processing system run over the KB periodically to merge equivalent nodes using some set of guidelines. There are literally hundreds of these examples (Tom Waits and Suzanne Vega are two obvious ones). > 2. The MKR equivalent is > > "FashionModelMacPherson,Elle" is "ActorMacPherson,Elle"; > > I *don't like the quotes* for MKR, but they are *required* to > distinguish a single resource from a list/set of two resources. > For example, I can say > > "AthleteYounger,Jordan", "AthleteOlder,Jordan" is > "AthleteJordan,_Michael"; > > which indicates three names for the same resource. > > 3. Because of 2, I would like to see TAP do away with the > commas embedded in names. What about using a \ in the MKR system, something like AthleteYounger\,Jordan, AthleteOlder\,Jordan is AthleteJordan\,_Michael We could change to do away with the commas, or to percent escape them, but I'm reluctant to change it with preparations for a release underway.
Received on Thursday, 7 August 2003 21:08:55 UTC