Menaka, do you think this could be in scope within your command line tool "Additional features", or are we running short on time..? I guess it could work similar to your workflow validator?
I don't think the RO Bundle code has any obvious validators now, but we have a spec which has MUST/SHOULD/COULD: https://w3id.org/bundle which could translate to ERROR/WARN/INFO or something. Could be something like BundleValidation val = Bundles.validate(Path p) or something simpler? On 13 July 2015 at 14:10, martin scharm (JIRA) <j...@apache.org> wrote: > martin scharm created TAVERNA-844: > ------------------------------------- > > Summary: Request for an RO validator > Key: TAVERNA-844 > URL: https://issues.apache.org/jira/browse/TAVERNA-844 > Project: Apache Taverna > Issue Type: New Feature > Reporter: martin scharm > Assignee: Stian Soiland-Reyes > 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) -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/0000-0001-9842-9718
