Closed kerimoyle closed 4 years ago
@nickerso ?
I'll have a crack at this again:
https://cellml.org/specifications/cellml_2.0/cellml_2_0_normative_specification.pdf
I guess I must have missed it, but do we really want to use a .
for the cellml_2.0
bit and an _
for the PDF filename? I know that I was in favour of the underscore for the PDF filename, but seeing it in context, it looks a bit odd since we want/need to use .
for the cellml_2.0
bit (to be consistent with previous versions of CellML). Argh, I am in two minds about this now.
Warning, warning, CellML Specification overload!
I think it's better to avoid using .
in URLs in general, so would rather have:
https://cellml.org/specification/cellml_2_0/cellml_2_0_normative_specification.pdf
It's a bit ugly though :|
The problem is that we already have https://cellml.org/specifications/cellml_1.0 and https://cellml.org/specification/cellml_1.1, so to have https://cellml.org/specification/cellml_2_0 would look really odd.
Actually, we have https://www.cellml.org/specifications/cellml_1.0 and https://www.cellml.org/specifications/cellml_1.1 (note the "www"!), which work fine but not https://cellml.org/specifications/cellml_1.0 and https://cellml.org/specification/cellml_1.1. IOW, there is no redirect to the www
... Something for @nickerso or @metatoaster?
Oops, it's actually https://cellml.org/specifications/cellml_1.0 and https://cellml.org/specifications/cellml_1.1, and it should be https://cellml.org/specifications/cellml_2.0. IOW, "specifications", not "specification"!
... when we know what it is ...