RE: RE: [obix-xml] oBIX 1.1 Issues

This skates close to an old notion that the integrator out to be able to set up named contracts. A named contract can then be invoked as if one had instead sent a whole collection of points. The result is a GUID that is *your* invocation of the contract.

Inviting a contract to a meeting would then be straight forward. Possibly we need a slot in the ICAL structure to hold the GUID when it is instantiated. Would I then request the current meeting, retrieve the GUID(s) assigned, and then watch the progress of the contract (if appropriate)

"When one door closes, another opens; but we often look so long and so regretfully upon the closed door that we do not see the one which has opened for us." -- Alexander Graham Bell

Toby Considine

Chair, OASIS oBIX TC
Facilities Technology Office
University of North Carolina
Chapel Hill, NC

Email: Toby.Considine@ unc.edu
Phone: (919)962-9073

http://www.oasis-open.org

blog: www.NewDaedalus.com

From: Brian Frank [mailto:bfrank@tridium.com]
Sent: Tuesday, October 02, 2007 1:37 PM
To: Richards, Dave; obix-xml@lists.oasis-open.org
Subject: RE: [obix-xml] oBIX 1.1 Issues

> 8) Are multiple RRULE’s necessary for us? Yes, it’s legal in iCalendar, but what is the value?

Some things can have multiple instances that we can’t ignore such as the ATTENDEE property. That leads me to think that maybe capturing properties via a contract rather than a name might be better. Plus any property that uses property parameters will require contracts. Although the downside is contract explosion.

obix-xml message