John Bresnik wrote:
> Thanks Ryan for the response - I made the changes as you suggested but
> still don't seem to see anything -
>
> I am still getting this velocity error on start up though:
>
> [ERROR - Velocity] VM #renderFrame: error : too few arguments to macro.
> Wanted 2 got 0
>
> You think this might have something to do with it?
>
> Thanks,
> brez
The unfortunate advice I usually give at this point is to add your data
and merge your configuration into a bundle that already works, then go
from there. You could try to build the 'people' target, then place your
data in the data directory. Add your displayClasses to the bundle's
configuration and see if any of your data comes up.
The problem sometimes is that Longwell won't display any facets for
searching if the number of results that will be returned is equal to the
size of all results; for instance, if you had a database of 20
foaf:Persons and the only facet used was rdf:type, Longwell wouldn't
show anything for narrowing because all 20 are rdf:type foaf:Person.
You could also try to expand and vary your test data...
> Ryan Lee wrote:
>
>> John Bresnik wrote:
>>
>>> Hello,
>>>
>>> I've trying to configure Longwell to view my own data [not as a
>>> bundle but by putting it in the WEB-INF/data directory and updating
>>> the config.n3 file] - I don't seem to be getting anything though -
>>> here's my log:
>>
>>
>>
>> Hi John,
>>
>> Your data needs to have an rdf:type for each resource. One of the
>> foundational assumptions of Longwell is that input RDF data is typed.
>> I would modify it as follows:
>>
>>> -----------------------------
>>> Here's the RDF:
>>
>>
>>
>> [[[
>> <?xml version="1.0"?>
>> <rdf:RDF
>> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>> xmlns:dc="http://purl.org/dc/elements/1.1/"
>> xmlns:foaf="http://xmlns.com/foaf/0.1/"
>> xmlns:test="http://test/TEST#">
>>
>> <test:Source rdf:about="http://test/TEST#TestInstance">
>> <test:hasCriteria rdf:resource="http://test/TEST#TestCriteria"/>
>> <dc:title>This is a test of the config file</dc:title>
>> <test:poc>
>> <foaf:Person rdf:about="http://test/TEST#MrTTest">
>> <foaf:name>Mr T Test</foaf:name>
>> <foaf:givenname>Tee</foaf:givenname>
>> <foaf:family_name>Test</foaf:family_name>
>> <foaf:phone rdf:resource="tel:(703) 621-1421"/>
>> </foaf:Person>
>> </test:poc>
>> <test:location rdf:resource="http://www.yahoo.com/"/>
>> <!-- see note below
>> <test:isDraft />
>> -->
>> </test:Source>
>>
>> </rdf:RDF>
>> ]]]
>>
>> I'm not sure which class you intended test:TestInstance to be, so I
>> randomly picked one out of your config.
>>
>> I commented out test:isDraft because it should be the predicate part
>> of a triple. If you mean to say that test:TestInstance is a draft,
>> consider remodelling your vocabulary to something like
>> 'test:TestInstance test:status test:Draft.'
>>
>> As for the configuration you've set up:
>>
>>> :fccc disp:displayProperties (
>>> foaf:name
>>> dc:title
>>> test:location
>>> test:poc
>>> foaf:name
>>> foaf:givenname
>>> foaf:family_name
>>> foaf:phone
>>> ) .
>>>
>>> :fccc disp:displayFacets (
>>> rdf:type
>>> test:hasCriteria
>>> test:hasReference
>>> test:poc
>>> ) .
>>> :fccc disp:displayClasses (
>>> test:Source
>>> test:Reference
>>> test:TestCriteria
>>> test:poc
>>> ) .
>>
>>
>>
>> test:poc should really only be in one of these lists. It's not a
>> class and it seems more suited to be a facet than just a displayed
>> property, so I suggest leaving it only in the disp:displayFacets list.
>>
>>> Should I use a bundle instead? Any help would be much appreciated..
>>
>>
>>
>> You could make your own bundle so you can just type './build.sh webapp
>> -Dbundle={your bundle name}' at the command line instead of manually
>> shifting around files. It's a convenience but not a requirement.
>>
>>> Thanks,
>>> brez
>>
>>
>>
>> Please let us know if you have any more questions.
>>
>
--
Ryan Lee ryanlee_at_w3.org
W3C Research Engineer +1.617.253.5327
http://simile.mit.edu/
Received on Thu Jun 16 2005 - 21:09:57 EDT