Open allynt opened 7 years ago
In the second case, what else, for example, could the URL end with: "www.mydomain.com/edit/seaice_1.6.0/?????"
@davidhassell - It would be:
"www.mydomain.com/edit/seaice_1.6.0/seaice"
This follows the convention <domain>/<thing-you-want-to-do>/<ontology>/<document-name>
as opposed to the current convention <domain>/<thing-you-want-to-do>/<ontology>/<document-type>
. I admit it looks weird because "seaice" is both the name of the document and the ontology (specialization).
Anyway, this is low priority and I am not going to make a decision yet. I was just concerned that in the long term there may be specializations which define more than one realm; I would need a way to distinguish those.
Currently views for editing & customizing documents use URLs like "www.mydomain.com/edit/seaice_1.6.0/realm". However, what happens if a specialization defines multiple realms (or models, or whatever)? It might make more sense to use URLs like "www.mydomain.com/edit/seaice_1.6.0/seaice" instead.