search

OpenTransport / vocabulary

A vocabulary to describe transport systems
36 stars 9 forks source link

Naming stop_time vs StopTime #14

Closed elf-pavlik closed 9 years ago

elf-pavlik commented 10 years ago

Looking at https://github.com/OpenTransport/vocabulary/blob/master/docs/vocabulary.md I see you prefer stop_time over StopTime

AFAIK many (most?) linked data vocabularies tend to use camel casing with first letter capitalized for classes eg. StopTime and first lower for predicates eg. belongsTo

I see similar convention also used in http://vocab.org/transit/terms/.html TRANSIT vocab

Tristramg commented 10 years ago

I have no strong opinion here. I just used what we used internally, but both forms are perfectly fine for me.

elf-pavlik commented 10 years ago

two relevant articles:

The well established convention is that RDF class names begin with upper case letters, properties with lower case letters, both use camel case. Further, where an object property is used for an n-ary relationship between classes, the property is often named in exactly the same way as the class that is the range. For example, in ORG we have org:role that has range org:Role.

pietercolpaert commented 9 years ago

"stop_time" is used by GTFS CSV format, while "StopTime" would be used by RDF ontologies. I will do a proposal to relaunch the vocabularies in a mere RDF manner later today/this week in which I'd prefer StopTime as well.