>>> I wouldn't be opposed, however, to adding a style guideline recommending
>>> that graph nodes be given an explicit URL (we actually say that they
>>> would normally be an anonymous node at the moment), so they can be
>>> referenced. The only disadvantages of this is that the resulting RDF/XM
David Nickerson wrote:
>
>> Therefore, you have to be aware of the relationship between RDF/XML and
>> the RDF data model, and make sure you put your rdf:ID in the right place
>> (as with any other attribute in RDF).
>>
>
> ok - I think something just dropped into place. So in this case what
Andrew Miller wrote:
> David Nickerson wrote:
>> Thanks Andrew, cleared a few things up. So now for some more
>> ideas/questions...
>>
>> When defining a graph outside the scope of a single model or when
>> combining results from multiple model's, does it still make sense to use
>> the about="mo
David Nickerson wrote:
> Thanks Andrew, cleared a few things up. So now for some more
> ideas/questions...
>
> When defining a graph outside the scope of a single model or when
> combining results from multiple model's, does it still make sense to use
> the about="modelid" ?
>
> I have been look
Thanks Andrew, cleared a few things up. So now for some more
ideas/questions...
When defining a graph outside the scope of a single model or when
combining results from multiple model's, does it still make sense to use
the about="modelid" ?
I have been looking at how to define my graph externa
David Nickerson wrote:
> Hi all,
>
> I have just been looking through the graphing metadata specification
> (http://www.cellml.org/specifications/metadata/graphs) and have a couple
> of questions (pretty much due to my continuing RDF ignorance). This
> specification seems to have dropped behind
Hi all,
I have just been looking through the graphing metadata specification
(http://www.cellml.org/specifications/metadata/graphs) and have a couple
of questions (pretty much due to my continuing RDF ignorance). This
specification seems to have dropped behind the simulation specification
a bi
