I disagree.
In my opinion it is subjective to use "import" when some unspecified
functions are applied to the data that is being incorporated in a new
dataset, but "derived" other times. I think there is no objective
discriminator that could distinguish between clever and non-clever
functions.
That is a nice use-case.
If you make a new file by selecting out a column from a single source file,
that is a narrow case of pav:importedFrom in my opinion. This is why we
added in http://purl.org/pav/html#http://purl.org/pav/importedFrom the
phrase:
> The imported resource does not have to be c
Papers submission - September 15th, 2014
Call for Papers
7th International Workshop on Semantic Web Applications and Tools for the
Life Sciences (SWAT4LS 2014) Berlin, Germany Dec. 9-10th, 2014
http://www.swat4ls.org/workshops/berlin2014
Overview
Since 2008, the SWAT
