Hi Paul,
What do you mean by "display semantics". Do you need a non-human to consume
the information? If that is the case, then I'd use RSS. If your display
semantics are for a web brower, then use markup which is CSS friendly.
Something like
<div class="post">
<a id="a1234"></a>
<h2 class="postTitle">Title of post</h2>
<div class="postMetaInfo">
<div class="postCategory"><span>Posted category:</span>
Alert</div>
<div class="postTopic">Weather</div>
<div class="postDate"><span>Posted date:</span>
12/13/2005</div>
<div class="postAuthor"><span>Posted by:</span> <a
title="About This Author" href="http://www.activeinterface.com";>Chris
Harrington</a></div>
</div>
<div class="postBody">
<p>Locals were shocked today when..</p>
</div>
</div>
With the DIVs you can decide (in CSS) how it gets layed out
With the SPANs you can decide (in CSS) what annotation text you (don't) want
to display:
DIV.postMetaInfo DIV.postCategory SPAN {display: none;}
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Paul Bryson
> Sent: Tuesday, December 13, 2005 3:03 PM
> To: [email protected]
> Subject: [WSG CMS] Proper semantics of a news posting
>
> I need to display this information semantically for news
> postings. There
> can either be one on the page, or several on the page where
> they are one
> after the other.
>
> Title (the name of news article, eg "Hurricane in LA")
> Category (eg "Alerts")
> Topic (an image with the appropriate ALT text, eg "Weather")
> Posted by: <username>
> Posted date: <date/time>
> Article Text
>
> Here is what I have so far
>
> <h2>Hurricane in LA</h2>
> <div>Alerts</div>
> <div>Weather</div>
> <dl>
> <dt>Posted by:</dt>
> <dd>Paul</dd>
> <dt>Posted date:</dt>
> <dd>December 15, 1940</dd>
> </dl>
> <div>Locals were shocked today when...</div>
>
> My biggest problem is the Category/Topic. They are both
> descriptive of the
> entire news article, but aren't stored as such. Their
> order/importance
> isn't categorized either, so one could be above the other if desired.
> Placing them in sub-headings doesn't seem appropriate because
> they describe
> the title as much as anything else. The could almost go in
> the definition
> list, but the <dt> for them would never be shown. And hiding
> text 100% of
> the time is bad practice as search engines will count against you.
>
> Any ideas how the Category/Topic could be appropriately
> stored without using
> a DIV?
>
>
> Paul
> *********************************************************
> The CMS discussion list for http://webstandardsgroup.org/
> *********************************************************
>
>
*********************************************************
The CMS discussion list for http://webstandardsgroup.org/
*********************************************************
