Mazda R27 1
•Télécharger en tant que PPT, PDF•
0 j'aime•254 vues
Experience Mazda Zoom Zoom Lifestyle and Culture by Visiting and joining the Official Mazda Community at http://www.MazdaCommunity.org for additional insight into the Zoom Zoom Lifestyle and special offers for Mazda Community Members. If you live in Arizona, check out CardinaleWay Mazda's eCommerce website at http://www.Cardinale-Way-Mazda.com
Recommandé
Contenu connexe
Similaire à Mazda R27 1
Similaire à Mazda R27 1 (20)
Plus de CardinaleWay Mazda
Plus de CardinaleWay Mazda (20)
Dernier
Dernier (20)
Mazda R27 1
- 1. Uncertainty Lineage Data Bases Very Large Data Bases 1975 2006
- 2. ULDBs: Databases with Uncertainty and Lineage Omar Benjelloun, Anish Das Sarma , Alon Halevy, Jennifer Widom Stanford InfoLab DATA UNCERTAINTY LINEAGE
- 17. Model (so far) Not Closed Suspects = π person (Saw ⋈ Drives) ? ? ? Does not correctly capture possible instances in the result CANNOT (Cathy, Honda) ∥ (Cathy, Mazda) Saw (witness,car) (Billy, Honda) ∥ (Frank, Honda) (Hank, Honda) (Jimmy, Toyota) ∥ (Jimmy, Mazda) Drives (person,car) Jimmy Billy ∥ Frank Hank Suspects
- 19. Example with Lineage ? ? ? Suspects = π person (Saw ⋈ Drives) λ (31) = (11,2),(21,2) λ (32,1) = (11,1),(22,1); λ (32,2) = (11,1),(22,2) λ (33) = (11,1), 23 11 ID (Cathy, Honda) ∥ (Cathy, Mazda) Saw (witness,car) 23 22 21 ID (Billy, Honda) ∥ (Frank, Honda) (Hank, Honda) (Jimmy, Toyota) ∥ (Jimmy, Mazda) Drives (person,car) 33 32 31 ID Jimmy Billy ∥ Frank Hank Suspects Correctly captures possible instances in the result
- 28. ULDB Properties and Operations Data-minimal Lineage-minimal Lineage-minimal Data-minimal Data-minimize Queries Lineage-minimize Membership Extraction
- 37. but don’t forget the lineage… Thank You Search “stanford trio” (or, http://i.stanford.edu/trio) DATA UNCERTAINTY LINEAGE
Notes de l'éditeur
- Say that work done in the context of the Trio project at Stanford
- Mention “at this point in time”, no conventional DBMS supports uncertainty or lineage, much less the two together.
- Mention that people can find more discussion of applications in original vision paper for the project
- Say what lineage is (briefly) Explain some motivating applications
- Say that you are going to substantiate the claim. Emphasize on the following slide “here are the specific technical substantiations I am going to give”.
- Make sure to say I’ll substantiate each statement technically.
- Mention that ULDB forms the basis of the Trio Project
- Say that Saw and Drives could be uncertain, and suspects could be uncertain and has lineage.
- Say that an instance is a certain database.
- Emphasize again that ULDBs are our model and basis of the Trio project. Emphasize that these are simple constructs.
- Or-sets: We can abbreviate but it is more general the way it is.
- Mention independence
- Default probabilistic interpretation, that confidences add up to <=1, and if <1, there’s implicit “?”. Then say that will talk in little more depth about confidences toward the end of the talk.
- Say it correctly!
- Mention verbally that talk is about internal lineage only.
- Mention that have added IDs to the data. I went too slow. Our semantics, once we have lineage, doesn’t allow in-consistent instances.
- Important to explain: keep base data with query results (emphasize a bit more) IMPORTANT-------- SAY CERTAIN CLASS OF QUERIES!!!!!!! INTUITIVELY WHAT KINDA CLASS -------------------
- Model can allow lineage all over the place. In reality there is a certain structure to lineage (which makes other properties nice). We define a more restricted kind of linegae in the normal case. Let me give an intuition of that. Say that we work with well-behaved ULDBs.
- Mention verbally why we care about minimality. Say less about minimality: Just say the paper as some results and also poses one open problem.
- Mention the example is very simple.
- You'll want to use it to recap what you've already said and what properties are retained by what operations, plus to introduce two additional operations you're going to discuss.
- Mention very early that Extraction is trivial in a conventional database by just removing relations, but poses interesting problem in ULDBs because of dependence of relations on other relations in lineage. In other words, possible instance of R may be determined by the possible instances in T and V, as saw in our original join example that demonstrated closure.
- “Let me just say a little more about the interesting topic about confidences…”. No need to read confidence values loud. Can motivate “custom” confidences by saying something like base data might be correlation (e.g., sensors) and u need things outside DB to compute conf.
- Mention more details in the paper.
- Mention that all the algorithms are closely related. (The extraneous data removal and membership are also confidence questions.)
- Say, “now let’s look at current work in the Trio project as a whole” To conclude let me give you the big picture of the project... Mention that this paper+talk is mainly about the data model After ULDBs: add “(coming…. correlations, continuous…)
- Say here’s a small sample, and there’s more in DB and AI, see the paper.