W3C home > Mailing lists > Public > public-prov-wg@w3.org > December 2011

prov-dm - when are constructs too domain specific?

From: Paul Groth <p.t.groth@vu.nl>
Date: Wed, 07 Dec 2011 11:25:08 +0100
Message-ID: <4EDF3F04.9050400@vu.nl>
To: Satya Sahoo <satya.sahoo@case.edu>
CC: "public-prov-wg@w3.org" <public-prov-wg@w3.org>
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 

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.


Issues to do with Domain Specificity
Received on Wednesday, 7 December 2011 10:28:41 UTC

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