We have come to a conclusion during the call, where we decided to use a
free-text comment approach.
See:
https://github.com/joejimbo/HCLSDatasetDescriptions/issues/65#issuecomment-46861614
Kim
On 23 June 2014 08:45, Alan Ruttenberg wrote:
>
>
>
> On Mon, Jun 23, 2014 at 11:27 AM, Jerven B
On Mon, Jun 23, 2014 at 11:27 AM, Jerven Bolleman wrote:
> Again, I think we should encourage more specificity than the boolean
> property flag.
>
> One academic makes the following statements
>
> _:sillyAcademicsDataset a dct:Dataset ;
> prov:wasDerivedFrom realworld:commercial
Again, I think we should encourage more specificity than the boolean
property flag.
One academic makes the following statements
_:sillyAcademicsDataset a dct:Dataset ;
prov:wasDerivedFrom realworld:commercialDataset .
realworld:commercialDataset a dct:Dataset ;
Yes. And the understandability of the class is just as dependent on the
documentation as understanding the property.
-Alan
On Mon, Jun 23, 2014 at 11:22 AM, Jim McCusker wrote:
> A boolean is good enough to set a class from:
>
> Class: OpenLicenseData
> EquivalentClass: hasOpenLicense value tru
A boolean is good enough to set a class from:
Class: OpenLicenseData
EquivalentClass: hasOpenLicense value true
Class: ClosedLicenseData
EquivalentClass: hasOpenLicense value false
It makes the properties more specific, sure, but it's more than enough to
go on in many situations.
Jim
On Mon,
On Mon, Jun 23, 2014 at 11:08 AM, Joachim Baran
wrote:
>
> On 23 June 2014 06:37, Alan Ruttenberg wrote:
>
>> In the case that the license is not asserted it distinguishes the case
>> where the publisher has made an affirmative effort to determine what the
>> license is, or not.
>>
> I cannot
On 23 June 2014 06:37, Alan Ruttenberg wrote:
> In the case that the license is not asserted it distinguishes the case
> where the publisher has made an affirmative effort to determine what the
> license is, or not.
>
I cannot fathom how this could be inferred from the truth value of a bit.
On Monday, June 23, 2014, Jerven Bolleman wrote:
> Booleans, in this case, are like answers on a math exam without
> showing your work. They might be right or they might be wrong, but no
> one knows how you got there.
Mind your metaphors ;)
How does the *datatype* make a difference on this matt
On Monday, June 23, 2014, Joachim Baran wrote:
>
> On 22 June 2014 19:30, Alan Ruttenberg > wrote:
>
>> What do you have against booleans? :)
>>
> My points were:
>
>With a boolean solution -- especially when it only denotes whether
> license lookup was tried -- it is not clear what inform
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYD
Booleans, in this case, are like answers on a math exam without
showing your work. They might be right or they might be wrong, but no
one knows how you got there.
I think it is critical in the semantic web that you describe what you
know (you might still be wrong) as in a world where we try to sha
11 matches
Mail list logo
