pm#process_supporting_the_non-repudiation_of_information_sent_or_received_by_some_RFID_related_entity_or_process
  exclusion:  pm#process_supporting_authentication_in_some_RFID_related_entity_or_process  pm#process_supporting_the_access_control_of_some_RFID_related_entity_or_process  pm#process_supporting_the_integrity_of_information_in/from_some_RFID_related_entity_or_process  pm#process_supporting_the_confidentiality_of_communication_with_some_RFID_related_entity_or_process  pm#process_supporting_the_privacy_of_information_in_some_RFID_related_entity_or_process  pm#process_supporting_the_availability_of_some_RFID_related_entity_or_process  pm#process_supporting_interoperability_from/to_some_RFID_related_entity_or_process
  supertype:  pm#process_supporting_some_security_attribute_in_some_RFID_related_entity_or_process
  subtype:  bridge#process_supporting_the_non-repudiation_of_information_sent_by_some_RFID_tag__id_req_tag_5  A reader that includes signature functionality must request that a tag signs information sent to it. With the signature, a reader can prove that a specific tag has communicated with it.
  subtype:  bridge#process_supporting_the_non-repudiation_of_information_in_some_RFID_related_network__id_req_net_5  Data contributions to the system must be signed in order that individual parties can me held accountable for the quality of the data they provide. There must be accountability for data validity (N19)
  subtype:  bridge#process_supporting_the_non-repudiation_of_information_sent_or_received_by_some_RFID_related_application__id_req_app_5  The parties which update DS records must be accountable for this fact. Likewise, the responsibility which the parties own in order not to refuse having receive queries at any time.

No statement uses or specializes pm#process_supporting_the_non-repudiation_of_information_sent_or_received_by_some_RFID_related_entity_or_process; click here to add one.