Jump to content
  • Announcements

    • boen_robot

      Guidelines and Netiquette   03/28/2017

      Posting Problems:   Having problems posting your topic? Read through this: To join, you agree to our terms and conditions and fill out and submit a registration form. An activation email will be sent to your email adress, so you'll need to verify your account. After that the account has to be validated by one of the moderators. This will mean that it can take up to a day to be activated. A couple of things to remember to ensure approval: Don't use an email address in one of those $2 four character .com domains eg. xyds.com. These will be deleted and the domain added to the banned list. Don't use an email address that is within a domain with a bad reputation for spam. A Google search is run on every email address and email domain. Don't sign up with an email address that doesn't exist, doesn't work or requires the sender to answer a quiz before their email can get to you. Put your country and or state and city in the signup form. Blank forms will go to the botton of the "to do" list. And make sure that your email address and your country match, saying you're from Alabama and using a .ru email address is not going to get you activated. After a membership is activated the first few posts will be monitored. Posting spam or unapproved topics described in the agreement results in an immediate ban. The email provider and the IP addresses associated with the account will be banned and all posts will be deleted. These strict measures have been deemed necessary to hinder spam. Sorry for any inconvenience this causes, but it's not liable to change. If, after reading this, you still can't post and don't understand why, contact one of the Moderators listed here.   Topic Guidelines   Including the following information can expedite an accurate response from board members: Must be a Specific Problem or Question related to web design and development Include Code in Question (wrap with   for small blocks of code and for longer blocks   ) Include Code Author Include Extra Notes/Modifications/Attempts Include web link to page/file when possible Content Guidelines   You may not post, upload, link to, or email any Content that contains, promotes, gives instruction about, or provides prohibited Content. Prohibited Content includes any Content that breaks any local, state, county, national or international law. Prohibited Content also includes: No direct or indirect advertising or websites, forums, products, services No hijacking of posts (do not post your question in someone elses) Content that infringes upon any rights [ex. MP3s and ROMs] (including, but not limited to, copyrights and trademarks) Abusive, threatening, defamatory, racist, or obscene Viruses or any other harmful computer software False Information or libel Spam, chain letters, or Pyramid schemes Gambling or Illicit drugs Terrorism Hacking or cheating for internet/online games Warez, Roms, CD-Keys, Cracks, Passwords, or Serial Numbers Pornography, nudity, or sexual material of any kind Excessive profanity Invasive of privacy or impersonation of any person/entity Hacking materials or information Posting Tips   There are more BBcodes than there are buttons for on the reply menu. To get the full list, click "BB Code Help" underneath the clickable smilie face menu. Use   for small snippets of code Use   for lengthy snippets of code Use   if your snippet is HTML (optional) Use   if your snippet is SQL (optional) Rules of Conduct   Be nice. There's no need for calling someone stupid if they ask an 'easy' question. Keep your avatars and signatures absolutely child friendly. We have a younger audience on this forum. Keep your language appropriate for the same reason above. Do not PM moderators for help on the forum. Post on the topic, or create a new one.   Spam:   Recently, as you have all without doubt noticed, we have had lots of spam and advertisement on the forum. Therefore, we'd like to alert you as to what to do when you have found any of the aforementioned annoying messages: it. Immediately. Give a clear reason, please, if the advertising is not evident. DO NOT POST! Report, let the post stay as is, and we will get to it, meanwhile if you continue to post as normal in the other threads, it won't be on the top so long. Refrain from PMing the member. This won't help at all, as they are most likely spambots anyway. Thank you.       Images in signatures:   After thinking of users on dial-up, we have decided to enforce the following rules regarding signatures. Please pay heed to them. Respecting these rules is respecting the members on this forum with dial-up. Signature rules: No animated images AT ALL. No matter the amount of animation. Maximum image widthxheight: 300x150 Maximum image (file) size: 15kb Use calm colors. Do not use highly contrasting images in your signature, as this can get really annoying when seeing several posts from one member in the same thread. The same prohibited content goes for images as for posts. Lastly, use common sense. No lengthy signatures please. Save us some scrolling. Thank you.       Links in signatures:   Please understand that w3schools.com only exists because of voluntary work and is barely supported by the advertising littered throughout the tutorials and the forum. So, please, stop advertising other sites. DO not post links that drive traffic away from the w3schools domain - especially to a site that offers similar if not identical information. Please help support the site by keeping individuals on it. Thank you. Here are some guidelines as to what you can put in your signature: w3schools links --> allowed w3.org links --> allowed browser links --> allowed html editor links --> allowed personal sites --> allowed tutorial sites competing with w3schools --> NOT allowed sites completely irrelevant to webprogramming and this forum --> NOT allowed   Thanks for understanding, and for taking the time to read this. ~W3Schools Modstaff~
iwato

<item> Subelements: <link> vs <enclosure>

Recommended Posts

I am confused about the use of the <link> and <enclosure> subelements of the <item> subelement. 

The difference between the <link> subelements of the <channel> and <item> elements appears clear, but the difference between the <link> and <enclosure> subelements of the <item> subelement are difficult to understand.  For example, if your RSS feed contained a long series of <item> subelements with each referring to a different podcast, why would you need both a <link> and <enclosure> for the same <item> subelement.

<channel>
	<link></link>
	<item>
		<link></link>
		<enclosure></enclosure>
	</item>
</channel>

Share this post


Link to post
Share on other sites

If the link is an article that contains some form of media, then you would use both the link and the enclosure. Let's say there's a link to an article containing the written transcript of a podcast along with embedded audio, you would put the link to that page in the <link> tag and the reference to the audio file in the <enclosure> tag.

An RSS item probably should not directly reference a multimedia file, it should reference a web page that contains the file.

Share this post


Link to post
Share on other sites

