Perhaps we should figure out a use case, and see if we can specify against it in a way that provides a resolution.

Well, other than some of the issues in you guys supporting the demo service going forward, that would be an obvious place to do it and then be able to show some of the middleware support for this and other things in when surfing in a browswer .@brutski thoughts?

@fosrias @sheavalentine-mdsol Just had a discussion about this with @HonoreDB

source: example.org/resource
target: ...
prompt: ...

Client makes a call using farscape with content-type it wants to. Media-type response then will be deserialized into representor_hash by representors. Which means actually, that target/prompt should actually specify representor_hash path of some sort.

? Our media type and messages should know nothing about our client library
conventions, but follow internet specifications. May not be understanding
you. That being said, I think this should be addressed by associating one
of the enctypes @sheavalentine-mdsol
https://github.com/sheavalentine-mdsol added to Hale in some way w/r to
source and target to constrain the content negotiation of resolving a
source. Are we talking about different things?

On Thu, Aug 21, 2014 at 11:25 PM, brutski [email protected] wrote:

@fosrias https://github.com/fosrias @sheavalentine-mdsol
https://github.com/sheavalentine-mdsol Just had a discussion about this
with @HonoreDB https://github.com/HonoreDB

source: example.org/resourcetarget: ...prompt: ...

Client makes a call using farscape with content-type it wants to.
Media-type response then will be deserialized into representor_hash by
representors. Which means actually, that target/prompt should actually
specify representor_hash path of some sort.

—
Reply to this email directly or view it on GitHub
#4 (comment).