[USPS-Webmasters] Check out http://www.usps.org/national/itcom/shared/pol...
Bill Ray
bray@apian.com
Wed, 30 Mar 2005 11:53:07 -0800
This is a multi-part message in MIME format.
------_=_NextPart_001_01C53562.1831B98A
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
It seems to me that the site should be kept up to date, but that it
should be the webmaster's prerogative to include historical and future
information as they see fit so long as the intent is clear. =20
=20
Saying prominently "Our next public boating class is January 2005" would
be unacceptable now. However listing that a class happened 1/2005
should be perfectly reasonable, say in an archive of past Newsletters or
calendars, or having a photo from last fall's class. We keep several
issues of the Newsletter on-line and have photos from past events, a
history page that goes back to the Squadron's founding, and our calendar
looks ahead to 2006.
=20
The choice of how to show it is 'past' is a matter of style for the
webmaster to decide including simple context such as a page labeled Jan
2005 Newsletter. Seems to me the criteria should be that the
communication should be 'current' as fits its purpose.
=20
Bill Ray
Seattle
=20
_____ =20
From: BSURuss@aol.com [mailto:BSURuss@aol.com]=20
Sent: Wednesday, March 30, 2005 11:09 AM
To: WMMILLER@aol.com; usps-webmasters@usps.org
Subject: Re: [USPS-Webmasters] Check out
http://www.usps.org/national/itcom/shared/pol...
=20
In a message dated 3/30/2005 12:58:45 A.M. US Eastern Standard Time,
WMMILLER@aol.com writes:
Click here:
http://www.usps.org/national/itcom/shared/policy/weballdoc.doc
<http://www.usps.org/national/itcom/shared/policy/weballdoc.doc> =20
=20
Here is your first opportunity to review the revised rules for
all websites in USPS. Note we are stressing the subtitles section of
the rules as well as having the information on the website up to date.
These rules will form the basis of this years webawards program. There
will be specific rules posted, hopefully by the end of April.
=20
Bill Miller
Website Coordinator
Bill,
=20
Regarding the updated rule.....
=20
1) Web site must be kept up to date - required=20
Any web site, which contains meeting, activities and/or pubic boating
course information that is 90 days or more out of date, may be removed
from linking to the national site. It is extremely important to keep
websites up to date. Any website found not current in their schedule
dates for events and educational programs will not be considered in any
awards evaluations. Note there is no grace period for the awards
program. If past dates are listed on websites they should be identified
as past events, such as by change in font style or color or within a
shaded background such as in a calendar format. Items that are date
referenced, such as the VSC Decal should show the present years version.
=20
Our squadron elects to post our entire annual watch year meeting/social
calendar at the beginning of the year so members can plan ahead. I
generally highlight the next one or two upcoming events so members can
easily spot where they are on our calendar. I keep all of the past
events listed on our calendar for several reasons. The most important
reason that we show all events - past and upcoming - is to provide
prospective members with a clear, complete picture of our annual
programming - which we feel is quite good. Our squadron is active, and
we want prospective members to easily see that. Aside from making sense
for that reason alone, in my opinion this should be a squadron decision
- not a USPS decision. Also, in my humble opinion, I'm guessing that
when I list past dates on our web calendar ... our members are sharp
enough to understand that those dates have already occurred without me
needing to explain how that works or identifying them as such. =20
=20
In short, I'm all for keeping current, and I believe a requirement for
USPS websites to keep updated on upcoming events makes sense. However,
I frankly feel that the decision to show past events is the local
squadron's call - not that of USPS and certainly not left up to the
variable interpretation of the individual reviewers. Anytime USPS
unlinks a local squadron's website, USPS is shooting itself in the foot
by reducing promotional reach created by our website network. This is
important given our membership trend. I realize that we don't need to
expose prospective members to 'lousy' outdated local websites as a
matter of image. However, rather than threaten to unlink websites for
being out of date, I can't help but believe that there would be some way
to work with these sites to help them improve on this criterion (rather
than simply pulling the plug). This would help both the local websites
and USPS rather than coming across as punitive. =20
=20
I realize that I'm raising a trivial issue. However, the reviewer in
the most recent evaluation apparently took exception to our practice
vis-a-vis ratings even though our website was meticulously up to date on
upcoming meetings, social events, and classes. Out of curiosity I
compared our site's rating on this criterion to other sites that were
grossly outdated on upcoming schedules and curiously found no consistent
difference in ratings. I'm attributing that to an inter-rater
reliability issue. However, that could be improved by tightening up the
wording of the criteria as in this case. I'm wondering when our
evaluations are conducted next fall if I need to somehow point out to
the reviewer that summer events have already passed in order to earn
points on this scoring criterion. Just a suggestion.
=20
Russ Wahlers
Hoosier Power Squadron - Indianapolis
------_=_NextPart_001_01C53562.1831B98A
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dblue id=3D"role_body" =
bottomMargin=3D7
leftmargin=3D7 topmargin=3D7 rightMargin=3D7>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>It seems to me that the site should =
be
kept up to date, but that it should be the webmaster’s prerogative =
to include
historical and future information as they see fit so long as the intent =
is
clear. <o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Saying prominently “Our next =
public
boating class is January 2005” would be unacceptable now. =
However listing
that a class happened 1/2005 should be perfectly reasonable, say in an =
archive
of past Newsletters or calendars, or having a photo from last =
fall’s
class. We keep several issues of the Newsletter on-line and have =
photos from past
events, a history page that goes back to the Squadron’s founding, =
and our
calendar looks ahead to 2006.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>The choice of how to show it is =
‘past’
is a matter of style for the webmaster to decide including simple =
context such
as a page labeled Jan 2005 Newsletter. Seems to me the criteria =
should be that
the communication should be ‘current’ as fits its =
purpose.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><st1:PersonName w:st=3D"on"><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Bill
Ray</span></font></st1:PersonName><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>
<p class=3DMsoNormal><st1:City w:st=3D"on"><st1:place w:st=3D"on"><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>Seattle</span></font></st1:place></st1:City><font size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>
<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>
</span></font></div>
<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
BSURuss@aol.com
[mailto:BSURuss@aol.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, March =
30, 2005
11:09 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> WMMILLER@aol.com;
usps-webmasters@usps.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: =
[USPS-Webmasters]
Check out =
http://www.usps.org/national/itcom/shared/pol...</span></font><o:p></o:p>=
</p>
</div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>In a message dated 3/30/2005 =
12:58:45
A.M. US Eastern Standard Time, WMMILLER@aol.com =
writes:<o:p></o:p></span></font></p>
</div>
<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt'>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'><a
href=3D"http://www.usps.org/national/itcom/shared/policy/weballdoc.doc"
title=3D"http://www.usps.org/national/itcom/shared/policy/weballdoc.doc">=
Click here:
http://www.usps.org/national/itcom/shared/policy/weballdoc.doc</a> =
<o:p></o:p></span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'> <o:p></o:p></span></font></p>=
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Here is your first opportunity to =
review
the revised rules for all websites in USPS. Note we are stressing =
the
subtitles section of the rules as well as having the information on the =
website
up to date. These rules will form the basis of this years =
webawards
program. There will be specific rules posted, hopefully by the end =
of
April.<o:p></o:p></span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'> <o:p></o:p></span></font></p>=
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Bill =
Miller<o:p></o:p></span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Website =
Coordinator<o:p></o:p></span></font></p>
</div>
</blockquote>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Bill,<o:p></o:p></span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'> <o:p></o:p></span></font></p>=
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Regarding the updated =
rule.....<o:p></o:p></span></font></p>
</div>
<div>
<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'> <o:p></o:p></span></font></p>=
</div>
<div>
<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in'><font size=3D3
color=3Dblack face=3DArial><span =
style=3D'font-size:12.0pt;font-family:Arial;
color:black'>1)</span></font><font size=3D1 color=3Dblack><span =
style=3D'font-size:
7.0pt;color:black'> =
</span></font><b><font
color=3Dblack face=3DArial><span =
style=3D'font-family:Arial;color:black;font-weight:
bold'>Web site must be kept up to date</span></font></b><font =
color=3Dblack
face=3DArial><span style=3D'font-family:Arial;color:black'> - =
<em><i><font
face=3DArial><span =
style=3D'font-family:Arial'>required</span></font></i></em> =
<o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:12.0pt;font-family:Arial;color:black'>Any web
site, which contains meeting, activities and/or pubic boating course
information that is 90 days or more out of date, may be removed from =
linking to
the national site. It is extremely important to keep websites up to =
date. Any
website found not current in their schedule dates for events and =
educational
programs will not be considered in any awards evaluations. Note =
there is no
grace period for the awards program. </span></font><font =
color=3Dred face=3DArial><span
style=3D'font-family:Arial;color:red'>If past dates are listed on =
websites they
should be identified as past events, such as by change in font style or =
color
or within a shaded background such as in a calendar =
format.</span></font><font
color=3Dblack face=3DArial><span =
style=3D'font-family:Arial;color:black'> Items that
are date referenced, such as the VSC Decal should show the present years
version.</span></font><font color=3Dblack><span =
style=3D'color:black'><o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'> <o:p></o:p></span></font></p=
>
<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:12.0pt;font-family:Arial;color:black'>Our
squadron elects to post our entire annual watch year meeting/social
calendar at the beginning of the year so members can plan ahead. I
generally highlight the next one or two upcoming events so members can =
easily
spot where they are on our calendar. I keep all of the past events =
listed
on our calendar for several reasons. The most important =
reason that
we show all events - past and upcoming - is to provide prospective =
members with
a clear, complete picture of our annual programming - which we feel =
is
quite good. Our squadron is active, and we want prospective =
members to
easily see that. Aside from making sense for that reason alone, in =
my
opinion this should be a squadron decision - not a USPS decision. =
Also,
in my humble opinion, I'm guessing that when I list past dates on our =
web calendar
... our members are sharp enough to understand that those dates have
already occurred without me needing to explain how that works or
identifying them as such. </span></font><font color=3Dblack><span
style=3D'color:black'><o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'> <o:p></o:p></span></font></p=
>
<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:12.0pt;font-family:Arial;color:black'>In
short, I'm all for keeping current, and I believe a requirement for USPS
websites to keep updated on upcoming events makes sense. However, =
I
frankly feel that the decision to show past events is the local =
squadron's call
- not that of USPS and certainly not left up to the variable =
interpretation of
the individual reviewers. Anytime USPS unlinks a local squadron's
website, USPS is shooting itself in the foot by reducing promotional =
reach
created by our website network. This is important given our =
membership
trend. I realize that we don't need to expose prospective members
to 'lousy' outdated local websites as a matter of image.
However, rather than threaten to unlink websites for being out of date, =
I can't
help but believe that there would be some way to work with these sites =
to help
them improve on this criterion (rather than simply pulling the =
plug).
This would help both the local websites and USPS rather than coming =
across as
punitive. </span></font><font color=3Dblack><span =
style=3D'color:black'><o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'> <o:p></o:p></span></font></p=
>
<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:12.0pt;font-family:Arial;color:black'>I
realize that I'm raising a trivial issue. However, the reviewer in =
the
most recent evaluation apparently took exception to our practice =
vis-a-vis
ratings even though our website was meticulously up to date on upcoming
meetings, social events, and classes. Out of curiosity I compared =
our
site's rating on this criterion to other sites that were grossly =
outdated on
upcoming schedules and curiously found no consistent difference in
ratings. I'm attributing that to an inter-rater reliability =
issue.
However, that could be improved by tightening up the wording of the =
criteria as
in this case. I'm wondering when our evaluations are conducted =
next fall
if I need to somehow point out to the reviewer that summer events have =
already
passed in order to earn points on this scoring criterion. Just a
suggestion.</span></font><font color=3Dblack><span =
style=3D'color:black'><o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:black'> <o:p></o:p></span></font></p=
>
<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:12.0pt;font-family:Arial;color:black'>Russ
Wahlers</span></font><font color=3Dblack><span =
style=3D'color:black'><o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:12.0pt;font-family:Arial;color:black'>Hoosier
Power Squadron - <st1:City w:st=3D"on"><st1:place =
w:st=3D"on">Indianapolis</st1:place></st1:City></span></font><font
color=3Dblack><span style=3D'color:black'><o:p></o:p></span></font></p>
</div>
</div>
</body>
</html>
------_=_NextPart_001_01C53562.1831B98A--