Note that the s-w.org examples use relative links to point to the data, 
which obviously won't work if you download the file.  I presume you mean 
you are updating them to absolute links.

Note also that modern browsers' cross-site-scripting protections 
_forbid_ accessing data on a different server than the one containing 
the root page.  So the data fetch fails, which leads exhibit to throw a 
syntax error---clearly not the most informative possible.  To get around 
that, you can use exhibit's "jsonp" framework (a standard mechanism for 
circumventing the XSS protections).  But this does require modifying the 
link specification (you need application/jsonp instead of 
application/json) and you need to be talking to a server that knows how 
to service jsonp requests.  I don't know if s-w.org does.  If you aren't 
so lucky, you can use our babel server as a proxy---you can point it to 
a json file, and it will give you a url that will serve up that file 
encapsulated as jsonp.  

John Callahan wrote:
> I've seen that too and I'm not sure how long it's been that way.  I get 
> the same error in the latest FF, IE, and Chrome.
>
> Take a look at the MIT Nobelists example: 
> http://www.simile-widgets.org/exhibit/examples/nobelists/nobelists.html
>
> Download the HTML, keep the js script and data pointers to the s-w.org 
> server, and you'll get a syntax error. (I think it's complaining about a 
> ")" or similar.)   Point to a local copy of nobelists.js and all works 
> great.  Maybe something new in the simile ajax code that prevents remote 
> data sources?  Maybe a new browser security feature? 
>
> - John
>
> **************************************************
> John Callahan, Geospatial Application Developer
> Delaware Geological Survey, University of Delaware
> Email: [email protected]
> **************************************************
>
>
>
>
> mleden wrote:
>   
>> If it's truly the same contents in each file, then I guess it must be
>> some sort of an authentication or general accessibility issue with the
>> "remote json file".
>>
>> The first thing to try is to access the "remote json file", directly
>> from your browser, via the url in your code.
>>
>> HTH,
>> -Mark
>>
>>
>> On Nov 2, 4:52 am, James Cummings <[email protected]> wrote:
>>   
>>     
>>> Hiya,
>>>
>>> I'm having a strange problem getting a remote json file to work that
>>> is identical to a local one.
>>>
>>> i.e.
>>> if I have
>>>  <link href="HOL01-meetings.js" type="application/json" rel="exhibit/data" 
>>> />
>>>
>>> It works perfectly as expected.
>>>
>>> If I have
>>>
>>>  <link href="http://some.domain.here.com/HOL01-meetings.js";
>>> type="application/json" rel="exhibit/data" />
>>>
>>> It just spins forever on 'Working'.
>>>
>>> To create the local one all I did was save the remote one from firefox.
>>>
>>> Is there something obvious I'm missing?
>>>     
>>>
>>>       
>>   
>>     
>
> >
>
>   

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SIMILE Widgets" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/simile-widgets?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to