types

Ivan R. Judson judson at mcs.anl.gov
Tue Dec 10 23:27:46 CST 2002


In the types you've defined below, what's struct look like?

This looks like it matches the content I expected to see?

--Ivan

PS - Is this notation something I should have seen before and have forgotten
or is it something you've defined for conversational clarity?

> -----Original Message-----
> From: owner-ag-dev at mcs.anl.gov
> [mailto:owner-ag-dev at mcs.anl.gov] On Behalf Of Robert Olson
> Sent: Tuesday, December 10, 2002 3:22 PM
> To: ag-dev at mcs.anl.gov
> Subject: types
>
>
> 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
> }
>
>





More information about the ag-dev mailing list