Content deleted Content added
Edgardmarx (talk | contribs) No edit summary |
Citation bot (talk | contribs) Removed parameters. | Use this bot. Report bugs. | #UCB_CommandLine |
||
Line 100:
=== Construction of control dependences ===
Control dependences are essentially the [[Dominator (graph theory)|dominance frontier]] in the reverse graph of the [[control-flow graph]] (CFG).<ref>{{Cite book|publisher = ACM|date = 1989-01-01|___location = New York, NY, USA|isbn = 0897912942|pages = 25–35
The following is a pseudo-code for constructing the post-dominance frontier:
Line 128:
==Data Dependency Management==
In 2016, Edgard Marx, a computer scientist from Leipzig University, coined the term Data Dependency Management<ref>{{Cite web|title=Data Dependency Management|url=https://github.com/AKSW/KBox|access-date=2023-07-13|website=github.com
Data Dependency Management systems are designed to facilitate the deployment and management of data on the cloud, personal computers, or smart devices (edge). Data Dependency Management frameworks can be used to describe how the data was conceived, licensing as well as its dependencies. The concept of data dependency management comes from software package dependency management tools such as npm for JavaScript, [[RubyGems|gem]] for Ruby, and [[NuGet]] for .NET. Their rationale is to allow users to manage the software dependency on data, such as machine learning models for data-driven applications. They are useful to publish, locate, and install data packages. A typical example of a data dependency management frameworks are Hugging Face, KBox,<ref>{{Cite journal|title=KBox|url=https://ieeexplore.ieee.org/document/7889519|access-date=2023-07-13|website=gieeexplore.ieee.org|date=January 2017 |pages=125–132 |doi=10.1109/ICSC.2017.77 |s2cid=14980310
==References==
|