This page specifies the types of portfolio item or Atom entry.
The type value is represented with an rdf:type sub-element of atom:entry.
Different types are needed to guide receiving systems on what information is vital to the interpretation of the item, and how to process that information. These types have either been used, or their use clearly foreseen as appropriate and raising no problematic issues.
Types of item
If an item has no other type, it is treated simply as an entry, much like a blog entry.
All the following types can be degraded to entries, by appending to the content all information from fields not present in plain entries.
The type of item is represented by
<rdf:type rdf:resource="leap2:..." /> or <rdf:type rdf:resource="http://terms.leapspecs.org/..." />
Characteristics of any item
- title (mandatory in every case, even if it has to be constructed, and must not be empty)
- published, updated
- content = normally the main text associated with the item. For anything like a blog entry or reflection, the content is simply what is written. For many items, however, Atom's content element is best thought of as a description of the item's subject.
- summary = if used, should give just a summary of the content, as is the intention in Atom. This should not be used for other purposes.
Literal or relationship
- author (seen as structured literal)
- author (seen as relationship)
- (author is mandatory if the containing feed has no author, though it normally has one)
- contributor (seen as structured literal)
- contributor (seen as relationship)
- relation → any other related item not related more specifically; any URI
- is part of → selection
- license → URI returning a representation of the license for this entry
- alternate → translations of the same type of entry, using the same kinds of representation
- enclosure → file incidentally attached to the item, not through a resource (see files)
- relation → resource mentioned in the item content, with no more specific relation
These Literals, relationships and categories can apply to any type, in addition to the ones specified for each particular type.
Use of CURIEs
To use CURIEs with Leap2A types, declare
in the opening element of the XML. Examples are given in place.