David Nickerson wrote:
>> I'm not sure we would name them so the URL needed a query portion,
>> because that would mean that browsers would save the model wrong. A
>> hierarchy (perhaps a subset of an existing ontology restricted so it
>> becomes a tree) could be used to locate the model from th
> I'm not sure we would name them so the URL needed a query portion,
> because that would mean that browsers would save the model wrong. A
> hierarchy (perhaps a subset of an existing ontology restricted so it
> becomes a tree) could be used to locate the model from the path rather
> than query
David Nickerson wrote:
>>> The only issue with this is what happens when you upload models into
>>> the repository (the relative URIs would need to remain consistent with
>>> what is in the model, or alternatively, we would need to modify the
>>> URIs).
>>>
>
> I don't think anyone has ye
>> The only issue with this is what happens when you upload models into
>> the repository (the relative URIs would need to remain consistent with
>> what is in the model, or alternatively, we would need to modify the
>> URIs).
I don't think anyone has yet come up with a solution for uploading
Andrew Miller wrote:
> David Nickerson wrote:
>> I guess thats something that we need to discuss a bit more - there
>> are probably some good reasons why we made them absolute?
> I don't think there is any requirement in the CellML specification for
> URLs on xlink:href to be absolute. PCEnv does
