- From: Renato Iannella <r@iannel.la>
- Date: Fri, 3 Jun 2022 14:56:23 +1000
- To: Jim Larson <jim42@larson-tech.com>
- Cc: "public-odrl@w3.org Group" <public-odrl@w3.org>, Bruce Epstien <bepstein@bfd.fr>
- Message-Id: <05EC1EF2-D689-42C1-97F4-AC03EBCF992E@iannel.la>
Hi, here is my attempt to visualise the use case:
Cheers - Renato
> On 6 May 2022, at 14:16, Jim Larson <jim42@larson-tech.com> wrote:
>
> The following is valid:'
>
> “Siri must validate the voice of Joe before acting on any of his commands”
>
> there are two generalizations:
>
> (a) “Siri must validate the person speaking before acting on their commands”
>
> and
>
> (b) “voice systems must validate the voice of joe speaking before acting on their commands”
>
> -Jim
>
>
> On 4/29/2022 5:36 AM, Renato Iannella wrote:
>> Hi Jim, I am not sure I have the correct use case here….
>> but is this valid….
>>
>> “Siri must validate the voice of Joe before acting on any of his commands”
>>
>> which you want to generalise to:
>>
>> “All voice systems must validate the person speaking before acting on their commands”
>>
>>
>> R
>>
>>> On 22 Apr 2022, at 04:39, Jim Larson <jim42@larson-tech.com> wrote:
>>>
>>> I'm a novice in ORDL trying to understand if ORDL can be used as a constraint language for collaborative voice agents. Suppose Joe is a participant in a collaborative conversation with a synthetic voice agent. The following is my attempt to specify "Joe is validated by a speaker identification process." Is this ORDL specification correct?
>>>
>>> {
>>> "@context": "http://www.w3.org/ns/odrl.jsonld",
>>> "@type": "Offer",
>>> "uid": "http://example.com/policy:1012",
>>> "profile": "http://example.com/odrl:profile:06",
>>> “obligation": [{
>>> "target": "http://example.com/party/Joe",
>>> "action": “validate"
>>> }]
>>> }
>>>
>>> How do I modify the above to represent the constraint "Each speaker must be validated by a speaker identification process?“
>>>
>>> Regards,
>>>
>>> Jim Larson
>>> Open Voice Network
>>>
>
>
Attachments
- text/html attachment: stored
- image/png attachment: Screen_Shot_2022-06-03_at_14.55.38.png
Received on Friday, 3 June 2022 04:56:47 UTC