Re: F2F5 Agenda

Dear F2F participants,
Find below our proposal for the MOF metamodel of the RIF Core. This 
proposal considers all concepts from the RIF Core Positive Language. We 
try to find good names which are proposed by using /better-name/ 
property. After the MOF/UML class diagram you'll find a proposal for a 
mapping from MOF to (E)BNF. The EBNF conforms to ISO/IEC 14977:1996 
(similar with OWL abstract syntax).


Mapping rules:

   1. Any abstract class (italic name in the diagram) translates into
      EBNF non-terminal using capitals (ex. /Condition /translates into
      CONDITION)
   2. Any concrete class translates into EBNF terminal (ex. And
      translates into 'And')
   3. Any composition is captured using round brackets as terminals
   4. As in OWL abstract syntax using curly brackets { and } denotes 0..*
   5. Right brackets [ ] are used to indicate 0..1

According with these rules we obtain the the following EBNF:

CONDITION ::= 'And' '(' {CONDITION} ')' |

              'Or' '(' {CONDITION} ')'  |

              'Exists' '(' 'declare('Var {Var}')' CONDITION ')' |

              POSITIVE

POSITIVE ::= 'Equal' '(' TERM TERM ')' | 'Uniterm' '(' 'functor' '(' Const ')' 'arguments' '(' {TERM} ')' ')'

TERM ::= Var | Const | 'Uniterm' '(' 'functor' '(' Const ')' 'arguments' '(' {TERM} ')' ')'

Var ::= 'Var' '(' name ['type' '(' SORT ')'] ')'

Const ::= 'Const' '(' id ['type' '(' SORT ')'] ')'

SORT ::= PSORT | 'ASort' '(' SORT {SORT} ')' | BSort

PSORT ::= xs:integer | xs:decimal | xs:time | xs:dateTime | xs:string

name::= NCNameRef

id ::= URIref

You may notice our proposal for using xs:NCName for local names and 
xs:anyURI for constants.
Also there is a question which arise:
Why the symbol set Const is not subclassed by (possibly overlapping) 
subclasses IndividualName, FunctionSymbol and PredicateSymbol?

Looking forward to your comments,

Adrian

Chris Welty wrote:
>
>
> We had to do a little reorganization of the agenda to deal with the 
> problems created by the weather here, and the new agenda for the f2f 
> is now on the wiki.  Of course things may change further as we uncover 
> new issues.  If someone who plans to attend the meeting remotely is 
> planning on attending for a specific session they should let us know.
>
> -CC&S
>
>