[Developers] RFE: wrap trans/blurb calls in JSON

[David Flanagan]

Thanks for the reminder.  Yes, I'm aware of this. I produced the 
documentation as PDF and HTML files.  Somehow, when those HTML files 
were converted to Freebase topics, the escaped angle brackets got 
mangled.  The missing parts here are probably all names of HTML tags, 
such as <img> and <iframe>.

	David Flanagan

Shug Boabby wrote:
> found at
> 
> http://www.freebase.com/view/guid/9202a8c04000641f800000000544e139
> 
> I've added ** where content appears missing...
> 
> t is usually easier, however, to use the trans service with *** and
> tags. To retrieve and display an image, simply use a trans URL as the
> src attribute of an *** tag. And to retrieve and display the HTML
> content of a document, use a trans URL as the src attribute of an ***.
> 
> HTML Content, tags, and Security
> 
> When you display Metaweb content in an ***, the origin of the framed
> content is different from the origin of your web application. This
> means that the same-origin security-rules apply. The user of your web
> application can see the framed Metaweb content, but JavaScript code in
> your application cannot access this content.
> 
> Metaweb strips executable code from HTML before returning it to you,
> but if any JavaScript code were somehow to make it past Metaweb's
> sanitizer, that code would also be subject to the same-origin policy
> and would be unable to interact with your web application content. In
> this way, using an *** for content fetched with trans gives you an
> extra layer of security.
> 
> 2008/7/22 David Flanagan <david at davidflanagan.com>:
>> Would you send me a the URL at which you're seeing the broken docs?
> _______________________________________________
> Developers mailing list
> Developers at freebase.com
> http://lists.freebase.com/mailman/listinfo/developers
>