Re: [Treebase-devel] [PhyloWS] query predicate vocabulary

[William P. <wil...@ya...>]

On Oct 4, 2010, at 6:24 AM, Rutger Vos wrote:

>> 1) The pattern for constructing the label uses a dot to delimit "words"
>> (e.g., identifier.tree), whereas normally the pattern I've seen uses
>> CamelCase (which would yield treeIdentifier). For the standard vocabulary
>> I'd rather stick with common conventions, so what were the reasons or
>> examples that motivated the dot pattern?
> 
> No reason. If CamelCase is the convention, we should stick with that.
> I simply did not know that.

Speaking of case... I notice that in this recent Am Nat article:

http://dx.doi.org/10.1086/656486

... the PDF has the TreeBASE URI displayed at the top of the page:

http://www.journals.uchicago.edu/doi/pdf/10.1086/656486

... which is nice, but while the URI is correctly written:  

http://purl.org/phylo/treebase/phylows/study/TB2:S10645

... the clickable link actually returns this string in lower case:  

http://purl.org/phylo/treebase/phylows/study/tb2:s10645

... which causes a "HTTP Status 400 - Bad ID string" error. i.e., our phylows implementation is case sensitive when it comes to identifiers. 

So I was wondering... is case sensitivity (e.g. the CamelCase discussed) an expectation for Linked Data identifiers and URIs? Or should TreeBASE be modified to accept both S10645 and s10645?

bp