Data modelling

One of the issues I think we are bound to come across is the distinction 
between data about the BPR and BPCs themselves and the data about the 
things they represent.

For example, the submission uses dcterms in what seems to be two ways.
Without wishing to get too detailed about the submission, but to use it 
as an illustration:

<http://example.org/container1>
    a bp:Container;
    dcterms:title "A Basic Profile Container of Acme Resources";

so the title is about <container1>.  But we also have:

<http://example.org/netWorth/nw1/assetContainer>
    a bp:Container;
    dcterms:title "The assets of JohnZSmith";

which suggests the title is about the assets themselves (although it is 
probably a more useful display label).

And when we have:

<http://example.org/netWorth/nw1/assetContainer/a5>
    a o:Stock;
    dcterms:title "Big Co.";
    o:value 200.02.

but assuming that is the intention of dcterms:modified being under the 
control of the system is that it records the last change:

<http://example.org/netWorth/nw1/assetContainer/a5>
    a o:Stock;
    dcterms:title "Big Co.";
    dcterms:modified  "2012-06-18T16;19:00+01:00"^^xsd:dateTime ;
    o:value 200.02 .

It's the time the entry in the container, not the stock, that is 
modified.  I may want to talk about both, separately.

On the other hand, "excessive modelling" can produce something unusable. 
  It is hard balance. Some basic guidance by example would probably be 
very helpful to developers.

 Andy

Received on Monday, 18 June 2012 15:41:31 UTC