Re: issue-34 example

hello.

On 2013-01-21 12:54 , "Henry Story" <henry.story@bblfish.net> wrote:
>But you are writing about input, and speaking about multi step
>shopping processes which suggests POST and forms. Why does a shopping
>process require a form? Because a new State has to be created, and
>input requested from the user. That is some form of speech-act or rather
>document-act is going on here that goes beyond simply declaring how
>things are ( saying such and such is true ).
>What you want a LDPC to say is something like:
>  by POSTing a graph of a certain type here <> you
>are engaging in a speech/doc act of a certain type
>that will be named and referrable to later, and
>that may put a certain obligation on you.
>  Perhaps with a few examples as I said, one could look them
>up, see if there are patterns and how they could be implemented.

it would be interesting to see examples for this. in most service-oriented
frameworks, one would use a schema or some other form of class description
for the "POSTing a graph of a certain type" part, and then declarative
validation could be use to validate whether the client is engaging in the
kind of interaction that's part of the protocol. but we cannot validate in
RDF.

on the other hand, in other parts of the protocol we need very similar
preconditions, so that the protocol can for example state that when
POSTing to a container, only members are acceptable. maybe we can use the
same mechanism for "validating" RDF in both places? i don't think there's
a conceptual difference between these scenarios.

cheers,

dret.

Received on Monday, 21 January 2013 13:17:26 UTC