cross-referencing constraints in conceptual model and formal model

('binary' encoding is not supported, stored as-is)
Hi,

I am missing the first 30-40 minutes of the teleconference (supervising an exam), but might be able to join later.

I had an action item to add cross-references between the conceptual model and formal model.

I have added <a name="PIL:XXXX"> tags and cross-reference links to:

http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html

and

http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html

I haven't tagged all of the things that seem like they should be tagged (my list of constraints is a week or two out of date).

Basically, the idea is that wherever we have a formal-sounding constraint or inference in the conceptual model, we should have links to/from the corresponding part of the formal model (or semantics, if there are constraints we can't or don't want to specify using OWL).

Right now these are maintained by hand, which could be painful over time.  We may want to add some automation to make it easier to keep these consistent.

If there is time I would appreciate if people could have a look at what I did and indicate whether it seems reasonable (or if there is a known better way to do this kind of thing).

If this looks OK, then going forward we should be careful to keep these consistent.

--James
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Received on Thursday, 18 August 2011 15:11:27 UTC