Dear Antoine,
> Thanks for the offer! It would be great.
My pleasure!
> the idea would be to register your story and requirement in our database at
> http://lelystad.informatik.uni-mannheim.de/rdf-validation/
> So that it eventually appears as an official DC requirement.
> For this we need a requirement in the database, a use case that requires it, and
> a case study that motives the use case.
[...]
> What we'd need now is a generic description of the use case. Something like:
> [
> Title: Accessing data about a resource according to a specific profile
> Description:
> For a same resource (URI), various RDF descriptions are available,
> corresponding to different application profiles.
> A Linked Data consuming service accesses these different descriptions using the
> same URI for the resource, by specifying which profiles he wants to get the
> data according to.
> For example ....
> ]
>
> And then a requirement, like:
> [
> Title: Serving different data profiles depending on client request
> Description:
> Linked Data content negotiation recipes are updated/extended so that for a
> same resource URI, it is possible to serve different descriptions depending on
> the application profiles a client is interested in (as specified by an URI).
> Possible solutions are described at
> http://wiki.dublincore.org/index.php/RFC-6906-Profiles
> ]
OK, I won't get to it this week, but at least I shall have it ready in time for the telco on June 18.
Best,
Lars
|