I have been giving some thought to this and I wonder how many others have as well.
The question is: How do we go about encapsulating some display-oriented JavaScript into XML RSS syndicated data for a message or blog post?
First, let me setup some options:
1. I create a bit of JavaScript that will show/hide some element within my content. Or perhaps I want to jam a little JavaScript image slideshow in there as well.
2. Maybe the supporting JavaScript functionality lives in a library .js file on my web server. Perhaps it is all inline script living within the element of the message.
3. I plan on using the content on my site as xHTML from an XML source; as a published RSS feed from the same XML source; syndicated and copied to an XSS cloud service for others to consume and own; cached in web and hard newsreaders like newsgator and RSS Bandit, etc.
The challenges I can think of are interesting. If we use the JavaScript inline within the post element, each time we display more than one post that contains the same JavaScript functionality, we could run into collisions with function names, variable values, etc.
Sometimes, the CDATA decoding to HTML entities is done using client-side functionality such as JavaScript. We might have to build in some kind of exec prototyping for the functions and variables if we want our JavaScript to be useful.
For the most part, the big RSS readers and republishing engines are using web browser ActiveX rendering components or they are Web based so we have access to JavaScript. This could be really useful if publishing some functional JavaScript was possible.
Yea. I am sure there are tons of security issues and accessibility challenges to consider as per norm. Anyone have any comments on this?
Comments:
Created 113 weeks, 5 days ago