Re: "Basic profile" terminology ?

hello all.

On 2012-07-07 18:34 , "Henry Story" <henry.story@bblfish.net> wrote:
>But I can see it would be fine for example to allow people to POST an
>atom-entry in a collection if there was a clear GRDDL for the atom-entry
>xml format.

i guess you're assuming that to be able to POST RDF? i am still unsure how
the platform is supposed to deal with scenarios like this: many protocols
have well-defined pre-conditions for what kind of interactions require
what kind of state representations. on the web, this is handled by media
types and very often, those are based on schemas (in atom's case, the
schema is augmented with prose that adds more constraints to the formally
defined schema). for a platform to support interactions which are
exchanging state information that needs to follow certain constraints,
there must be a model for how you can communicate those constraints, both
on the protocol level (media types on the web), and on the representation
level (schemas on the web when XML is used).

http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements is where arnaud
has made available the use cases and requirements for the LDP work, and so
far we have seen too little activity there. i'll add the scenario above
right now, and i'd like to encourage everybody to add there own use cases
and requirements. we still have very little input from the WG when it
comes to what we will actually work on, and we need this information so
that we can identify open issues and start working on them. please take a
little time today, read through
http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements, and maybe add
the scenario you're interested in. ideally, instead of just looking at a
very application-specific scenario, identify the issues you see with the
current stack of technologies, and also briefly mention where you think
there are open issues in the current stack that should be addressed by the
LDP WG.

thanks a lot and talk to you later today,

dret.

Received on Monday, 9 July 2012 06:56:55 UTC