OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: [dita-fa-edboard] News/Announcements Content Requirements

[ Lists Home | Date Index | Thread Index ]

Well .. from a calendar's perspective, announcements are more like 
events .. they are things that happen in the future. While news is a 
historical thing. For that reason, news is something that remains 
relevant for a longer time that a typical announcement or event (there 
may be some news about an announcement or event, but once an event has 
passed it's not all that useful any more).

So while there could be three separate pages for news, announcements, 
and events, I'd be more inclined to have a News page and an 
Events/Announcements page.

Does this make sense or am I making more of this than is useful?

...scott


Carol Geyer wrote:

>So, do you suggest a separate page for Announcements?
>
>We do need a space somewhere for people to post announcements, i.e. items of interest that people want to convey to one another, not
>necessarily official, published news articles or press release, e.g., "DITA v5.0 public review begins today and closes on 8 Oct
>2008," "An effort to translate DITA into Portuguese is underway; interested volunteers should contact Jose," "A Call for Papers has
>been issued for DITA World"...
>
>Should we create some sort of bulletin board page, and save News for published articles? Would company press releases be News or
>Announcements? 
>
>You're right, whatever we decide, we need to be clear about it. If policing/redirecting is too much trouble, should we just take a
>lighter approach to the News page, and let anyone post any type of announcement there, either linking to a published article,
>company press release, archived email message, detailed wiki page, or even no link at all if the vitals can be conveyed in 2-3
>sentences?
>
>Fields for the News/Announcements form could be something like:
>
>1: Headline 
>
>2: Description: 100 words or less
>
>3: Source (publication, company or contact info if posted by an individual)
>
>4: Date (if article, date of publication or when press release was issued, for informal messages, date of posting
>
>5: URL for complete article, company press release, or other page, if appropriate and publicly accessible. (optional)
> 
>--c
>
>
>-----Original Message-----
>From: Scott Prentice [mailto:sp@leximation.com] 
>Sent: Thursday, January 26, 2006 1:31 PM
>Cc: dita-fa-edboard@lists.xml.org
>Subject: Re: [dita-fa-edboard] News/Announcements Content Requirements
>
>Maybe this should be just "News" rather than "News/Announcements" .. an Announcement can certainly be in the future .. maybe that
>would help to draw a better distinction between news and events. I agree that we don't want to spend much time worrying about what
>gets on which list. I also agree that the ordering of the lists should be opposing as long as one is mainly future and the other is
>past.
>
>...scott
>
>
>Carol Geyer wrote:
>
>  
>
>>Sorry for the confusion. While working on the News page, I was looking 
>>for a press release to use as an example. The CM Conference press release happened to be in my in-box, so I grabbed it.
>>
>>I don't think we need to spend too many cycles trying to police or 
>>redirect items on the News page, though. Realistically, there are many 
>>press releases and news articles published about conferences and about 
>>products. Just because a company lists its product on our Products and Services page doesn't mean they can't post a press release
>>    
>>
>about it on the News page as well. Just because a conference is posted on the Events page doesn't mean a press release with details
>on its keynote can't be listed on the News page.
>  
>
>>The redundancy may be less than optimal, but I don't think it's a big issue.
>>
>>As for the inconsistent ordering between the News and Events pages, 
>>there's a practical reason for this. When you look at News items, you 
>>want to see the most recent first. There is no "future" News, yet 
>>"Past" news may still be of interest. Events, on the other hand, is the 
>>opposite. "Future" events are what people need to see. We may want to keep links to past events around for archival purposes
>>    
>>
>(especially if the conference organizers post presentations there), but if they are prominent, they'll make the page look dated.
>  
>
>>I'm usually all for consistency, but this is one instance where it doesn't work.
>>
>>
>>Carol
>>
>>
>>-----Original Message-----
>>From: Scott Prentice [mailto:sp@leximation.com]
>>Sent: Thursday, January 26, 2006 12:45 PM
>>To: Jerry Silver
>>Cc: dita-fa-edboard@lists.xml.org
>>Subject: Re: [dita-fa-edboard] News/Announcements Content Requirements
>>
>>Sorry to be responding so late to this ..
>>
>>- What determines the difference between an event and a 
>>news/announcement item? In looking at the examples, I'd think that the 
>>CM Strategies Conference would be an event. It seems like we'd need to clearly define what type of items go on each list. I'd think
>>    
>>
>that anything that can be attended by a group of people is an event and anything else is news/announcement.
>  
>
>>- I'd set up both of these lists in the same chronological order, the mockups are reversed from each other.
>>
>>- Will the events page handle recurring events?
>>
>>...scott
>>
>>Scott Prentice
>>Leximation, Inc.
>>www.leximation.com
>>+1.415.485.1892
>>
>>
>>
>>Jerry Silver wrote:
>>
>>
>> 
>>
>>    
>>
>>>Attached is an annotated mockup for the Focus Area News and 
>>>Announcements page.
>>>
>>>I'd like to see a new content type for DITA announcements.  The 
>>>interaction model is:
>>>
>>>1. Authenticated users enter new announcements, via a form.  To enter 
>>>a new announcement, they click on the "Add New Announcement" link, 
>>>which will be available on the News and Announcements page, and 
>>>possibly in other locations on the site.
>>>
>>>2. Authenticated users can edit or delete announcements they have 
>>>submitted.  An authenticated user will be able to see all the 
>>>announcements they have created, use the form to update an 
>>>announcment, or select an announcement for deletion.
>>>
>>>3. People looking for news/announcements visit a News/Announcements 
>>>page, a dynamically generated page that lists all relevant announcements.
>>>
>>>A few additional requirements:
>>>
>>>1. The News and Announcements page should show up to two months of 
>>>announcements (the current month and the previous month), in 
>>>chronological order, grouped by month.
>>>
>>>2. Older events should still be accessible via the News and 
>>>Announcements Archive page.  This page should contain a link for each 
>>>month; e.g. a link to December 2005, November 2005, etc.  These 
>>>archived pages can be dynamically generated, but they must be 
>>>crawlable by a search engine, so they should avoid parameters in the 
>>>URL.  Question: can the News and Announcements Archive Page be 
>>>dynamically generated to add a new link each month?
>>>
>>>Regards,
>>>
>>>Jerry
>>>
>>>----------------------------------------------------------------------
>>>--
>>>
>>>JERRY SILVER
>>>Director, Product Management
>>>BLAST RADIUS Product Division
>>>www.blastradius.com <http://www.blastradius.com/>
>>>
>>>direct 	+1 604 697 8708
>>>mobile 	+1 604 786 3505
>>>email 	jerry.silver@blastradius.com <mailto:jerry.silver@blastradius.com>
>>>
>>>
>>>
>>>---------------------------------------------------------------------
>>>This publicly archived list is provided by OASIS for the use of the 
>>>Editorial Board of the XML.org DITA Focus Area. Subscription and 
>>>posting privileges are reserved for members of the Editorial Board; 
>>>others should contact communications@oasis-open.org for assistance.
>>>
>>>[Un]Subscribe: dita-fa-edboard-[un]subscribe@lists.xml.org
>>>List archives: http://lists.xml.org/archives/dita-fa-edboard
>>>Committee homepage: http://www.oasis-open.org/committees/dita
>>>
>>>   
>>>
>>>      
>>>
>>---------------------------------------------------------------------
>>This publicly archived list is provided by OASIS for the use of the 
>>Editorial Board of the XML.org DITA Focus Area. Subscription and 
>>posting privileges are reserved for members of the Editorial Board; others should contact communications@oasis-open.org for
>>    
>>
>assistance.
>  
>
>>[Un]Subscribe: dita-fa-edboard-[un]subscribe@lists.xml.org
>>List archives: http://lists.xml.org/archives/dita-fa-edboard
>>Committee homepage: http://www.oasis-open.org/committees/dita
>>
>>
>>
>>
>>
>>
>>
>>
>> 
>>
>>    
>>
>
>
>---------------------------------------------------------------------
>This publicly archived list is provided by OASIS for the use of the Editorial Board of the XML.org DITA Focus Area. Subscription and
>posting privileges are reserved for members of the Editorial Board; others should contact communications@oasis-open.org for
>assistance.
>
>[Un]Subscribe: dita-fa-edboard-[un]subscribe@lists.xml.org
>List archives: http://lists.xml.org/archives/dita-fa-edboard
>Committee homepage: http://www.oasis-open.org/committees/dita
>
>
>
>
>
>
>
>
>  
>





 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS