For example, each entry has a title. The primary use case that Atom addresses is the syndication of Web content such as weblogs and news headlines to Web sites as well as directly to user agents. This specification uses "Atom" internally. Additionally, it places some requirements on Atom Processors. Note that the choice of namespace prefix is arbitrary and not semantically significant. REC-xml-infoset ]. However, this specification uses a shorthand for two common terms: the phrase "Information Item" is omitted when naming Element Information Items and Attribute Information Items.
Therefore, when this specification uses the term "element," it is referring to an Element Information Item in Infoset terms.
Likewise, when it uses the term "attribute," it is referring to an Attribute Information Item. However, the text of this specification provides the definition of conformance. A complete schema appears in Appendix B. An Atom Feed Document is a representation of an Atom feed, including metadata about the feed, and some or all of the entries associated with it.
Its root is the atom:feed element. Its root is the atom:entry element. REC-xmlbase ]. When xml:base is used in an Atom Document, it serves the function described in section 5. Any element defined by this specification MAY have an xml:lang attribute, whose content indicates the natural language for the element and its descendents.
The language context is only significant for elements and attributes declared to be "Language- Sensitive" by this specification. Requirements regarding the content and interpretation of xml:lang are specified in XML 1. REC-xml ], Section 2.
See Section 6 of this document for a full description of how Atom Documents can be extended. The manner in which Atom Feed Documents are combined in order to reconstruct a feed e. Common Atom Constructs Many of Atom's elements share a few common structures. This section defines those structures and their requirements for convenient reference by the appropriate element definitions. When an element is identified as being a particular kind of construct, it inherits the corresponding requirements from that construct's definition in this section.
Some XML-emitting implementations erroneously insert white space around values by default, and such implementations will emit invalid Atom Documents. Text Constructs A Text construct contains human-readable text, usually in small quantities. The content of Text constructs is Language-Sensitive.
When present, the value MUST be one of "text", "html", or "xhtml". If the "type" attribute is not provided, Atom Processors MUST behave as though it were present with a value of "text". Unlike the atom:content element defined in Section 4.
Text Example atom:title with text content Such text is intended to be presented to humans in a readable fashion. Thus, Atom Processors MAY collapse white space including line breaks and display the text using typographic techniques such as justification and proportional fonts. Atom Processors that display such content MAY use that markup to aid in its display. Atom Processors that display the content MAY use the markup to aid in displaying it. The following example assumes that the XHTML namespace has been bound to the "xh" prefix earlier in the document Person Constructs A Person construct is an element that describes a person, corporation, or similar entity hereafter, 'person'.
Person constructs allow extension Metadata elements see Section 6. The "atom:name" Element The "atom:name" element's content conveys a human-readable name for the person. The content of atom:name is Language-Sensitive.
Person constructs MUST contain exactly one "atom:name" element. The "atom:email" Element The "atom:email" element's content conveys an e-mail address associated with the person.
REC-xmlschema ]. For example, it would be generally inappropriate for a publishing system to apply the same timestamp to several entries that were published during the course of a single day.
Atom Element Definitions 4. Container Elements 4. The "atom:feed" Element The "atom:feed" element is the document i. Its element children consist of metadata elements followed by zero or more atom:entry child elements. If multiple atom:entry elements with the same atom:id value appear in an Atom Feed Document, they represent the same entry.
One typical behavior would be to display only the entry with the latest atom:updated timestamp. Providing Textual Content Experience teaches that feeds that contain textual content are in general more useful than those that do not.
Some applications one example is full-text indexers require a minimum amount of text or X HTML to function reliably and predictably. Feed producers should be aware of these issues. The "atom:entry" Element The "atom:entry" element represents an individual entry, acting as a container for metadata and data associated with the entry.
This element can appear as a child of the atom:feed element, or it can appear as the document i. The following child elements are defined by this specification note that it requires the presence of some of these elements : o atom:entry elements MUST contain one or more atom:author elements, unless the atom:entry contains an atom:source element that contains an atom:author element or, in an Atom Feed Document, the atom:feed element contains an atom:author element itself.
The "atom:content" Element The "atom:content" element either contains or links to the content of the entry. The content of atom:content is Language-Sensitive. The "type" Attribute On the atom:content element, the value of the "type" attribute MAY be one of "text", "html", or "xhtml". If neither the type attribute nor the src attribute is provided, Atom Processors MUST behave as though the type attribute were present with a value of "text".
If the "src" attribute is present, atom:content MUST be empty. The value is advisory; that is to say, when the corresponding URI mapped from an IRI, if necessary is dereferenced, if the server providing that content also provides a media type, the server-provided media type is authoritative.
Thus, Atom Processors MAY collapse white space including line breaks , and display the text using typographic techniques such as justification and proportional fonts. If the "src" attribute is not provided, this would normally mean that the "atom:content" element would contain a single child element that would serve as the root element of the XML document of the indicated type.
Metadata Elements 4. The "atom:author" Element The "atom:author" element is a Person construct that indicates the author of the entry or feed. This makes automation incredibly simple because you only have to update the feed on your blog and all these other services will pick it up. They will then perform some task for you. You don't have to manually tell those services that you published a new post, they will retrieve it from your website. This means that you don't have to do anything yourself when you want to share your blog posts.
This is in contrast with sending API requests to other platforms telling them an update is available. You don't have to write any implementation details for sharing your content, but rather, you can use this standardized system to create the feed in one place and then hang back and relax until the other services request the feed and pick up your content.
A lot of people think syndication feeds are this outdated technology people used a decade ago. I used to be one of those people until I discovered it's true potential.
Syndication feeds allow you to tailor your newsfeed exactly the way you want it to. Instead of going through a newsfeed that's been created by something like a newspaper, where you see every single news article, you can pick and choose which channels you would like to see. This sounds oddly familiar, doesn't it? It sounds like a social media platform, where you decide who you want to follow and hear more from.
So really, syndication feeds are very modern but get a bad reputation "because it's so old and rusty". Do you know how Spotify, Apple Podcasts, Sticher, and all the other podcast players know which episodes are within a podcast? That's right, RSS. If you've been on Facebook and Twitter in the last year or two, you'll have noticed that you keep missing posts of your friends and people you follow. These can include, for example, text, graphics, video, podcast, or interactive elements programmed with applications such as JavaScript.
In the Atom feed, the respective content type is displayed in abbreviated form so that you can get an idea of its content. At the same time, you will also get a Snippet from the content such as the title of a current blog post.
Since Atom feeds are a machine-readable format, they are also relevant to search engines. The original function of Atom feeds is to provide website users with a consistent format that allows them to be quickly and easily informed about news on different websites. Users only need to subscribe to an Atom feed, and can then use various Feed readers or their browser. The atom format as such has the advantage that different data types can be syndicated which is impossible with an RSS feed.
Preview the Feed To preview the feed, select the Preview tab. References For more information about required and optional fields in your Atom feed, please see the Atom documentation. Please help us improve our documentation Suggest changes or request new documentation. Site Search.
0コメント