>>> 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/XML 
>>> is longer and more deeply nested, and that people could be tempted to 
>>> perform open-world extensions to existing simulations, rather than 
>>> making a copy at a new URL.
>>>     
>>   
>> do you really mean graph nodes, or do you mean cs:simulation nodes? If 
>>   
> Sorry, it should be simulation nodes at least (although perhaps 
> commenting on graphs would also be useful, for example, "graph 
> http://www.cellml.org/models/myModel/download#mygraph demonstrates that 
> (reified statement node)" could be useful metadata for knowledge 
> management systems, as could access to almost any node in the RDF 
> graph). Suggesting that anonymous nodes not be used could be one 
> approach, although it would result in harder to read metadata in the 
> hand-coded case (the model repository will mess up nicely hand-optimised 
> RDF/XML anyway, though).

yep - and I think we should look at adding something along those lines 
to specification. Even when writing papers, you could see something like 
http://www.cellml.org/models/myModel/download#mygraph being used as a 
source for a figure and then running this through a CellML preprocessor 
to generate the actual image to be displayed in the article.

I don't think we need to overly worry ourselves about maintaining human 
readability of the metadata, because as you point out most processors 
will not maintain the hand-written RDF/XML serialisation. At best, I 
think we need to start thinking about metadata editing interfaces - 
although at least for the simulation metadata pcenv is already pretty 
close, and probably not too far off for the graphing metadata?

Thanks for this discussion Andrew, its really helped me start to come to 
grips with RDF.


David.
_______________________________________________
cellml-discussion mailing list
[email protected]
http://www.cellml.org/mailman/listinfo/cellml-discussion

Reply via email to