types

[Thomas Uram]

Plus StreamDescription, which of course also looks similar, but adds a 
capability.

Does the authorizationPolicy fit in the attributes struct?



Robert Olson wrote:

> So I came up with this set of types, used in representing various bits 
> of the system when sent to other bits of the system. It seems that 
> they are all the same; seems likely we could simply represent them all 
> using the same type with analog of typedef to particular types if we 
> care.
>
> attributes:struct below represents the "other stuff" that showed up on 
> teh board for at least a couple of them; it is the mechanism for 
> including information which we may not know at the time the types are 
> defined but may be applicable to a particular application.
>
> type IconType {
> iconType: string (png, jpg, etc)
> iconData: base64string
> }
>
> type URIType {
> uri: string
> }
>
> type VenueDescription {
> name: string
> description: string
> URI: URIType
> icon: IconType
> attributes: struct
> }
>
> type ConnectionDescription {
> name: string
> description: string
> URI: URIType
> icon: IconType
> attributes: struct
> }
>
> type DataDescription {
> description: string
> URI: URIType
> icon: IconType
> attributes: struct
> SomethingType (venue, user)
> }
>
> type ServiceDescription{
> description: string
> URI: URIType
> icon: IconType
> attributes: struct
> }
>
>