[cap-talk] OO interoperation via OCap, presentation level issues

[John Carlson]

>
>
>> Is there no way to describe the essential and core
>> capability concept and to provide for communication
>> of capabilities between different systems (language
>> or OS) without getting drawn into issues such as the
>> synchrony of the communication and the presentation
>> of the data parameters?
>
> Well, just looking a the Ethernet standard, here:
>
> http://en.wikipedia.org/wiki/Ethernet#Ethernet_frame_types_and_the_EtherType_field
>
> As you may recall, Ethernet was standardized without a type field,  
> so it's conceivable to
> to provide for communication w/o a type field (as you can read, the  
> type was specified in
> another standard).


I hate to continue this topic, but...
You may have been referring to natural language, with it's notable  
lack of types.  Another thing you could do is something visual.  Is  
there a capability icon that would be useful?  Perhaps an icon with a  
key?



John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.eros-os.org/pipermail/cap-talk/attachments/20080519/5837683c/attachment.html