Re: License unknown

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 <mccusj@rpi.edu> wrote:

> 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, Jun 23, 2014 at 11:08 AM, Joachim Baran <joachim.baran@gmail.com>
> wrote:
>
>>
>> On 23 June 2014 06:37, Alan Ruttenberg <alanruttenberg@gmail.com> 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.
>>
>>
>
>
> --
> Jim McCusker
>
> Data Scientist
>  5AM Solutions
> jmccusker@5amsolutions.com
> http://5amsolutions.com
>
> PhD Student
> Tetherless World Constellation
> Rensselaer Polytechnic Institute
> mccusj@cs.rpi.edu
> http://tw.rpi.edu
>

Received on Monday, 23 June 2014 15:27:15 UTC