W3C home > Mailing lists > Public > public-prov-wg@w3.org > January 2012

Re: prov-dm - when are constructs too domain specific?

From: Graham Klyne <GK@ninebynine.org>
Date: Tue, 03 Jan 2012 13:57:31 +0000
Message-ID: <4F03094B.9090900@ninebynine.org>
To: Paul Groth <p.t.groth@vu.nl>
CC: Satya Sahoo <satya.sahoo@case.edu>, "public-prov-wg@w3.org" <public-prov-wg@w3.org>
Late response - catching up on emails...

I agree with you that the key criteria for domain specific structures should be 
based on interchange/interoperability.

Where I would maybe differ is that to have constructs that are too specific may 
impair interoperability as much as not having sufficiently specific constructs, 
by virtue of (a) being harder to understand, and (b) potentially over-specifying 
a particular case hence reducing scope of applicability.

As a rule of thumb, I would suggest that specific concepts that are common 
across most anticipated domains of use (e.g. people, organizations, software) 
are probably appropriate to include, but others (e.g. biological agents were 
mentioned previously) are not.  The framework should make it easy for 
applications to specialize concepts without masking any information that would 
be recognizable using common constructs.  (What constitutes "easy" here is a 
matter for debate - e.g. subclassing and assumption of associated inference 
capabilities is such a debatable point.)


On 07/12/2011 10:25, Paul Groth wrote:
> Hi Satya, All:
> I noticed that many of the issues Satya raised (see below) talked about terms
> being domain specific. For example, collections and the typing of agent.
> I think we as a group need to figure out where we stand on constructs that can
> be considered domain specific. I would like to just get your general thoughts on
> this as I think getting a broad agreement on where we roughly draw the line on
> too much domain specificity will help us resolve these issues.
> Personally, I'm in favor of being more liberal here in terms of including
> constructs. Primarily because our purpose is interchange and having some what
> can be considered domain specific constructs will greatly help in facilitating
> provenance interchange. This is especially the case for common cases.
> Anyway, I'm interested to hear your thoughts.
> Thanks,
> Paul
> Issues to do with Domain Specificity
Received on Tuesday, 3 January 2012 14:32:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:51:05 UTC