Menu

#2 ability to post-validate ATLASElements againt MAIAScheme

As_Soon_As_Possible
open
8
2012-09-14
2003-02-07
No

We would like the ability to post-validate ATLASElements against a given MAIAScheme.

Our main reason for this request is to allow us to create Elements (Annotations) whose required fields are
not fully specified initially, and fill them in as the information becomes available. It would be useful to be
able to check that we have filled in everything we need.

An alternate use for this facility might be to transfer/copy elements between corpuses (corpi?) that use
similar but non-identical MAIASchemes -- we could check that the element satisfies the new corpus'
scheme before attempting to transfer it.

Discussion

  • Christophe Laprun

    Logged In: YES
    user_id=27100

    ATLAS currently doesn't support post-validation (validation
    of an element after its creation) for the simple reason that
    it is not possible (at least, it is made fairly difficult if
    not impossible) to create ATLAS element in such a way that
    they would be invalid. Moreover, no modification of an ATLAS
    element is allowed that would render it invalid.

    This choice was made in order to facilitate validation
    operations since they are then done incrementally for each
    elements. Moreover, it also allows developers not to have to
    worry about validation aspects.

    However, we are evaluating the need/interest of being able
    to post-validate elements either in conjunction with or
    replacement of (where all validation aspects will be left up
    to developers) incremental validation. Thanks for the feedback.

     
  • Robyn Kozierok

    Robyn Kozierok - 2003-03-28

    Logged In: YES
    user_id=671742

    It turns out that the ability to create, save and load "incomplete" Annotations (or other elements) is
    going to be very important to us.

    Right now we are using createPrimal etc. (against Christophe's advice) to be able to create "incomplete"
    Annotations, and are just making sure to complete them before trying to save them out. But we really need to be
    able to save them out in an incomplete state as well in some cases.

    We also need the ability to set the value of any required subordinate to null and still be able to save out that
    element, and of course to load in such incomplete corpi.

    Making this happen using separate methods to make it obvious that we know we are breaking the corpus is fine,
    and would make it easier to maintain the "must always be valid" rule for those who prefer it. So perhaps we need
    the addition of methods like saveIncompleteAsAIF etc..... and possibly a method that sets a required subordinate
    to null rather than just allowing one to directly set it to null.

    We don't need the ability to create other types of invalid elements (such as using the wrong type of element as a
    subordinate) but we definitely need to be able to work with incomplete elements, and this is becoming a high
    priority for us.

    We would also like a method to determine whether or not a given element is "complete" according to the MAIA.

    The reason for this is a strong preference voiced by our users to be able to temporarily create an
    Annotation with only partial information filled in. They want the interface to make it clear that there is
    information they need to add, but they want to be able to save out their file in that condition if necessary
    (their ride's leaving, etc....) They are clear that they want the software to facilitate them creating a
    corpus that is valid and in accordance with the task requirements, but they don't want the software to
    force them to keep the corpus in a valid state 100% of the time. Sometimes when making changes
    especially, they find it most efficient to put the corpus into an invalid state temporarily, and then fix
    things as needed. Forcing the corpus to remain valid at all times forces an awkward workflow.

    This is becoming very important in our current project, so if there's any chance you can make consideration of this
    issue a high priority there, that would be great.

    Thanks,
    --Robyn

     

Log in to post a comment.