1 / 4

What is the declarative (logic) approach?

What is the declarative (logic) approach?. Use of declarative database and knowledge representation formalisms for... adding knowledge packages to AIPs: capture context known at the time of archival using conceptual models of collections, integrity constraints, virtual relations, …

crete
Download Presentation

What is the declarative (logic) approach?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. What is the declarative (logic) approach? • Use of declarative database and knowledge representation formalisms for... • adding knowledge packages to AIPs: • capture context known at the time of archival using conceptual models of collections, integrity constraints, virtual relations, … • applying them at ingestion (aka: bringing-in), migration, and instantiation/access time (= wrapping, transforming, querying collections)

  2. It’s wrapping time again... • reassembling document structure (lexical scopes) from the OAV (or rather AOV) model: attr_interval(Attr, SID, Attr_val, LN, LN1) :- oav(Attr, (SID, LN), Attr_val), oav(Attr, (SID, LN1), _), LN1 > LN, not attr_between(Attr,SID,LN,LN1). attr_between(Attr,SID,LN,LN1) :- oav(Attr, (SID, LN), _), oav(Attr, (SID, LN1), _), oav(Attr, (SID, LN2), _), LN < LN2, LN2 < LN1.

  3. Caught in the accessioning loop... • Data provider says: “please archive all records of legislative activities of the 106th senate” • Integrity constraint!? • {senators} = {sponsors} = {co-sponsors} ? • Let’s check the incoming collection: • ic1_violation1(X) <== sponsor(X), not senator(X). • ….

  4. Make Knowledge Executable • specify archival relationships, procedures, functions (cf. Reagan’s classification of relationships), business rules, etc. • formalize them in logic! => executable specifications • logic programming paradigm: logic can be executed, i.e., run!

More Related