Hi,
I read through the Behavioral Metadata Proposal,
and I am not sure about a detailed issue related to Post/Preconditions.
When we specify a type X which has a feature whose range is
FeatureStructure of another type Y,
then type Y (and other referred types recursively) will automatically be
included,
or we should specify every type explicitly?
I hope both is possible by some flags in the descriptor.
Excuse me if I missed descriptions about it in the document.
Thanks,
-Yoshinobu
--
Yoshinobu KANO
Tsujii Laboratory, the University of Tokyo
Adam Lally wrote:
>
> Everyone,
>
> Six new web ballots have been posted on the OASIS UIMA TC webiste.
> Please register your votes. A summary of the issues is listed below.
> If all the votes pass then I think we're done with the Behavioral
> Metadata for now.
>
> Thanks,
> -Adam
>
>
> All refer to the attached document BehavioralMetadataProposal_v4.
>
> *1. **Type-Level XML structure. *Accept Section 4.1 "Type Names" of the
> Behavioral Metadata Proposal, which proposes the XML syntax for
> declaring Behavioral Metadata at the type level (e.g. inputs types X and
> Y and creates type Z).
>
> *2. Constraint-Level XML structure. * Accept OCL as the constraing
> language for UIMA Behavioral Metadata, and accept Section 4.2 "OCL
> Expressions" of the Behavioral Metadata Proposal, which proposes the XML
> syntax for specifying OCL expressions as part of the Behavioral Metadata
> XML.
>
> *3. View XML structure*. Accept section 4.3 "Views" of the Behavioral
> Metadata Proposal, which proposes the XML syntax for declaring
> Behavioral Metadata for analytics that operate on views. Note this vote
> includes the following that have been added to the Proposal since the
> last telecon:
> a. Analytics can specify /optional/ input views as well as
> /required/ input views.
> b. Analytics may use OCL expressions to specify the views that
> they operate on, for cases where referring only to the Sofa Type of the
> View is insufficient.
>
> *4. Including Features for "Modifies". *Accept section 4.4 "Specifying
> Which Features are Modified" of the Behavioral Metadata Proposal, which
> proposes the XML syntax for declaring the names of the features that an
> analytic may modify.
>
> *5. Precondition, Postcondition, Projection Condition XML Structure.
> *Accept section 4.5 "Specifying Preconditions, Postconditions, and
> Projection Conditions" of the Behavioral Metadata Proposal, which
> proposes the XML syntax for directly declaring preconditions,
> postconditions, and projecton conditions in Behavioral Metadata.
>
> *6. Defer Open Issues to a later date. *Resolve to defer the open
> issues in Section 7 of the Behavioral Metadata Proposal until after we
> produce a preliminary specification draft.
>
>
> _____________________________
> Adam Lally
> Senior Software Engineer
> UIMA Framework Lead Developer
> IBM T.J. Watson Research Center
> Hawthorne, NY, 10532
> Tel: 914-784-7706, T/L: 863-7706
>
