ࡱ> 65( / 0LDTimes New Romantt*x: 0@ .  @n?" dd@  @@`` h,    0AA3@3 ʚ;ʚ;g4tdtdIx: 0jppp@ <4dddd@ 0t`*80___PPT10 ?  %fRIF Design GoalsDERI & RuleML Perspective Michael Kifer  Stony Brook Harold Boley  NRC Jos De Bruijn  DERI Dieter Fensel - DERIPYP t#Rule Interchange & Interoperability$$(Our rule interchange/rule interoperability distinction is similar to the Design Document of the UCR editors: http://www.w3.org/2005/rules/wg/wiki/UCR/Design_Goals but we elaborate on this.Dm6m/Rule Interchange(Enable sending rules in one rule language, L1, to an engine implementing another rule language, L2, provided that the semantics of L1 is compatible with the semantics of L2 and L2 supports the same or more syntactic features. I.e., L1 is upward-compatible with L2 and L2 is downward-compatible with L1 (or L2 is an extension of L1) Example: L1 is a rule language with stratified semantics L2 is a rule language with stable model semantics and, in addition, it supports Lloyd-Topor Here L2 may have more syntactic features and may or may not be more expressive. It is not the job of RIF to support anything but straightforward translations. Design families of languages (characterized by both syntax and semantics) into which other ("vendor") languages are mapped losslessly This implies that RIF is itself a family of languages (a semi-lattice formed by feature/semantic inclusion; cf. the RuleML family)2PkPPPPP Py  v  >e u Rule InteroperabilityTo be able to exchange information between rule languages at the level of queries. Semantically compatible interoperability L1 is upward compatible with L2 so L2 can send queries to L1 provided that the queries (which are also rules) are within the capabilities of L1. Note: L1 querying L2 in a semantically preserving way may be problematic. For instance, L2 may use 3-valued semantics and L1 may use 2-valued. Semantics preserving interoperability It is possible to define narrow query channels in which semantics of query answers is well-defined. Ad hoc interoperability Take your chance (presumably the user knows what to do with the answers; metadata can be helpful here)SP*P.P'ndPngPS)'d  gOWL and RDF InteroperabilityMust enable that Probably at the level of semantics preserving and ad hoc interoperability See A Realistic Architecture for the Semantic Web in RuleML 2005: Intl. Conference on Rules and Rule Markup Languages for the Semantic Web. Galway, Ireland, November 2005. http://www.debruijn.net/publications/msa-ruleml05.pdf See DERI/RuleML  roadmap presentation tomorrow.J1.w6 ,"Targeted LanguagesNLanguages in the RIF family should cover the most interesting theoretically sound, and important features among the languages represented in RIFWG (see the  roadmap ):*8F*8F 'Scoped Inference, Metadata, Integration(((Modularization to support Integration of rule sets Scoping of inference, and Scoping of negation Import of rule sets Metadata to support interchange, provenance, etc.6HFHF,4S  SerializationXML serialization of RIF family members; analogous to RuleML RDF can be generated from RuleML facts via XSLT, XQuery, or other transformations >6  0` ̙33` ` ff3333f` 333MMM` f` f` 3>?" dd@,|?" dd@   " @ ` n?" dd@   @@``PR    @ ` ` p>> *"(    6`t P  T Click to edit Master title style! !  0Lw   RClick to edit Master text styles Second level Third level Fourth level Fifth level!     S  0~ ``  Z*   0 `   \*   0 `   \* H  0޽h ? ̙33 Default Design} 0  $(  r  S I(> ( r  S @(p`   ( H  0޽h ? ̙33___PPT10i.:@}+D=' = @B +}  0 0$(  r  S (P  ( r  S (` ( H  0޽h ? ̙33___PPT10i.:VH+D=' = @B +}  0 @$(  r  S (p  ( r  S `(0 ( H  0޽h ? ̙33___PPT10i.: h+D=' = @B +}  0 P$(  r  S $( 0  ( r  S ( ( H  0޽h ? ̙33___PPT10i.:ԉo+D=' = @B +}  0 ` $(   r  S l(P  ( r  S D( ` ( H  0޽h ? ̙33___PPT10i.(; th+D=' = @B +}  0 p$$(  $r $ S  (P  ( r $ S |( ( H $ 0޽h ? ̙33___PPT10i.(; +D=' = @B +}  0 ($(  (r ( S ,`   r ( S p-`  H ( 0޽h ? ̙33___PPT10i.);@pi+D=' = @B +}  0 ,$(  ,r , S h>(P  ( r , S @?(` ( H , 0޽h ? ̙33___PPT10i.); P+D=' = @B +r,$&)+%.0/3598 1Oh+'0  hp   $PowerPoint PresentationChristian de Sainte Maire15Microsoft PowerPoint@ZD@@0:v;G g  g  y--$xx--'@Times New Roman-. ̙2 6,RIF Design Goals."System7-@Times New Roman-. ̙2 B+DERI & .-@Times New Roman-. ̙2 BBRuleML.-@Times New Roman-. ̙2 BY PerspectiveG.-@Times New Roman-. 2 OUMichael .-@Times New Roman-. 2 OdKifere.-@Times New Roman-.  2 On.-@Times New Roman-. 2 Or Stony Brook.-@Times New Roman-. 2 TcHarold .-@Times New Roman-. 2 ToBoleyd.-@Times New Roman-.  2 T{.-@Times New Roman-.  2 T~NRC.-@Times New Roman-.  2 YaJos.-@Times New Roman-.  2 YhDe .-@Times New Roman-. 2 YnBruijn.-@Times New Roman-.  2 Yz.-@Times New Roman-.  2 Y}DERI.-@Times New Roman-. 2 _bDieter .-@Times New Roman-. 2 _nFensel.-@Times New Roman-.  2 _z-.-@Times New Roman-.  2 _}DERI.-՜.+,0    On-screen Show8A  Times New RomanDefault DesignRIF Design Goals$Rule Interchange & InteroperabilityRule InterchangeRule InteroperabilityOWL and RDF InteroperabilityTargeted Languages(Scoped Inference, Metadata, IntegrationSerialization  Fonts UsedDesign Template Slide Titles1_m80Christian de Sainte MaireChristian de Sainte Maire  !"#$&'()*+,./012347Root EntrydO)Current User-SummaryInformation(PowerPoint Document(8DocumentSummaryInformation8%