Loading source files for package notio... Loading source files for package notio.translators... Loading source files for package notio.test... Constructing Javadoc information... /home/finnegan/code/src/notio/translators/LFParser.java:6: Class com.metamata.parse.ParseException not found in import. import com.metamata.parse.ParseException; ^ /home/finnegan/code/src/notio/translators/CGIFParserImpl.java:7: Package com.metamata.parse not found in import. import com.metamata.parse.*; ^ /home/finnegan/code/src/notio/translators/CGIFParserImpl.java:241: Superclass com.metamata.parse.Scanner of inner class notio.translators.CGIFParserImpl. __jjScanner not found. public class __jjScanner extends com.metamata.parse.Scanner { ^ /home/finnegan/code/src/notio/translators/CGIFParserImpl.java:311: Superclass com.metamata.parse.ScanError of inner class notio.translators.CGIFParserImpl. __jjScanner.TokenMgrError not found. class TokenMgrError extends com.metamata.parse.ScanError ^ /home/finnegan/code/src/notio/translators/CGIFParser.java:6: Class com.metamata.parse.ParseException not found in import. import com.metamata.parse.ParseException; ^ List of @bug Tags

List of @bug Tags

Package Index


Package notio

Class notio.Marker

Method Comments

Class notio.TypeHierarchy

Method Comments

Class notio.RelationTypeHierarchy

Method Comments

Class notio.Designator

Class Comments

  1. Must rework all matching-related comments.

Method Comments

Class notio.DefinedDesignator

Class Comments

  1. This class does nothing. What are these things for anyway?

Class notio.Node

Class Comments

  1. Should this be in the API or not?

Class notio.Concept

Method Comments

Class notio.Generator

Class Comments

  1. What methods should generators be forced to implement.

Class notio.NodeMappingGenerator

Class Comments

  1. Needs to be upated to support actors and nested matches.
  2. Currently assumes that mappings of different node types can not affect each other. This may not be true if coreferent matching is used on compound graphs.
  3. Folding probably requires that folded nodes match. The current method is that they just have to match the same node in another graph but they should match each other too, I think. This is not necessarily true, unless one can reduce the folded nodes to entities which are not the same. For example: Mapping both [Canine] and [Female] to [Bitch] is quite legal. However, [Canine#12] and [Female#44] should probably not be allowed.
  4. Need to test folding.
  5. Need to add common subgraph stuff.
  6. Need to fix proper subgraph implementation and restrictions.
  7. Some types of relation matching might preclude the need for mapping related concepts. Unrelated concepts (unconnected) will have to be mapped, of course.
  8. Arc-concept matching is very useful for the match routine in Relation but rather poor for this level. Is there a way to reconcile the two without overly complicating life?

Constructor Comments

Method Comments

Class notio.Graph

Class Comments

  1. Must add default class-wide setting for allowIncompleteRelations.

Method Comments

Class notio.Relation

Class Comments

  1. Need to rework some actor-related comments.
  2. restrictTo() and copy() can only return a Relation, not an Actor. Perhaps it can check the class to make sure that the correct class is used for the copy.
  3. Do we really want package visibility for member vars?
  4. Really need to rethink this whole input/output argument approach.

Constructor Comments

Method Comments

Class notio.Actor

Constructor Comments

Class notio.MatchResult

Class Comments

  1. The semantics of whether an operation can return a mapping or not need to be tightened a trifle. Is there any point to allowing empty mappings?

Class notio.RelationType

Constructor Comments

Method Comments

Class notio.Extensions

Class Comments

  1. What about activating different features for separate, concurrently running databases? Allow specific extensions instances?

Method Comments

Class notio.MatchingScheme

Class Comments

  1. Coreference matching should be better structured. Currently automatch means that two concepts will automatically match if they are coreferent. Coref agreement mean that when matching two concepts, all of their coreferent concepts must match as well. Should also be usable to test that two graphs possess identical coreference structure. Perhaps the current meaning should be a set of CN_ flags or a new set of REFERENT flags should be added. Then the COREF_ flag could take a meaning similar to the ARC_ flag (i.e a requirement for identical structure).
  2. ARC flags and CONN flags may conflict in some ways.
  3. Instance matching is too implementation specific. It is based on the assumption that two calls to Graph.getConcepts(), etc. will result in the same set of objects. This need not be the case. We should probably override the .equals() method in various classes to detect whether two different objects in fact represent the same node within a given graph (compare graphs and place in graph, if no graph, use Object.equals()).

Class notio.MarkerSet

Method Comments

Class notio.CoreferenceSet

Method Comments

Class notio.ConceptType

Constructor Comments

Method Comments

Class notio.ParserException

Method Comments

Class notio.Referent

Method Comments

Class notio.Parser

Class Comments

  1. What methods should parsers be forced to implement?

Class notio.NameDesignator

Class Comments

  1. This class is really superfluous unless we want special treatment for names which should really just be relations.

Package notio.translators

Class notio.translators.SimpleGenerator

Class Comments

  1. Escape sequences need work.

Method Comments

Class notio.translators.LFGenerator

Class Comments

  1. Doesn't handle 0-adic relations/actors.
  2. Doesn't actually generate Actors.

Method Comments

Class notio.translators.DefiningLabelTable

Method Comments

Class notio.translators.LFParser

Class Comments

  1. Currently catching ScannerError since token coverage is incomplete.
  2. Need to rework comments.

Class notio.translators.CGIFParserImpl

Class Comments

  1. Token coverage is probably inadequate. We sometimes throw TokenMgrError.
  2. ParserExceptions are still poor at providing locations. Need access to scanner's state information.
  3. Graph termination problem remains. Can use at the end but doesn't work for nested graphs. Should probably use to terminate Wrapper().
  4. Lots of ugly stuff in this class relates to outdated coreference scope checking.
  5. Ok: Need to pass several components down so we can connect them together when we know they will really be used.
  6. What about the state of the defining label table after a ParserException? Currently, the state should be assumed to be bad, so a new table or translation context should be used in the future. Should we try to handle this elegantly? Perhaps in CGIFParser.java?

Method Comments

Class notio.translators.CGIFGenerator

Class Comments

  1. Should add 'useNegationAbbreviation' flag to generator.

Method Comments

Class notio.translators.CGIFParser

Class Comments

  1. Currently catching ScannerError since token coverage is incomplete.

Class notio.translators.LFParserImpl

Method Comments


Package notio.test

Class notio.test.TestSimplify

Class Comments

  1. This test is implementation specific since it relies on knowing which of the redundant relations will be left after simplification and on the same instance being returned by getRelations() every time it is called.

Class notio.test.TestSerialization

Class Comments

  1. Should add more structures to ensure adequate coverage.

Class notio.test.TestTypeHierarchies

Class Comments

  1. Need to add test cases for different constructors/uses of RelationTypeDefinition.

8 warnings