Data Portal @ linkeddatafragments.org

Matches in DBpedia 2014 for { <http://dbpedia.org/resource/Prosigns_for_Morse_code> ?p ?o. }

• Prosigns_for_Morse_code abstract "In Morse code, prosigns or procedural signals are dot/dash sequences that do not represent text per se, but have a special meaning in a transmission: they are generally not copied down, they are a form of control character. They are used to indicate formatting of the text being copied or to indicate operational changes in transmission. They may be written as if they were composed of two or three ordinary alphabetic characters but they are sent "run together", omitting the normal inter-character spaces that would occur if they were being sent as normal text. These ligatures are often represented in print either by a ligating bar (overline above the letters) or by surrounding the run-together letters with angle brackets (such as <BT>), indicating that they are linked and sent as one contiguous sequence.An error may be indicated by a sequence of eight dots EEEEEEEE, or sometimes fewer spaced-out dots, the unusual 'broken' rhythm indicating an error."K", while not strictly a prosign, is normally used at the very end of a transmission to indicate "Go ahead". K, KN, and SK are also commonly used in text modes such as RTTY and PSK31. Notably, SK is also used by TTY/TDD users, though "GA" ("Go Ahead") is typed rather than "KN".Having sensible and efficient conversations in Morse code involves more than simply knowing the alphabet. To make communication efficient, there are internationally-agreed protocols or patterns of communication.Here is an example Morse code conversation between stations with the callsigns A1AA and A2BB:A1AA:CQ CQ CQ DE A1AA A1AA ARCalling anyone (CQ), this is (DE) A1AA, end of transmission (AR). A2BB:A1AA DE A2BB A2BB KNCalling A1AA, this is A2BB, back-to-you. (KN means you are inviting only the named party to reply)A1AA:A2BB DE A1AA = GA DR OM UR RST 599 HR = QTH TIMBUKTU = OP IS JOHN = HW? A2BB DE A1AA KNGood afternoon dear old man. You are RST 599 here.(Very readable (5), very strong signal (9), very good tone (9))I'm located in Timbuktu. The operator's name is John.How do you copy? Go ahead, A2BB.A2BB:A1AA DE A2BB = TNX FB RPRT DR OM JOHN UR 558 = QTH HIMALAYA = NAME IS YETI AR A1AA DE A2BB KThanks for the nice report dear old man John. I read you 558.I am in the Himalayas. My name is Yeti. That's all for this transmission (AR), go ahead.(K without the N potentially invites other callers to break in).A1AA:A2BB DE A1AA = OK TNX QSO DR YETI = 73 ES HPE CUAGN A2BB DE A1AA KOkay, thanks for this conversation, dear Yeti.Best regards and hope to see you again.A2BB:A1AA DE A2BB = R TU CUAGN 73 A1AA DE A2BB SKUnderstood. Thank you. Best regards. Signing off. (SK)A1AA:E EA couple of dits typically ends a contact. This resembles the archaic English "pip pip old chap, tally ho!"In practice, A1AA and A2BB would be conventional amateur callsigns uniquely identifying each of the parties to the contact.With heavy use of the Q code, prosigns and Morse code abbreviations, surprisingly meaningful conversations can be had with relatively short transmissions, rather like "TXT speak" on cellphones. Note that very few full English words have been used in the conversation ("is" and "name"), with most words and phrases abbreviated. A1AA and A2BB might not even speak the same native language, merely learning to translate their native tongue into the correct Morse abbreviations.Rag chewers are Morse code operators who engage in casual conservations with other operators discussing subjects such as: the weather, their equipment, and their families, etc. Of course, real rag-chewing (lengthy chats or conversations) cannot be done without a common language, a lingua Franca. On the worldwide amateur bands this is most often English but long Morse contacts can also be heard in French, German, Spanish, Russian etc. Likewise, common words in these languages have their own abbreviations, such as "MCI BCP" for "merci beaucoup", "AWDH" for "auf Wiederhören" and "DSW" for "do svidaniya". It is courteous to use such simple non-English abbreviations in contacts with non-English speakers, although there is a slight risk that they might take it as a sign that you are fluent in their language!Contesters are Morse code operators who engage in sometimes frenetic contest activity where transmissions are short and cryptic. Contesters often use an even shorter, stylized format for their contacts. Their purpose is to complete as many contacts as possible in a limited time (e.g. at a rate of 100–200 contacts per hour). They typically omit superfluous procedural signals and repeats unless the band is noisy and/or the other party seems likely to have trouble copying correctly. Accuracy is particularly important, especially for callsigns, to avoid points being deducted during the scoring process so good Morse operators regulate their style according to conditions and the other party (e.g. matching their speed).Traffic handlers are Morse code operators who send and receive—or 'handle'—recorded text messages for relay and delivery to third parties. The message information in such formal traffic handling is called 'record traffic'. In the sense meant here the words 'record' and 'recorded' means manually hand written, or typewritten, on paper or else typewritten into a word processing file so that a more or less permanent record of the message is available. Morse code record traffic handlers may be radio amateurs or professionals (ship's radio operators or military radio operators). In North America (USA and Canada) amateur radio operators ('hams') are permitted to handle such third party traffic as a non-profit public service, however such traffic handling on behalf of third parties by amateurs is forbidden by law in much of the rest of the world. The American and Canadian national ham radio organizations, the ARRL (American Radio Relay League) and the RAC (Radio Amateurs of Canada), publish manuals that standardize procedures for such record communications. Record traffic handlers (both professional and amateur) traditionally use several of these Morse code prosigns to format the text of the messages as recorded on the page (written by hand or typwritten). When record traffic handlers receive formal message traffic by Morse code they do not write or type the prosigns, instead they take page and text formating action upon receiving the prosigns to properly format the recorded message on the page. For example when hearing the prosign CT ("Copy This") the operator will begin copying down all that comes afterword, immediately expecting a message header to follow. When hearing BT ("Begin Two lines") within a message, the traffic handler starts a new paragraph on the page (spaces down two lines). When hearing the prosign AA within a message, the traffic handler spaces down one line on the page (e.g. starts a new line for each line of a street address or postal address). Upon hearing the prosign AR the operator stops writing down or recording the message text but continues listening.".
• Prosigns_for_Morse_code wikiPageID "5648649".
• Prosigns_for_Morse_code wikiPageRevisionID "604802531".
• Prosigns_for_Morse_code hasPhotoCollection Prosigns_for_Morse_code.
• Prosigns_for_Morse_code subject Category:Brevity_codes.
• Prosigns_for_Morse_code subject Category:Morse_code.
• Prosigns_for_Morse_code comment "In Morse code, prosigns or procedural signals are dot/dash sequences that do not represent text per se, but have a special meaning in a transmission: they are generally not copied down, they are a form of control character. They are used to indicate formatting of the text being copied or to indicate operational changes in transmission.".
• Prosigns_for_Morse_code label "Prosigns for Morse code".
• Prosigns_for_Morse_code sameAs m.0dy4bt.
• Prosigns_for_Morse_code sameAs Q7250609.
• Prosigns_for_Morse_code sameAs Q7250609.
• Prosigns_for_Morse_code wasDerivedFrom Prosigns_for_Morse_code?oldid=604802531.
• Prosigns_for_Morse_code isPrimaryTopicOf Prosigns_for_Morse_code.