Context: The UCS-2 and UTF-16 encodings specify the Unicode Byte Order Mark (BOM) for use at the beginnings of text files, which may be used for byte ordering detection (or byte endianness detection). The BOM, code point U+FEFF has the important property of unambiguity on byte reorder, regardless of the Unicode encoding used; U+FFFE (the result of byte-swapping U+FEFF) does not equate to a legal character, and U+FEFF in other places, other than the beginning of text, conveys the zero-width non-break space (a character with no appearance and no effect other than preventing the formation of ligatures).

Question: What does BOM stand for? 
Answer: Unicode Byte Order Mark

Question: What specifies the BOM?
Answer: UCS-2 and UTF-16

Question: what is the code point of the BOM?
Answer: U+FEFF

Question: What is U+UFFE the result of? 
Answer: byte-swapping U+FEFF

Question: What is the code point for BOM?
Answer: Unanswerable

Question: What changes the important property in BOM?
Answer: Unanswerable

Question: U+FFFE is equated to what?
Answer: Unanswerable

Question: What are UCS-2 and UTF-16 specified by?
Answer: Unanswerable

Question: What is the abbreviation for UCS-2 and UTF-16?
Answer: Unanswerable