Re: User Hypermedia format

Inbound sounds like a reference from a different resource to a given resource. Do you mean Embedded? Or is there a precedent for describing transclusion, embedding as inbound?

-- 
http://matthewlmcclure.com

> On Feb 27, 2014, at 9:48 AM, Glenn Block <[email protected]> wrote:
> 
> Thanks
> 
> Is transclude a widely understood term? Did you consider having an attribute like link-type with values of 'outbound' or 'inbound'? When I first read H-Factors, the usage of outbound and inbound was very obvious. Transclude was not.
> 
> Just sharing my experience / very first impression.
> 
>> On Thursday, February 27, 2014, mike amundsen <[email protected]> wrote:
>> right, this aims directly at that H-Factors.
>> 
>> 
>> mamund
>> +1.859.757.1449
>> skype: mca.amundsen
>> http://amundsen.com/blog/
>> http://twitter.com/mamund
>> https://github.com/mamund
>> http://linkedin.com/in/mamund
>> 
>> 
>> On Thu, Feb 27, 2014 at 11:16 AM, Glenn Block <[email protected]> wrote:
>> Thanks for clarifying. So this relates to what are outbound and inbound links in HFactors?
>> 
>> 
>> 
>> On Thursday, February 27, 2014, mike amundsen <[email protected]> wrote:
>> Yep - Matt's got it.
>> 
>> these are equivalent:
>> 
>> <data url="..." rel="logo" transclude="true" />
>> and
>> <img src="..." rel="logo" />
>> 
>> 
>> 
>> mamund
>> +1.859.757.1449
>> skype: mca.amundsen
>> http://amundsen.com/blog/
>> http://twitter.com/mamund
>> https://github.com/mamund
>> http://linkedin.com/in/mamund
>> 
>> 
>> On Thu, Feb 27, 2014 at 7:12 AM, Matt McClure <[email protected]> wrote:
>> Glenn,
>> 
>> I'll let Mike correct me if I'm wrong but I believe transclusion is analogous to the behavior of an <img> or <iframe> element in HTML. It's telling the client to fetch the transcluded resource, just including it by reference instead of by value. 
>> 
>> Matt
>> 
>> -- 
>> http://matthewlmcclure.com
>> 
>>> On Feb 27, 2014, at 2:04 AM, Glenn Block <[email protected]> wrote:
>>> 
>>>  
>>> Hi Mike
>>> 
>>> Cool to see this. I am looking over the format. I can see there's some CJ footprints there ;-)
>>> 
>>> Question on transclude. What do you mean when you say that if it is true it should be embedded in the current document, do you mean it is already present inline?
>>> 
>>> I am asking in reference to this example:
>>> 
>>>               {
>>>                 "name" : "person",
>>>                 "rel" : "item",
>>>                 "url" : "http://example.org/people/1",
>>>                 "data" :
>>>                 [
>>>                   {"name" : "givenName", "value" : "Mike"},
>>>                   {"name" : "familyName", "value" : "Amundsen"},
>>>                   {"name" : "email", "value" : "[email protected]"},
>>>                   {"name" : "avatarUrl", "transclude" : "true", "value" : "http://example.org/avatars/1"}
>>>                 ]
>>>               },
>>> 
>>> Above, transclude is true. Where is the embedding / how does it play in?
>>> 
>>> Thanks
>>> Glenn
>>> 
>>> 
>>> On Sun, Feb 23, 2014 at 10:25 PM, mike amundsen <[email protected]> wrote:
>>>  
>>> yep - you got it right. 
>>> 
>>> i might add some prose that sets expectations on which level of support for RFC6570 is needed in order to be uber-compliant. that might lower the bar for implementation.
>>> 
>>> 
>>> 
>>> 
>>> mamund
>>> +1.859.757.1449
>>> skype: mca.amundsen
>>> http://amundsen.com/blog/