Hi Ingolme,

If there were no <link> subelement for the <channel> element I could easily agree.  If, however, the media file -- in my case, a podcast -- is well presented and can stand alone, the <link> subelement of the <item> element would appear unnecessary.

What I currently have under consideration is a single webpage that achieves two tasks:  several methods of categorization and access for each posted podcast.  One method of categorization would be for the chronological order in which the podcasts appear.  Two to three additional categories would be created for different methods of categorizing the same content.  From each of these categories one could call up any of the podcasts in the same webpage -- say, with an iframe, include, or the like that contains a link to the podcast along with additional reference materials, a brief explanation of the podcast, and a forever changing image that would host an advertisement.

In addition to my own feed I plan to create other feeds for other podcast hosts.  As these other hosts generally permit images, I will include a link with each image to my own webpage.  When the link is clicked the aforementioned insert containing the desired podcast would automatically appear.

Although all RSS feeds require certain information some RSS feeds have their own namespace with a variety of optional elements -- the iTunes namespace, for example, as its own set of required elements.

In effect, I envision three different <link> elements:

1) <link> (channel) - Points to the webpage.

2) <link> (item) - Points to the webpage and calls up the insert.

3) <link> (image) - Points to the webpage, or points to the webpage and calls up the insert.

My concern, of course, is how to achieve the action "points to the webpage AND calls up the insert".

How would the link be designed?  Could I append a hash tag to the link that points to the website, for example.

Roddy 

 

Share this post


Link to post
Share on other sites

Some RSS readers may embed the podcast in the feed if you have an <enclosure> element, so I would suggest using both <link> and <enclosure> elements to point to the podcast.

The <link> element of the <channel> should link to a page where the channel resides, that is a collection of podcasts. The <link> of an <item> would link to an individual podcast. Ideally each podcast should have one page on your site, but if you just want to link to the MP3 I can't tell you if there are any restrictions on that.

Namespaces may give you more options, but the elements of each namespace will only work on the software that supports it, for example only iTunes may use the iTunes namespace elements.

Here's the official specification of RSS with a description of all the elements: https://cyber.harvard.edu/rss/rss.html

Share this post


Link to post
Share on other sites

I am not very fond of the link that you provided, as I find it both confusing and incomplete.  It is, however, where I began my own investigation several weeks ago.  Since then, I have been using what appears to me to be a better resource.  

OK. I believe that I have finally sorted the elements out.

1)     <link> (channel) - Points to the folder containing the items targeted in each <item> element.

2a)   <link> (item) and <emclosure> (item - Point to the most recent feed <item>, or alternatively

2b)   <link> (item) - Points to the most recent feed item,  and <enclosure> (item) points to a media file that accompanies the feed item.

3)     <link> (image) - Points to the webpage that provides a description of the channel as well as access to the individual items.

4)     <url>  (image) - Points to the image itself.

4)     <source> (item) - Points to the xml file that contains the actual feed -- namely, itself.

During my research I read that feeds for a website are typically found by entering the website's domain name followed by a feed folder.  Surely this path is not automatically generated.  Surely, this folder must be created by the webpage's host.  What exactly goes into this folder.  Is it the xml feed page, the podcasts, or both?  Are you familiar with this "common" practice?

Roddy

Share this post


Link to post
Share on other sites

Many CMS will generate the feed link, but it's not created automatically by the browser or server. The feed URL should point to the XML file itself.

On your website you can add a <link> tag to indicate that there's a feed so that the RSS icon appears in the navigation bar:

<link href="... Feed URL ..." rel="alternate" type="application/rss+xml" title="Give a title to your feed">

 

Share this post


Link to post
Share on other sites

I have never looked for the presence of an RSS feed in my browser window before, but any form of additional, positive, free advertisement cannot hurt. Still, I am not sure that you have answered my question.  So, please let me try again.

If the <link> element that you just described were present on my webpage and the user typed the following in his browser search window

http://www.grammarcaptive.com/feed

the feed link and, of course, the path to it would be revealed automatically.  Is this true?

Share this post


Link to post
Share on other sites

Just adding "/feed" to a URL won't show the feed. You have to manually put your feed XML in that URL and have your server send the correct content-type type header of application/rss+xml. Like I said, most content management systems will generate this link for you, but if your website isn't using a content management system or the one you're using doesn't have that feature then you will have to create the URL yourself.

I can't verify that it's a common practice to use "/feed" for the feed URL, but I know that the CMS I've been working with does that.

Share this post


Link to post
Share on other sites

I do not use a CMS, but am still a little unclear about what you mean when you write "and have your server send the correct content-type type header of application/rss+xml"

Also, I do not know, if I have asked this question before, but certainly I am still in doubt. The use of RSS and XML terminology is often undefined or loosely applied, and it has created enormous confusion for me.  So, please be further patient.

QUESTION:  Where does the XML/RSS file containing the <channel> and <item> elements go?

1)  Anywhere, so long as the file's elements point to the proper folders and files.

2)  In the folder with the items that are the content of the RSS feed.

3)  Any of several preferred locations, and it is good practice, but not necessary that the file and the content to which its elements point are in the same folder.

Roddy

 

Share this post


Link to post
Share on other sites

The RSS file can go anywhere you want, you just have to tell people where to find it. As I mentioned earlier, you can tell browsers where to find a feed by putting a <link> tag in your HTML page. There's no real best practice as to where to place your RSS feed files. I think RSS feeds have to use absolute URLs in the <link> tags including protocol and domain name to point to the location of the files.

If you want a URL like "/feed" for your RSS feed you would have to use URL rewriting on the server, a regular URL would look like this instead: "/feed.xml" or "/feed.rss".

  • Like 1

Share this post


Link to post
Share on other sites

Got it!  Thanks!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×