Can we output expanded JSON-LD by default?

[dannylamb]

@DiegoPino what do you think? I want to use the jsonld serializer to return responses AND put jsonld on the queue. I'd prefer it be expanded when getting passed to Fedora. Can we make that the default?

I'd like to explore other options (like auto-generating contexts and allowing the user to request different representations through the use of headers) later, but for now would like to simplify things if possible.

[dannylamb]

Talking to @acoburn has revealed the use of "profile" within the accept header. Fedora 4 is doing something like Accept: application/ld+json; profile=\"http://www.w3.org/ns/json-ld#expanded\".

Now, we don't strictly enforce Accept headers, but we could still look for this and act on it. 👍 for a standard way of describing which jsonld operation you want to perform upon request.

[acoburn]

The JSON-LD spec describes this here: https://www.w3.org/TR/json-ld/#application-ld-json

[DiegoPino]

OK, can do that. Have to see where do i have to cut/break/hack to be able to have a clean header access. If not, can make it the default via config options. Is that right for you @dannylamb?

[dannylamb]

@DiegoPino right now all i need is the serializer to output expanded jsonld. I'm outside of the HTTP layer and I'm using it to publish to a queue. That will unblock me for the time being.

We can map out the specifics for headers and GET requests separately as part of #398.

[DiegoPino]

@dannylamb will do that for today. 😄

[dannylamb]

Hey @DiegoPino, can you give this a look when you have a chance? https://github.com/DiegoPino/claw-jsonld/pull/1

[DiegoPino]

@dannylamb yes, i'm my radar. Just finished fedora4camp and moved to my new apartment. You will get news on this on Friday.

[dannylamb]

@DiegoPino Those are definitely more important things than this. Just whenever you get a chance, man.