Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Stored, sent and received data assets are always processed #18

Closed
wants to merge 2 commits into from
Closed

Stored, sent and received data assets are always processed #18

wants to merge 2 commits into from

Commits on Jun 29, 2021

  1. Data assets stored, sent or received are processed 

    Data assets of a technical asset that are stored by that technical asset
or are sent to or received by that technical asset via a communication
link are also always implicitly processed by that technical asset.

- Always add stored, sent and received data assets to processed assets.
- Remove code no longer necessay due to the above change.
- Ensure uniqueness of `DataAssetsProcessed`, `DataAssetsStored`,
  `DataAssetsSent` and `DataAssetsReceived`.
- Do not require presence of `data_assets_processed`,
  `data_assets_stored`, `data_assets_sent` or `data_assets_received`.
- Fix wording in rules because stored data assets are already processed.
    @aceg1k
    aceg1k committed Jun 29, 2021
    Configuration menu
    Copy the full SHA
    01932af View commit details
    Browse the repository at this point in the history

  2. Data assets are processed by communication targets 

    Data assets sent to or received by a technical asset as the target of a
communication link are also always implicitly processed by that target.

- Data assets sent to or received by a target through a communication
  link are always added to that targets' processed data assets.
    @aceg1k
    aceg1k committed Jun 29, 2021
    Configuration menu
    Copy the full SHA
    29abff2 View commit details
    Browse the repository at this point in the history