Shadi
that's spot on! 'time' was used as an example of a condition that
might be relevant - devices is obvious, but also fatigue, presence of
an assistant, all sorts of things....
Liddy
On 18/06/2012, at 8:51 PM, Shadi Abou-Zahra wrote:
> Hi Liddy,
>
> Thanks for clarifying. I was just checking whether "time" is the
> only parameter for some needs. Otherwise I thought it could
> generalized to:
>
> 1. which of my requirements applies when [time, device, ...?]
> 2. can I be given what I need
>
> Excuse if I'm off, I don't understand the full context. Just a
> thought.
>
> Best,
> Shadi
>
>
> On 18.6.2012 10:46, Liddy Nevile wrote:
>> Shadi
>>
>> as I understand it, people will have different 'times' for the
>> conditions and so there is a two step process needed:
>> 1. which of my requirements applies right now
>> 2. can I be given what I need
>>
>> We have been encouraged to work with a big conditional profile and
>> then
>> the one that is to be applied....so needs can be prerecorded for
>> convenience...
>>
>> I think this way, individuals could choose their conditions...
>>
>> Liddy
>>
>> On 18/06/2012, at 3:30 PM, Shadi Abou-Zahra wrote:
>>
>>> Hi Liddy,
>>>
>>> Can this be generalized to generic conditions? There could also be a
>>> use case for "6am-6pm during working days" or whatever (ie. not only
>>> the time of day but also other parameters).
>>>
>>> Maybe OWL can address such conditions in predicate logic terms?
>>>
>>> Regards,
>>> Shadi
>>>
>>>
>>> On 8.5.2012 15:28, Liddy Nevile wrote:
>>>> Now that I have sent the question, I can see that there is a
>>>> problem I
>>>> did not deal with. While it might be possible to have two fixed
>>>> time
>>>> periods, how about all the possible time periods? something
>>>> better needs
>>>> to be done!
>>>>
>>>> Liddy
>>>>
>>>>
>>>> On 08/05/2012, at 1:21 PM, Liddy Nevile wrote:
>>>>
>>>>> Would people like to contribute to this discussion, please.
>>>>>
>>>>> The GPII needs to be able to describe a requirement for a
>>>>> resource as
>>>>> including the conditional that if the time is 6 am - 6 pm the font
>>>>> should be green but if it is another time, the font should be
>>>>> red -
>>>>> for example.
>>>>>
>>>>> I think that there are a few ways of doing this but they would
>>>>> include:
>>>>>
>>>>> resource - My Story
>>>>> property - font-colour-6am-6pm
>>>>> value - green
>>>>>
>>>>> and there might also be
>>>>>
>>>>> resource - My Story
>>>>> property - font-colour-6pm-6am
>>>>> value - red
>>>>>
>>>>> where font-colour-TIME is a refinement of font-colour, that is
>>>>> itself
>>>>> a refinement of font, probably.
>>>>>
>>>>>
>>>>> It might also be that there are two properties: time and font-
>>>>> colour,
>>>>> of course, and they both need to be satisfied?
>>>>>
>>>>> I do not want a conditional as an attribute of a property but
>>>>> included
>>>>> in the property(ies). That is, I don't think we should have a
>>>>> property
>>>>> and then in its description in the namespace add a conditional.
>>>>> This
>>>>> has been assumed by some as the only way to make the property.
>>>>>
>>>>> What do you think?
>>>>>
>>>>> Liddy
>>>>
>>>
>>> --
>>> Shadi Abou-Zahra - http://www.w3.org/People/shadi/
>>> Activity Lead, W3C/WAI International Program Office
>>> Evaluation and Repair Tools Working Group (ERT WG)
>>> Research and Development Working Group (RDWG)
>>
>
> --
> Shadi Abou-Zahra - http://www.w3.org/People/shadi/
> Activity Lead, W3C/WAI International Program Office
> Evaluation and Repair Tools Working Group (ERT WG)
> Research and Development Working Group (RDWG)
|