[Webmaster_forum] Re: [USPS-Webmasters] Website Requirement #11
KPolt@aol.com
KPolt@aol.com
Sun, 14 Aug 2005 13:04:25 EDT
-------------------------------1124039065
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
I understand the intent of the requirement, and I agree that websites should
be kept reasonably up to date. I also agree that the full-year calendar of
events is a very good tool to show members and visitors alike what the squadron
is all about. The requirement is asking for "some indication of what events
have already transpired." I believe that it is intuitively obvious to the most
casual observer that today is 14 August 2005, and any event listed with a
date of 13 August 2005 or older has indeed already transpired. Doesn't the
calendar, by it's nature of being a calendar, comply with the intent? I don't
understand the need to be really innovative on this.
Respectfully,
Kay Polt
LRGV
In a message dated 8/14/2005 10:25:47 AM Central Daylight Time,
WMMILLER@aol.com writes:
Many websites have an entire year long calendar of events displayed. That is
certainly allowed in this rule, as long as there is some indication of what
events have already transpired. Many websites have come up with innovative
means to make such a distinction. This presentation of past and future dates has
two benefits. First it gives visitors to the website some idea as to the
depth of activities available to members of the organization. Second it provides
information about future events yet to occur, and should provide an
appropriate contact for the various events.
-------------------------------1124039065
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<HTML><HEAD>
<META charset=3DUS-ASCII http-equiv=3DContent-Type content=3D"text/html; cha=
rset=3DUS-ASCII">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR></HEAD>
<BODY style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; BACKGROUND-COLOR: #fffff=
f">
<DIV>
<DIV>I understand the intent of the requirement, and I agree that websites s=
hould be kept reasonably up to date. I also agree that the full-year c=
alendar of events is a very good tool to show members and visitors alik=
e what the squadron is all about. The requirement is asking for "=
some indication of what events have already transpired." I believ=
e that it is intuitively obvious to the most casual observer that today is 1=
4 August 2005, and any event listed with a date of 13 August 2005 or older h=
as indeed already transpired. Doesn't the calendar, by it's nature of=20=
being a calendar, comply with the intent? I don't understand the need=20=
to be really innovative on this.</DIV>
<DIV> </DIV>
<DIV>Respectfully,</DIV>
<DIV>Kay Polt</DIV>
<DIV>LRGV</DIV>
<DIV> </DIV>
<DIV>In a message dated 8/14/2005 10:25:47 AM Central Daylight Time, WMMILLE=
R@aol.com writes:</DIV>
<BLOCKQUOTE style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue=20=
2px solid"><FONT face=3DArial size=3D2>Many websites have an entire year lon=
g calendar of events displayed. That is certainly allowed in this rule=
, as long as there is some indication of what events have already transpired=
. Many websites have come up with innovative means to make such a dist=
inction. This presentation of past and future dates has two benefits.&=
nbsp; First it gives visitors to the website some idea as to the depth of ac=
tivities available to members of the organization. Second it provides=20=
information about future events yet to occur, and should provide an appropri=
ate contact for the various events.</FONT></BLOCKQUOTE></DIV>
<DIV></DIV></BODY></HTML>
-------------------------------1124039065--