You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by "Menaka Madushanka (JIRA)" <ji...@apache.org> on 2015/07/28 19:34:04 UTC

[jira] [Comment Edited] (TAVERNA-844) Request for an RO validator

    [ https://issues.apache.org/jira/browse/TAVERNA-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644706#comment-14644706 ] 

Menaka Madushanka edited comment on TAVERNA-844 at 7/28/15 5:33 PM:
--------------------------------------------------------------------

I finished implementing the basic part of the ro bundle validation module. 

TODO : Check the annotations

The validation report structure will be as follows.

There are mainly 3 conditions. 
    Aggregate files are not present in  the bundle
    Aggregates have external urls
    Files which are in the bundle not included as aggregates.

The report structure: 
      * If aggregates are not found: This is an Error
                     Aggregate not found error: <List of missing aggregates>
      * If external urls present: Warning
                     Warning : <url> is an external url
      * If extra files available: Warning
                     Warning (info) <file_name> 

Each of the reports can be accessed individually by calling the get methods.

If there are no errors or warnings,
           The bundle has no errors
           The bundle has no warnings
           The Bundle has no Info level warnings
will be displayed.

Please let me know if there are anything to be modified.

Menaka


was (Author: menaka):
I finished implementing the basic part of the ro bundle validation module. 

TODO : Check the annotations

The validation report structure will be as follows.
There are mainly 3 conditions. 
Aggregate files are not present in  the bundle
Aggregates have external urls
Files which are in the bundle not included as aggregates.
The report structure: 
If aggregates are not found: This is an Error
Aggregate not found error: <List of missing aggregates>
If external urls present: Warning
Warning : <url> is an external url
If extra files available: Warning
Warning (info) <file_name> 
Each of the reports can be accessed individually by calling the get methods.
If there are no errors or warnings,
The bundle has no errors
The bundle has no warnings
The Bundle has no Info level warnings
will be displayed.

Please let me know if there are anything to be modified.

Menaka

> Request for an RO validator
> ---------------------------
>
>                 Key: TAVERNA-844
>                 URL: https://issues.apache.org/jira/browse/TAVERNA-844
>             Project: Apache Taverna
>          Issue Type: New Feature
>          Components: Taverna Language
>            Reporter: martin scharm
>            Assignee: Menaka Madushanka
>            Priority: Minor
>
> I'm looking for some code to check/validate if a given container is a Research Object. Currently, the RO library just consumes like everything. If I open a non-RO container it simply deploys a fresh RO-manifest and tells me that it is an RO.
> It would be nice to have a method that checks if a certain file is an RO. E.g. this method could check if the mime type is set correctly and if there is a proper manifest. A validator could also check if the manifest is correct/up-to-date etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)