For your newsgroups file: alt.binaries.vcd Video CD compliant files. CHARTER ------------------- The purpose of this newsgroup is to provide a dedicated forum to exchange Video CD compliant video images (VCD). For the purposes of this and other related newsgroups in this hierarchy, a "Video CD compliant video image" is defined as a single binary file which contains all of the data necessary which, when burned to a CDR or CDRW compact disc, will allow that CDR or CDRW to be played in a standalone VCD player or such other player that will play VCD compatible CDRs and CDRWs. VCD players include, but are not limited to, DVD players, some game consoles and computer DVD/CD-ROM readers. Further definitions are listed below in the Acceptable Postings section. Subscribers to this group are expected to own or have access to devices capable of writing CD-R or CD-RW media from the images that are provided, however, these images may also be viewed on a computer by playing the video image stream using a software MPEG multimedia player application. Subscribers to this group are expected to subscribe to a premium news service or otherwise have access to a news server with ample binary article completeness and retention. Definitions ------------------- IMAGE (also MOVIE): The movie or video itself. Also, an archive of the movie or video, as in an Archive Image. (video.mpg, video.bin, video.rar) FILE: The individual files that get posted to Usenet. Together these files (or parts) comprise the archived movie image. (video.rar, video.r00, video.r01) SEGMENT: The smaller sections that make up an archive part. (video.rar (1/32), video.rar (2/32), video.rar (3/32) REPOST: Posting the same article or video again (an archive part or an entire movie) ARTICLE (or USENET ARTICLE): Any message posted to Usenet containing a Message ID. PAR Files: Redundant Parity data files. The software equivalent of hard drive RAID that can be used to reconstruct missing data. Acceptable Postings ------------------- The following requirements describe acceptable and unacceptable posts in alt.binaries.vcd: 1. All images submitted SHALL conform to the "White Book" Video CD specifications, which are outlined in the "VIDEO CD SPECIFICATION VERSION 2.0" by Philips Consumer Electronics and the MPEG Standard (ISO/IEC 111172) documents. If, at any time in the future, the "White Book" specifications defining the Video CD should change, then all postings to this group SHALL conform to the updated specifications, and the updated specifications SHALL take precedence over any such specifications listed in this Charter. If the potential submitter is unsure of compliance with these requirements, the question should be asked in the discussion newsgroup, alt.binaries.vcd.d, and a majority consensus of those participating in the group reached before submitting posts containing binary data. See "Additional Information" (below) for other sources of information on the preparation process. Lack of response WILL NOT be considered a valid reason to submit such material. 2. All data contained in the image file SHALL BE an exact digital representation of a VCD "White Book" compliant image and SHALL NOT have to be further processed in any way in order to bring the image within compliance. Super Video CD (SVCD) or any type of non-compliant "extended" VCD (XVCD, XSVCD) SHALL NOT be posted to alt.binaries.vcd and MAY BE posted to a newsgroup specifically for that purpose. Acceptable video images include: MPEG-1 format files which may be burned in VCD format to a CD with any Video CD compliant burning software. Raw Data files (such as BIN and CUE or other such format) so as to allow the reimaging of the original multi-track VCD when burned. If posting a BIN/CUE file the poster MUST indicate the source of the BIN/CUE and the application used to create them, i.e., is it imaged from a physical CD or was it created via a BIN/CUE creation software application prior to actually burning the image to a CD. Any video image requiring additional digital processing in order to bring the file to within specifications for playback on either a standalone compatible VCD player or a software VCD player, including, but not limited to, the adjustments of the audio layer, audio bitrate, video bitrate, total bitrate, frame size, frame rate, system clock reference video pack size, audio pack size plus padding, or last pack size are NOT considered VCD compliant images and are therefore not acceptable. 3. Non-VCD compliant binary articles SHALL NOT be posted to the group. This includes, but is not limited to, application software of any kind, tools or utilities for the purpose of downloading or the posting of articles to Usenet, tools or utilities for the purpose of processing video images, tools or utilities for the purpose of CRC validation or parity data reconstruction, picture images such as BMP, GIF or JPEG (unless the picture images are to support a VCD image file being posted), and audio or sound files. There are specific newsgroups for those purposes and should therefore be used as such. Non-VCD compliant posting exceptions: A.) [See section 5 of Group Etiquette below] Non-VCD compliant documents that support the compliant image being posted are permissible. These include, but are not limited to, information files (NFO) that give details about the image being posted, SVF files or other such CRC data files, parity data files (PAR files) and VCD/CD cover picture images (GIF, JPG, BMP, etc). 4. Non-binary articles SHALL NOT be posted to this group. All non-binary articles SHALL BE posted only to the discussion group for this newsgroup, alt.binaries.vcd.d or to the repost group as necessary. 5. A binary posting news client SHALL NOT be used to post text or binary attachments of any kind in lieu of posting a text message with a standard news client. Non-binary article posting exceptions: A.) Non-binary messages may accompany a binary file that is being posted provided the messages contain relevant information concerning the file being posted. B.) Article postings that do not comply with this Charter may be responded to with an informational reply regarding group policies and may point the user to the discussion group, this Charter, and/or any relevant FAQs (Frequently Asked Questions documents). All responses to such non-compliant articles MUST contain a Followup-To: header, redirecting subsequent replying posts to the discussion newsgroup or otherwise relevant newsgroup. Respondents to a message containing a proper Followup-To: SHALL NOT alter the newsgroup listed in the Followup-To: header. 6. Articles containing an advertisement for a commercial product or service (also known as "spam") or containing pornography or links to pornographic sites SHALL NOT be posted to this group. This includes, but is not limited to, "Make Money Fast" chain letters, "For Sale" announcements and ads for any type of Web site, IRC channel, audio or video feed. 7. Articles crossposted into or from other non-related newsgroups are considered spam and are not permitted. Crossposted articles to and from ANY non-binary group, including alt.binaries.vcd.d, are considered spam and are not permitted. Articles crossposted into or from any related newsgroup MUST conform to the charters of all groups to which the articles are posted to. 8. If an image requires disc layout information (generally referred to as a "cue sheet" or "layout file") or other data, all of these special components SHALL BE posted with the image, preferably at the beginning of the post or within the archive. 9. Once an image has been posted in its entirety to this newsgroup, the same title SHALL NOT be reposted to this newsgroup for a minimum of 30 days. A posting of the same video image, even though a different archive set, is considered a repost - regardless of the time span between postings. A posting of the same image by someone other than the original poster is considered a repost. A repost of an image MAY BE posted to a newsgroup specifically designed for that purpose, such as alt.binaries.vcd.repost, provided it conforms to that newsgroup's charter and posting practices. Missing or incomplete parts of an image SHALL NOT be posted or reposted to this newsgroup. Missing or incomplete parts of an image MAY BE posted or reposted to a newsgroup specifically designed for that purpose, such as alt.binaries.vcd.repost. Exceptions: If any of the parts of an image do not propagate past the poster's news server due to the news server having technical difficulties, the file MAY BE reposted to this group. If there is any question as to the nature of the problem, discussion and a majority consensus MUST BE reached in dealing with the problem before the repost is to take place. If any of the parts did not initially make it to the poster's server then a reposting of the files is not considered a repost and SHOULD BE posted to this newsgroup. If a repost of this type occurs, the subject line of the messages headers SHALL indicate RETRY and SHALL NOT use the word: REPOST, as the word 'REPOST' will incorrectly convey to new users that reposts are allowed in this newsgroup. If the posting client allows the reposting or resending of missing segments of a file then the missing segments SHALL BE reposted without any alteration of the Subject headers. A newer release of the same image, or a different foreign language or subtitled version, or special edition of the same image or title that is functionally different (not just repackaged) MAY BE posted at any time, provided that ALL of the processes stated in the Charter are repeated before that posting, including discussion in the discussion group. 10. HTML text, whether in the body of a message or in a signature (sig), is not permitted. Group Etiquette ---------------- 1. At least 48 hours prior to any VCD image submission to alt.binaries.vcd, an article proposing the image MUST BE sent to the discussion group, alt.binaries.vcd.d. This post should place in the Subject: line the phrase, "OFFER:", or "INTENT TO POST:" or some other header information intended to convey an offer of an intent to post a binary image. This MUST BE done in order to determine if there is sufficient positive interest in the file being offered. Sufficient positive interest is defined as an acceptable number of people who would like to see the file posted to warrant the use of bandwidth and other limited Usenet resources. Based on the responses, common sense should be employed as whether or not a file should be posted. 2. An INTENT TO POST text article MAY be submitted to alt.binaries.vcd for approval provided the Followup-To: header is set to redirect any replies to the discussion group. In addition to the INTENT TO POST article being sent to alt.binaries.vcd.d, a sample of the image proposed SHOULD BE posted to alt.binaries.vcd. The binary image sample should include the INTENT TO POST header and MUST include a Followup-To: header, redirecting subsequent replying posts to the discussion newsgroup. 3. This group deals primarily with VCD compliant movie files of all types, but also other VCD compliant images such as concert video, and other multimedia content. Television shows, anime, erotica and other VCD content for which there is a more appropriate newsgroup specifically designed for that purpose SHALL BE posted to those newsgroups and SHALL NOT be crossposted into alt.binaries.vcd. If users are unsure whether a specific title belongs in the group, the discussion phase of the INTENT TO POST will determine its appropriateness for this newsgroup. 4. In order to conserve bandwidth and utilize all available resources efficiently, if there are insufficient responses expressing interest in the proposal, the binary submission SHALL NOT be made. 5. If there is sufficient interest after the full 48 hours have elapsed the proponent MAY proceed in posting the image following the format requirements outlined in this Charter. Sufficient immediate interest alone is not enough to warrant the posting of an image. The full 48 hours MUST pass so as to allow any dissenting opinions as to why something should not be posted. This will also allow people to better plan the use of their own resources if they can anticipate the posting of a particular file. Only responses in the discussion group are to be considered in determining if there is any interest. Header-only replies in alt.binaries.vcd are not to be considered as either positive or negative. 6. Requests for files, reposts of missing or corrupted parts of an image file, or binary posts of any nature, SHALL NOT be placed in alt.binaries.vcd. All requests SHOULD be placed in alt.binaries.vcd.repost or some other more appropriate newsgroup. Any such request in the binary group constitutes a non-binary article and is expressly forbidden by this Charter. In the event of a widespread delivery or corruption problem, discussion in alt.binaries.vcd.d will determine the best way to resolve the situation. 7. Along with each video image posted, an informational text file (i.e., NFO file) MUST BE posted. The text file MUST BE standard ASCII text. The file extension SHOULD BE ".NFO" but MAY BE ".txt". This same information MUST BE included as in-line text (not as a file attachment) when posting an 'INTENT TO POST' in the discussion group. Suggested information to be included within a NFO file: Movie title or Internet Movie Database (IMDb) URL Plot summary (or IMDb URL of title) IMDb rating Run time Format (MPG, BIN/CUE, etc.) Number of discs Image file size Archive file size Number of archive parts Number of PARity files or parity data percentages Posting schedule (parts per day, MB's per day) Reposting policy Technical notes Technical specifications Any other information or comments the poster may wish to include. The use of automated NFO generators that include this information or use of a widely-accepted NFO template (available from the FAQs or from prior postings) is recommended to ensure that the recommended data is included. While the posting of an NFO file in the binary group is within the guidelines of the Charter, all content of NFOs SHOULD BE pasted into the body of any INTENT TO POST article posted in the discussion group to avoid the posting of binary file attachments. Please refer to the charters of the other groups mentioned for their own policies. 8. Parity data files (PAR files) SHOULD BE posted as part of the original archive files. The number of PAR files SHALL BE based on a percentage of the total data posted so as to allow reliable data file recovery of incomplete files from competent news servers. Generally, at least 10%, but not more than 20%, is sufficient for data recovery. The actual number of PAR files to be posted is solely at the discretion of the poster. Once the PAR files have been posted to alt.binaries.vcd, any subsequent postings SHALL BE considered a repost and SHALL BE posted to alt.binaries.vcd.repost. If additional PAR files are created for any reason they MAY BE initially posted to alt.binaries.vcd without being considered a repost. Any subsequent postings of additionally-created PAR files SHALL BE posted to alt.binaries.vcd.repost. 9. File names SHOULD BE in the standard 8+3 naming convention to avoid truncation problems and for better cross-platform compatibility. File names SHALL NOT be any longer than 31 characters. Filenames SHALL NOT contain ACSII Control Codes or non-standard alphanumeric characters. Posting Format, Volume and Frequency Requirements ------------------------------------------------- 1. The VCD compliant image file MUST BE compressed and split into multiple files (parts) using an archival tool that incorporates RAR (preferred), JAR, ACE, ZIP or other such accepted compression format as agreed upon by the majority of the users. 2. Each compressed part SHOULD BE no smaller than 3 megabytes and no larger than 20 megabytes in size, except for the last part of the archive which may be smaller. The smaller the compressed part, the greater the propagation. In many instances a 5 megabyte file will propagate better than a 15 megabyte file. Each part of the archive MUST contain any recovery and/or reassembly and validation information that the archival tool generates. 3. Prior to posting, the submitter MUST reassemble the VCD compliant binary from the separate parts, test the validation information, burn the image (if applicable), and test it for playback compatibility to ensure that no corruption of data has occurred during the disassembly and reassembly process. Accepted validation tools include, but are not limited to, QuickSFV, SFV32w, FastSFV, Checkerz, Validate and TreeCRC, all of which may be found by searching the World Wide Web. For PAR files, acceptable tools include, but are not limited to, SmartPar and FSRAID. Any validation or parity program which outputs the same results as would be obtained by one of the programs mentioned above, and the output is compatible for use with the above-mentioned programs, may be utilized, as well. Any new validation or parity tools that are not compatible with the above listed applications MUST BE discussed, and a positive consensus reached in the discussion group before utilizing them in a binary posting. Lack of response will not be considered a valid reason to submit video images validated with any new validation tool. 4. The submitter shall put forth a reasonable effort to ensure the files posted are free from any virus, Trojan Horse, or anything that might act as such. The submitter is also responsible for checking their news article submission software and operating system for viruses PRIOR to a binary submission. Potential submissions that fail ANY of these tests MUST NOT be posted. 5. Each 3 to 20 megabyte file (described in #2, above) SHALL BE encoded for submission using the most widely-accepted method of binary encoding. Experimental and narrowly-supported binary file encoding formats are not acceptable and SHALL NOT be submitted. Due to the fact that binary files with large part and segment sizes are not widely propagated by many news servers, the size of each encoded part of each file MUST BE of acceptable size in order to facilitate sufficient Usenet news server propagation. Posting size guidelines are as follows: The file segment size SHALL NOT exceed 500 kilobytes (approximately 8,126 lines). Segment sizes of between 250 kilobytes (approximately 4,063 lines) and 461 kilobytes (approximately 7,500 lines) are highly recommended. The minimum part size SHALL NOT be smaller than 100K (approximately 1587 lines). 6. The files SHALL NOT be encrypted in any form or employ privately distributed passwords of any type. 7. The parts SHALL BE posted in sequence, but limited to no more than 400 megabytes of encoded data per day. This 400 megabyte limit SHALL include all data that is posted, including sample files, support and PAR files. An entire image SHALL NOT be posted in a single day UNLESS the complete encoded image size and all accompanying files is less than 400 megabytes. If, at such time in the future, the Internet and Usenet infrastructure conditions are appreciably upgraded to allow the primary method of access to the Internet by a majority of users via a broadband connection (also known as universal broadband acceptance), and the Internet and Usenet infrastructures are updated to handle the increased bandwidth, then these posting size limits MAY BE amended by the majority of the users within this newsgroup to utilize the upgraded infrastructure conditions. An informed decision and discussion by the proponents will determine the status of any infrastructure improvements. 8. When an image is posted to alt.binaries.vcd, the Followup-To: header SHALL BE set to have any replies to the message be directed to the appropriate newsgroup. For the vast majority of image postings, the appropriate newsgroup SHOULD BE alt.binaries.vcd.repost, as that is what most of the replies will deal with, and replies asking for a repost or fill are most appropriately placed in the repost group. Follow-ups to the discussion group are to be discouraged (but not expressly forbidden by this Charter) since most of the discussions concerning the post will have already taken place during the INTENT TO POST phase. In short, clicking the message and hitting REPLY in order to request a missing segment or part is the way it SHOULD BE done. This is the quickest, easiest and most intuitive way to do it. To which newsgroup that request actually gets posted to is to be determined by the poster of the file. The Followup-To: header SHOULD direct all replies to the repost group. If the Followup-To: header is left blank by the poster then the reply will be directed to this newsgroup. The object is to have ALL binary articles posted to alt.binaries.vcd include a Followup-To: alt.binaries.vcd.repost header. If the header is altered so as to force the reply for a requested part or segment to be posted to this newsgroup, the reply SHALL BE ignored. 9. When an image is posted, the Subject: line of the message SHOULD begin with the word "FILE", "IMAGE", "VCD", the name of the movie, or anything to denote it as a VCD compliant binary posting header. The Subject: line SHOULD NOT begin with any non-standard numeric or alpha character including, but not limited to, any "attention-getters" such as punctuation marks, exclamation marks, pound signs, etc. While not necessarily spam, articles beginning with these types of characters are often filtered out, as with traditional attention-getting spam, by both end users and many news services. The Subject: line SHALL BE kept as short as possible to allow for the easy reading of the header. Run-on headers, excessively long headers, entire message bodies in the headers, or any information unrelated to the file being posted, such as a request of any kind, SHALL NOT be posted. The standard for posting a binary file to Usenet is: Subject: FILE: A very brief description of the file - file x of n - {filename.ext} Examples include: Subject: Moviename - disc 1 of 2 - day 1 of 5 - {filename.ext} Subject: Moviename - Telecine - disc 1 of 2 - day 1 of 5 - {filename.ext} Many other variations are acceptable. The primary goal is to keep the Subject headers neat and easy to read. Additional Information on alt.binaries.vcd ----------------------------------------------- Proponents of this group actively maintain a list of Frequently Asked Questions (FAQ) and other helpful files on building, testing, posting, retrieving and re-assembling binary and VCD compliant images. The files, themselves, or pointers to these and other related materials, are posted regularly to the discussion and utility newsgroups. The FAQ for this newsgroup and any other related FAQs may be housed at a Web site, the location of which (if available) may be obtained from any regular participant of the newsgroup. The newsgroup also conforms to the basic rules of Usenet and Usenet behavior as laid out in the Usenet FAQs that are regularly posted to the news.announce.newusers newsgroup. These materials should be reviewed carefully prior to posting a question in the discussion newsgroup and before posting content to alt.binaries.vcd. REASON FOR NEWSGROUP ------------------- This newsgroup was improperly newgrouped without a charter. At the suggestion of several news administrators, this document is being created expressly for the purpose of giving alt.binaries.vcd a valid charter, and to rectify something, which, over time, has become a problem with news administrators as well as individuals trying to determine where to post articles. Many files are being duplicated (not merely crossposted) due to the disorganized state of many of these types of newsgroups. JUSTIFICATION ------------------- This newsgroup was created on Sun Dec 6, 1998 with no charter and no discussion. Traffic measurements indicate a high volume of traffic to this already-existing newsgroup. Precise traffic measurement numbers are not needed to justify the group, itself, as news administrators are very well aware of the traffic. However, this Charter fixes the problem of an improperly created group.