Discusion of the ConceptualModel itself seems to have mostly fallen off, with most conceptual discussions being part of the syntax discussion. See SyntaxDiscuss.

See also WellFormedEntryModel, [WWW]Atom in OWL


Structure of an entry (exactly one of each required unless otherwise noted):

Optional extension modules (status in parentheses):

Discussion elsewhere

From discussion in WhatIsAnEntry, see also ComponentBlog and AdaptiveBlogosphere for the use-case for a generalized definition of an Entry.





online journal, weblog


feed, channel:


See also record and resource.

TrackBack URL:

Discussion with SamRuby: [WWW]Road map, [WWW]linkage, [WWW]only what is required.

Discussion in thread mode

[DavidJanes, RefactorOk, DeleteOk] Not to be overly pedantic, but shouldn't it be "poster" or "creator" (in DublinCore-speak) rather than "author". That's really the concept you're talking about here. [Identity] gives the deeper concept of Author.

[AdamRice, RefactorOk] I'd like to introduce a few other concepts to the model:

[JimRoepcke, RefactorOk] I agree with adam that there should be creation/modification timestamps (or whatever labels you want to give them). If this is to be an archive format (to be used to migrate a weblog to a different software platform, for example) as well as for syndication, as the home page says, then this kind of information is crucial. Also, having a modification timestamps aids aggregators in knowing how to deal with entries that the user has already read, but have since changed.

[JimRoepcke, RefactorOk] I am hoping it will be possible to describe a weblog that has posts that are not in chronological order. The weblogging system I use lets me order the items on a given day arbitrarily. Perhaps making the order of the entries in a file significant (rather than assuming that sorting the list by posting date should represent the order the items are to be displayed) is enough? I might have posted an item at noon, but then at 2pm i moved it down to the bottom of the day's entries. Or, I posted an item at noon, then another at 1pm, and then moved the noon-item back to the top after that.

[MaciejCeglowski, RefactorOk] Language should not be optional, except with non-text posts (photoblogs). Otherwise we will have a repeat of the current situation, where English speakers don't use the language attribute, nor do half of non-English speakers, and it becomes essentially useless from neglect. Language is a basic attribute of a post, and hard enough to identify from content that it deserves required status.

[HaroldGilchrist, RefactorOk] The scope of entry needs to support the basic idea that the main message of the entry can and will be communicated by various multi-media file types (ie. photos, audio, video, etc.). Media messages (such as audio, video. FLASH, Word file and combinations of the above and others) and their metadata must be able to stand on their own (not only embedded into HTML) to enable the ability of these and future multi-media type files to be the central message of the entry.

The question becomes, how do we keep entry's definition and metadata generic and simple to support this basic idea?

[MartinAtkins, RefactorOk] (I'm a little confused as to where "what is an entry" discussion should be going on now, so I'm adding this here in the hope that someone will find it and possibly give it a good home) It would be useful to be able to redefine the site which an entry came from at entry level. This is useful for aggregate feeds, which are great for cutting down on the "millions of users pull millions of feeds" problem.

If it were well-supported in the spec, It would facilitate Necho syndication proxies which can pull down and cache content from many feeds and then re-deliver different aggregate feeds to different users reflecting their subscriptions. Moreover currently do something like this with RSS, but it's far from ideal as the description field becomes the "where this came from" field.

However, AggregateFeeds require more than passing consideration since future versions of the spec are an issue.

[DougRansom,RefactorOk] Why is PGP called out? This IMO is a poor choice for PKI, since most of the secure web is based on X.509. I know dozens of people with x.509 certs, and nobody with PGP. X.509 is what businesses use for web site authentication, and they need to sign press releases etc. I feel either the mainstream technology, x.509 should replace PGP, or the generic term PKI used instead, in any spec.

[DougRansom, RefactorOk] BlogRoll. I feek this lingo is kind of sloppy. Syndication is not just about blogs (a lame term itself), its about press releases, marketing communications, etc. It detracts from credibility to have words like "blog" intertwined within a technical standard that has serious commercial applications. NEcho is not a toy.

[JonDavis, RefactorOk] In PowerBlog I use a Significance header for the articles with values of "High", "Normal", or "Low". I've been thinking of changing this to something numerical (1 to 100 or somesuch). I actually use this Significance header in templates; articles of low significance get truncated, and articles of high significance get a special border and bold print. It would be nice to either have this header, or have an open-ended META header.

[wootest, RefactorOk] Hey, guys, last time I checked an article could be co-authored. Why not 1+ authors?

There are numerous problems with this model, discussed in ConceptualModelRevisited. An alternate model proposal is presented in RevisedConceptualModel.

CategoryMetadata, CategoryModel