[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [atlarge-discuss] Re: [wg-web] RE: [atlarge-discuss] RE:[atlarge-panel] Web Site Updates?
Jaz-Michael and all stakeholders or other interested parties and members,
This is good stuff here Jaz-Michael. Thank you for providing it.
I hope others will have some other Web Publishing and management
procedures and standards to posts as well so that we can as
Wg-Web Participants have an opportunity to choose the best overall
set of standards or hybrid of all of them submitted to come up with our
own for ICANNATLARGE.ORG...
I have a few, very few comments to these set of procedures that
you provided below...
Jaz-Michael King wrote:
> IPRO Web Publishing Manual
First off, the title here is for "Web Publishing". The ICANNATLARGE.ORG
organization is not a web publishing organization so I would say that our
Web site should not reflect or look as though we are one...
>
>
> This manual is applicable for any IPRO staff member or consultant who creates, edits or manages content for the IPRO family of web sites.
>
> Glossary:
> C&CD Communications and Corporate Development Department
> OSM Online Services Manager
> CMS Content Management System
> QOC Quality Oversight Committee
> QC Quality Council
Ok these positions might be very appropriate for a "Web Publishing"
Web site organization/company. However as you know and I stated above,
ICANNATLARGE.ORG is not a Web Publishing organization... Hence
most of these positions are not applicable or appropriate... I would say
that the WG-Web would, should and does serve most of these positions
except perhaps the QC position which would be best held or be performed
by the WebMaster for ICANNATLARGE.ORG...
>
> Content Owner Person responsible for the authenticity, correctness and timeliness of published material
> Web Publisher Person who has access to the CMS to create or edit published material (a.k.a. Web Liaison)
> ipro.org The general web presence of IPRO (not a specific site)
>
> The IPRO family of web sites exists to support IPRO's mission: IPRO is an independent, not-for-profit corporation committed to assessing and improving the value of health care services received by consumers through the use of innovative methods and technologies.
>
> In support of this mission the web strategy includes in its objectives:
>
> * cost-effective web publishing
Again we are not a Web Publishing organization.
>
> * an integrated and editorially consistent site
As very little editorial content would appear on our Web site I can't
really see this as being relevant for ICANNATLARGE.ORG. However
Integration may be appropriate at some point.
>
> * a site that is current, complete and correct
> * a site that publishes information relevant to our situation.
>
>
> Implementation
>
> Operationally, the strategy has three levels:
>
> 1. A site layout intended to promote communication with our various users and to cover areas germane to our mission.
>
> 2. A 'whole of site' design concept and a template that promotes site branding, and which can also be used to simplify web page production by web coordinators using a database-driven web publishing system.
>
> 3. The adoption of dynamic web publishing as a philosophy, which in turn enables the company to reduce costs for web and print publications by making all publishing dependent on a common database.
>
> The web site includes the following features:
>
> * it separates content from design
> * it has a secure and advanced web publishing service
Again we are not a Web Publishing firm or organization hence this is
not really relevant to ICANNATLARGE.ORG
>
> * it has a search engine, which has the capacity to index across the whole of the content base
> * it is user oriented rather than based on organizational structure
> * it has authenticated extranet services
> * it has improved navigation for infrequent users
> * the home page gives rapid access to all major areas of the site.
>
> This reflects a change of culture for web development: from ad hoc development and duplicated efforts, to coordinated and effective use of our resources. At this stage of our development, we are implementing coordination and institutional arrangements to foster responsibility for our image and mission on the web, including proper allocation of human and financial resources.
>
> 1. Dynamic publishing
>
> Aim: to lower production, design and editorial costs and reduce the lead-time involved in publishing.
>
> Dynamic publishing relies on creating processes rather than individual files. Separating content from presentation allows production of more content more efficiently, as we eliminate individually created HTML pages and replace them with custom pages generated by the computer 'on the fly' (i.e. the pages are generated at the time of browsing). Generally, dynamic publishing relies on extracting web pages from a database and on using templates to vary presentation and design livery.
>
> Not only does dynamic publishing enable efficient updating of web site content, but it also opens opportunities to create a more personalized experience for our users. Moving in this direction permits us to improve our response to our users' need for relevant information, as they need it.
None of the above really applies again because we are not a Web Publishing
organization.
>
>
> 2. Editorial control
>
> Aim: to have a coherent and cohesive web site that adheres to publishing standards, and that is independent of our organizational structures.
>
> Lack of authority to impose editorial policy on web sites leads to web sites that are difficult to navigate and have an inconsistent style and presentation. It is difficult for users to find what they are looking for in such a site, particularly if they are not familiar with the organization.
>
> Editorial control will enable our site to cater to a wider range of interests, communicate better with our different audiences, and allow us to develop appropriate web presentation (including writing).
>
> Our web site should reflect the intellectual discipline involved in publishing, with appropriate standards for editorial style and content as they apply to the various media types to be made available on the site. Our layout should transcend our organizational structure to remove unnecessary complexity for our users.
>
> 3. Information management
>
> Aim: to publish correct and up-to-date information, both for our credibility as a health care organization and for legal reasons.
>
> Obsolete and inaccurate information on a web site damages the integrity of the site. We should adopt information management solutions to ensure that our information is current, and that there are mechanisms to prevent our web site becoming obsolete in any of its parts.
>
> Putting mechanisms in place that will ensure the completeness and currency of information is a key aspect of the development of a new site that we need to address. Such mechanisms should ensure that our web site is not isolated from our routine business, and they should recognize our contributors' roles and the partnerships needed to publish accurate and appropriate material.
>
> The web site cannot be developed in isolation from our other formal and informal publications. Nor should it be isolated from other promotional activities. A supporting network will need to be developed to achieve this.
>
> 4. Broader ownership
> Aim: to provide a broader, balanced access to publishing tools within IPRO, so that the site expresses the currency and diversity of the IPRO community.
>
> We need to define clearly those who need access to the web, and the processes necessary to publish material automatically.
>
> General Rules
>
> It is imperative that all Web Publishers follow IPRO's editorial policies and procedures to help ensure a consistent Web experience for ipro.org visitors. Adherence to these policies and procedures helps protect IPRO's brand and leverage ipro.org's common look and feel across all of IPRO's external Web sites.
>
> Web Publishers must follow all guidelines in this Web Publishing Manual. If you have questions or comments about the manual or the standards and procedures discussed within it, please send them to the Online Services Manager (OSM) webmaster@ipro.org
>
> All content must comply with the HTML Specifications, Templates, and Graphics standards as published in this manual.
>
> OSM must approve new URLs (including changing an existing URL), server names, and content for ipro.org.
> OSM must approve the addition of new technology (cgi, executables etc) to ipro.org.
>
> All IPRO Web presence must be in the ipro.org domain (e.g. medicare.ipro.org, cstimler.ipro.org). C&CD and the Web Quality Oversight Committee (QOC) must review exceptions.
>
> The single domain name for IPRO is ipro.org. Staff should not independently register or promote other domain names. If there is a domain name to be acquired by IPRO, please contact C&CD. Subdomains (something.ipro.org) can be requested from the OSM, as can home pages (ipro.org/users/yourname)
>
> Management guidelines deal with how to promote ourselves on the web site and within IPRO, how we manage official information and misinformation, staff and budget resources, cooperation and supervision, outsourcing and confidentiality, priorities, liaison within IPRO and promotion of common goals, and other legal issues, to ensure that we maintain a quality web site as suitable vehicle for advancing IPRO's mission.
>
> Contact point
>
> The point of contact who advises Content Owners and Web Publishers on web publishing within IPRO is the Online Services Manager, webmaster@ipro.org.
>
>
> Responsibilities
>
> These guidelines specify how we manage our web publishing, identifying key responsibilities and goals:
>
> * responsibility for the domain and sub domains
> * the promotion of publishing (including all supported media types) by IPRO under this manual
> * the management of the IPRO corporate web server as the principal means of achieving these aims
> * guidance on matters relating to the management of the IPRO corporate web server.
>
> The Online Services unit of C&CD is responsible for the management of services generally and the domain web services specifically within IPRO. It assumes non-exclusive, but leading responsibility for the promotion of IPRO in cyberspace through listing in directory services, portals, electronic advertising, search engines and the like.
>
> It is also the role of Online Services / C&CD to provide coordination among Content Owners, Web Publishers and the Departments.
>
> The OSM is responsible for overall editorial control and management of links and their names, the content and placement within the appropriate designated area on our web site.
>
>
> Approved staff
>
> To ensure that the site is managed in a way that fosters the mission of the company, the number of contributors will be limited to those approved by the QC and C&CD.
>
> Content Owners and Web Publishers will receive the IPRO Web Publishing email newsletter and are required to attend editorial meetings periodically.
>
> Content Owners:
>
> Page (content) ownership cascades to child pages, unless otherwise noted with an "*". All pages may be viewed by visiting the main ipro.org web site and clicking "sitemap".
>
> Company Director, Communications
> * Career Opportunities Senior Director, Human Resources
>
> Consumers Director, Consumer Protection & Outreach
>
> Event Listings Director, Communications
>
> Home Vice President, Communications
>
> Health Policy Update Director, Communications
>
> Members Area Online Services Manager
>
> News Director, Communications
>
> Newsletter Director, Communications
>
> Products and Services Senior Vice President, Program Operations
> * Encounter Data Validation Vice President, Managed Care
> * HEDIS Vice President, Managed Care
> * Managed Care Vice President, Managed Care
> * QMI Senior Vice President, Principal Clinical Coordinator
>
> Professionals
> - Anthrax Vice President, Communications
> - Managed Care Activities Vice President, Managed Care
> - Medicaid Activities Senior Vice President, Program Operations
> - Professionals Registration Vice President, Communications
> - CME Module Director, Communications
> - HCQIP Module Senior Vice President, Principal Clinical Coordinator
> - Links Vice President, Communications
> - Administrative Memos Online Services Manager
> - PEPP Vice President, PEPP
>
> Publications Online Services Manager
> Search Online Services Manager
> Site Map Online Services Manager
> * Accessibility Director, Communications
> * Copyright Notice Director, Communications
> * Privacy Policy Director, Communications
> * Terms of Service Director, Communications
> Free Headlines Online Services Manager
>
>
> Web Publishers and Content Flow
>
> Web Liaison ->
> Editorial Review ->
> Web Standards Review ->
> Content Owner Authorization ->
> Publish
>
> Each page intended for an ipro.org web site must pass through a publishing cycle before being posted to the web site. A chain of staff governs the publishing cycle; who each have varying responsibilities for the page in question.
>
> Each page or section is assigned to a Content Owner. These are the primary staff responsible for the authenticity, veracity and accuracy of the information on the pages in question. These Owners may also be responsible for checking the pages for outdated material and current timeliness on a frequent basis, and reporting the need for editing, updating or deletion as needed, although it is more likely that these duties will be delegated to Web Liaisons.
>
> Content Owners and Web Publishers who create pages must use the Content Management System located in the IPRO Extranet and must adhere to the document standards outlined in this manual.
>
> Once the content is ready for review it should be assigned Draft status, and be reviewed for completeness and evaluated for its inclusion in the site. This applies to both new content and edited content.
>
> Once editorial review is completed the content should be placed in Queue status and reviewed by Online Services for standards compliance, technical correctness and (provided no problems are found with the content) be published to the site. Any problems found at this point should be referred back to the Editorial level and re-assigned Draft status.
>
> Content that has been approved for publishing is always under the review of the QC. Content publicly available on the web sites may be converted by Online Services to various delivery formats including conversion to Microsoft Office formats, PDA-readable packages and PDF files.
>
>
> Technical Standards
>
> The site is entirely constructed using PHP, should be fully XHTML compliant and Section 508 compliant.
>
> Directories will not be named according to components (e.g., HCQIP); but rather by subject (e.g., /documents, /video). This enables a more portable structure independent of organizational changes.
>
> Every directory will have an index page.
>
> All time-sensitive sections, such as News and Press Releases should list only current-year materials on the main topic page. Archives are to be linked from the bottom of the main topic page.
>
> File formats that can be used without prior approval are:
>
> *Hypertext Markup Language (HTML) written to W3 XHTML 1.0 Transitional specifications
> *PHP pages (scripts) (PHP)
> *Portable Document Format (PDF) - Version 5 ONLY
> *Graphics Interchange Format (GIF)
> *Joint Photographic Experts Group (JPEG)
>
> File formats that may be used pending prior approval are:
>
> *Rich-Text Format (RTF)
> *Comma-Separated Values (CSV)
> *Extensible Markup Language (XML)
> *Microsoft Word
> *Microsoft Access
> *Microsoft PowerPoint
> *Portable Network Graphics (PNG)
> *Scalable Vector Graphics (SVG)
>
> Web page Guidelines
>
> General
>
> Frames, Flash and server side includes (SSI) are not allowed.
> All pages submitted must use the IPRO templates.
> All tags and attributes must be in lowercase.
> All attribute values must be enclosed in quotation (") marks.
> Ampersands (&) must be encoded as &.
> All non-empty elements must have a closing tag. For example:
>
> Close all Paragraph tags with </p>.
> Close all List Item tags with </li>.
>
> All empty elements must be closed by placing /> at the end of the start tag. For example:
>
> <br />
> <hr />
> <img ... />
>
> Include Files must be used to access boilerplate language, instead of hard-coding text.
> Include Files must have a TPL file extension (.tpl).
> JavaScript shall be used very sparingly. The author shall ensure that a) the page functions with JavaScript disabled and b) the JavaScript does not interfere with and is accessible to assistive technologies.
> Users of ipro.org must not be required to provide personal information.
> Users must specifically and knowingly provide personally identifiable information, if collected.
> The purpose of collecting personal information must be described at the point of collection.
> Persistent cookies are never allowed.
> If cookies are needed, only session cookies must be used.
>
> Stylesheet
>
> Presentation is handled by a global stylesheet (.css) file.
> All formatting will be done via stylesheets (no local formatting or presentation markup).
> All justification will be done via stylesheets.
> The <font></font> tags have been deprecated, and are not to be used. All fonts and colors are incorporated into the stylesheet through available classes.
>
> Head Section
>
> Complete author, keywords, description, and expiration date meta tags in the template.
> Author meta tags must have a component and name. For example:
> <meta name=''Author'' content=''Barbara Schwartz'' />
> Each page must have appropriate keywords and page titles.
> All meta tags must be closed using /> at the end of the start tag. (There is always a space character included)
>
> Body Section
>
> Tags and Attributes
>
> <b></b> and <i></i> are deprecated, use <strong></strong> and <em></em> instead. Use bold and italics for emphasis only
> Tables shall not use fixed widths (pixels), but shall only use percentages.
> Nested tables shall be no more than two levels deep.
> All data tables must use either <th></th>, "id", and "headers" or "scope" and "axis" to support assistive technologies. Use of <caption></caption> and "summary" is strongly encouraged.
> Complex data tables (2 levels of headers or more) must use the "scope" and "axis" attributes within the <th></th> and <td></td> tags.
> Use the lang="es" attribute on any Spanish phrases or pages.
> The first use of any acronym on a page will be spelled out followed by the acronym in parentheses. All remaining uses of that acronym on the same page will only use the acronym, with an acronym tag. Abbreviations are treated in a similar fashion.
> e.g. <abbr title="HyperText Markup Language">HTML</abbr>
>
> Links
>
> Internal links must be written in root-relative syntax, e.g. ../news, index/news.
> All external links to non-IPRO sites must pass through the "ciao" page. Use the following code on all non-IPRO external links:
> <a href=''/ciao.php?uri=http://www.your-url-here.org''>http://www.your-url-here.org</a>
> All external links to educational institutions (.edu), non-profit organizations (.org) and government agencies (.gov) are acceptable.
>
> Points of consideration for external links:
>
> *Relevance to IPRO activities and communication goals;
> *Compliance with legal obligations;
> *Sponsoring organization or person;
> *Verification of information;
> *Timeliness and review of information;
> *Qualifications to provide health or human services information or advice;
> *Disclaimers;
> *Privacy;
> *Separation of advertising and editorial content;
> *Financial interests;
> *Contact information or feedback mechanism;
> *Registration and fees.
>
> Graphics
>
> Refrain from gratuitous use of graphics.
> In general, the use of image maps is strongly discouraged.
> Image maps should be used sparingly and mostly client side.
> Server-side image maps are to be used only for maps. In this case, text-only links to each State and territory must also be made available.
> Server side image maps require equivalent text links.
> Every graphic must have an "alt" attribute with meaningful descriptions.
> Do not use clip art, photographs, other copyrighted works or copy materials from other sites without first obtaining a license agreement and Clearance.
> Labelling of all copied materials must clearly identify ownership.
> Data graphs require use of the "long desc" attribute.
> Graphical representations of signatures are not allowed.
>
> Page Design
>
> Use tables for data, not layout. The current design is already table oriented.
> When posting large documents, individual HTML files must not exceed more than 10 printed pages.
> With documents that span multiple files, a Table of Contents page should be created.
> HTML is always the preferred format.
>
> Posting of binary or proprietary formats is strongly discouraged.
> MS Office files will be posted only under special circumstances and must be zipped
> If you post a file which requires a plug-in you must a) ensure that the plug-in and content are both compliant with assistive technologies and b) use the standard "download" help files.
>
> Never use "click here" as the text for a link. Instead, use a descriptive phrase, as in the following example (where the text "Search Engine" is used as the link): Please use our Search Engine to see if your comment/concern/question is addressed elsewhere on this site.
>
> Download Files
>
> .PDF Files
>
> Adobe Acrobat 5 is IPRO's current supported standard. Previous versions are not compliant with Section 508 or other website accessibility standards; thus they will not be cleared for posting. Refer to access.adobe.com for Acrobat functionality relating to Section 508.
> For large documents which span multiple web pages, providing a PDF version of the same content provides convenience for the end user, a guarantee of better printability and a common pagination that can be used for support and reference materials.
> Material should not be published in PDF-only format. In addition to the PDF version, an HTML version of the content should be posted.
> A PDF version, if made available, should consolidate multiple HTML files into one printable PDF file. Or, if the material existed previously in Word, Quark, etc., the PDF file can be generated from the original application.
>
> .ZIP Files
>
> Large files should be compressed using the .ZIP format.
> .EXE (self-extracting executable) files are not allowed.
>
> Multimedia Guidelines
>
> Any multimedia objects that are posted must be made available in Synchronized Multimedia Integration Language (SMIL) format.
> All files must utilize RealAudio and RealVideo format.
> All files must be able to accommodate a minimum speed of 56k.
> All files must be captioned.
> Files must not include live streaming or broadcasting.
> Video clips must accept low frame rates and small window sizes.
> Resolution must be 240x180 or 176x132.
> Animation (GIFs, Shockwave, Flash, etc.) is not allowed.
> Graphical representations of signatures are not allowed.
Regards,
--
Jeffrey A. Williams
Spokesman for INEGroup - (Over 127k members/stakeholders strong!)
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number: 214-244-4827 or 972-244-3801
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208
---------------------------------------------------------------------
To unsubscribe, e-mail: atlarge-discuss-unsubscribe@lists.fitug.de
For additional commands, e-mail: atlarge-discuss-help@lists.fitug.de