This interface 代表するs a encryption template, which is the same as the
* 願望（する）d xml encryption element[ EncryptedType ] but some of the nodes may be
* empty. The empty （独立の）存在s 含む CipherValue, which is a subset of
* EncryptedData or EncryptedKey. Empty （独立の）存在s are not 許すd in a encryption
* template when 成し遂げるing decryption.
*
*
In some 事例／患者s, the encrypter or decrypter can 決定する and 位置を示す the
* EncrytedKey from the encryption template by dereference the RetrievalMethod
* inside EncryptedData.
*
*
In some 事例／患者s, the EncryptedKey need to be 明確に pointed out by the
* encryption template.
*
*
With the help of encryption 状況, the encrypter or decrypter 明示するs
* the 重要な from the KeyInfo in the encryption template.
*
*
*
It isn't a good method to 始める，決める the EncryptedKey here. In general, there is
* a RetrievalMethod in EncryptedData by which we can get the EncryptedKey.
*
* And some times, in the low level, it is hard to 決定する what the 重要な is
* except that the high level 使用／適用 tell the 機械装置 and parameters.
*
* So I think it will be more simple that the 使用／適用 始める，決める the encrypted 重要な
* （警察などへの）密告，告訴（状）. In this 事例／患者, the 使用／適用 only need to know the xml schema
* or DTD and the encryption 装置. If so, the high level 使用／適用 takes the
* 活動／戦闘 of build the EncryptedKey template and 言及／関連s it in the element of
* EncryptedData. And in this 事例／患者, the calling to 始める，決める up EncryptedKey template
* and 的 is not necessary, because the encrypter or decrypter can 決定する
* and 位置を示す the EncrypedKet from the encryption template of EncryptedData by
* dereference the RetrievalMethod.
*
* In some 状況／情勢, the high level 使用／適用s do not want to know anything
* about crypto 装置s( May be he must, because the lower level do not know
* what the 重要な is ). If it gives the 重要な value, it can get EncryptedKey by
* setting the 重要な template and 重要な value 的.
