Hello Ryan, Thank you for for putting me back on the right track! what I was trying to do looks like a dirty hack... Right now the solution I see is having sed replace all the rdfs:labels for pretty much all of the Fortune 500 companies (dirty too..)
But maybe the reason why I came to this messy situation is a more interesting subject of conversation : What I'm doing here is what I would call a "Poor man entity disambiguation". I got lot of company names, written the funny way, and I'm trying to do some sort of entity disambiguation and get a unique identifier for each of them. To do this the quick and cheap way I just run a "I'm feeling lucky" Google request and the URL returned become my unique identifier. I'm sure some people trying to upgrade to RDf to take advantage of all your cool tools have been in my situation. I assure, my solution works pretty well and it's cheap! but there is one drawback : I have a lot of different and dirty rdfs:label (my Google requests : "pricewater", "PWC", "pricewaterhouse", "pricewaterhousecoopers") for one single URI (the "I'm feeling lucky" URL I get as an answer). It looks messy and I can't afford to have "pricewater" as a facet label in Longwell... Maybe one of your tools could help me with this? (Banach??) Many thanks. Cheers, Frederic Ryan Lee wrote : > Frederic wrote: > > Hello everybody, > > > > I'm having a little problem trying to force the label > > of resources in Longwell's facets. > > Manipulate your data before feeding it to Longwell. > > There is no provenance record in Longwell; all of your > data becomes one > large graph of equally weighted statements. What you > would effectively > get is: > > <rdf:Description rdf:about="http://www.pwc.com/";> > <rdfs:label>PWC</rdfs:label> > <rdfs:label>Pricewaterhouse</rdfs:label> > <rdfs:label>PricewaterhouseCoopers</rdfs:label> > </rdf:Description> > > while noting that order means nothing in this context; > it's just > serialized that way. > Longwell's underlying RDF engine picks one at random > (though it probably > has some internal mechanism for ordering strings, > that's not a feature > of RDF so much as an implementation consequence of > needing to use an > iterator). > > > But it did not work... and I'm running out of ideas > > as > > I have no idea how Longwell works internally. > > While there are pieces of Longwell that can help with displaying and, to > some degree, manipulating data, you are, at this stage of development, better off "cleaning" it manually for Longwell > consumption before > feeding it in. > > -- > Ryan Lee [email hidden] > MIT CSAIL Research Staff http://simile.mit.edu/ > http://people.csail.mit.edu/ryanlee/ ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
