ni-/ni-dm — pull request #37 by nicholsn (2014-04-05 16:03:36+00:00)
Title: Capitalize class names in prov namspace

Caught these two capitalization issues while validating the RDF conversion from PROV-N.

1. `prov:collection` should be `prov:Collection`: http://www.w3.org/TR/prov-dm/#component6
2. `prov:location` should be `prov:Location`: http://www.w3.org/TR/prov-o/#Location

Note: While `prov:location` is a valid term in PROV-DM, the context in which it is used on lines [274](https://github.com/nicholsn/ni-dm/compare#diff-ea33497cc431cdd97b9858c9608fe263L274), [291](https://github.com/nicholsn/ni-dm/compare#diff-ea33497cc431cdd97b9858c9608fe263L291), etc. is as the `prov:type` of a `prov:Entity`, not as the relation that the lowercase version refers to (i.e., `prov:location`).

When the file is converted into RDF, all `prov:type` are interpreted as `rdf:type` and correspond to classes, not relations. PROV Classes follow the convention as being CamelCase with the first letter capitalized, thus any class names listed as `prov:type` should start with a capital letter (unless coming from a vocabulary following a different convention). In this way, URIs can be considered case-sensitive in order dereference correctly when multiple terms exist with the same spelling in the same namespace..

The relation `prov:location`, when converted into RDF, becomes `prov:atLocation`.

Further,`prov:Location' being used as the `prov:type` of an entity has an implication in the RDF world. For example, in RDF the `niiri:coordinate_0001` on line [273](https://github.com/nicholsn/ni-dm/compare#diff-ea33497cc431cdd97b9858c9608fe263L273) is a `prov:Entity`, `prov:Location`, and `nidm:coordinate`; however, `prov:Entity` and `prov:Location` are not related in the PROV Ontology. To correctly map `nidm:coordinate` we define it as a subclass of both a `prov:Entity` and `prov:Location`, meaning that a `nidm:coordinate` is a `prov:entity` with some spatial aspect to it, which makes sense...