Use htsworkflow ontology to validate various RDF using components.
authorDiane Trout <diane@caltech.edu>
Wed, 19 Sep 2012 23:10:57 +0000 (16:10 -0700)
committerDiane Trout <diane@caltech.edu>
Wed, 19 Sep 2012 23:10:57 +0000 (16:10 -0700)
commitc99feb78c58da43cb018dc3ef109bc3074d3c511
tree8579128f1dca2bb6053e1b799773a19279fff9ae
parentda57ac1c65ff0fa96c831ff6adb787c64e99cc8d
Use htsworkflow ontology to validate various RDF using components.
Of course to use the ontology I had to make one first.
Unsurprisingly implementing it touched a bunch of code & templates.

I tried to be more consisten with using mixed-case names for
classes and lower_case names for properties.

There's some inconsistencies. like i use the term notes & comments
in different areas. Also, should I be using my own terms or
do better at reusing more standard ontologies?
12 files changed:
encode_submission/test_encode_find.py
htsworkflow/frontend/experiments/tests.py
htsworkflow/frontend/templates/experiments/flowcell_detail.html
htsworkflow/frontend/templates/experiments/flowcell_header.html
htsworkflow/frontend/templates/experiments/flowcell_lane_detail.html
htsworkflow/frontend/templates/sample_header.html
htsworkflow/frontend/templates/samples/library_detail.html
htsworkflow/pipelines/sequences.py
htsworkflow/pipelines/test/test_sequences.py
htsworkflow/submission/condorfastq.py
htsworkflow/submission/test/test_condorfastq.py
htsworkflow/util/schemas/htsworkflow.turtle [new file with mode: 0644]