On Feb 15, 2006, at 4:18 PM, Considine, Toby ((Facilities Technology
Office)) wrote:
I am asked for a user name and password, which I do not
have. When I close that request screen, I go to the OASIS home page
where I seem to be able to get access to most pages, but I think the working
group pages are for members only.
Francois Grobler, Technical Director, IAI-North America,
should see the oBIX work to see how it fits with the IFC
model. Also Steve Selkowitz and Valdo B. at Lawrence Berkeley
National Laboratory and Kent Reed and Mark Palmer at the National Institute
for Standards and Technology. We might also want to have Steve Busby of
NIST take a look, but Kent and Mark will know best.
Trane has been involved with the IAI, at least via the
NIBS FMOC OMSI project. The other firms have not.
I am not familiar with SOAP/REST.
But does the link below work?\
If not, I can send you the PDF. I would very much like to
get some other eyes on the draft - I particularly would like to get an BIM eye
on it.
Right now I have commitments to implement by summer from
several large vendors - you can help make sure they implement the right thing.
I'm hearing NIAGRA/GridLogix/Johnson/Trane/possibly
Honeywell/Echelon/...
The one real problem I see in the short term is that many
will do their first drafts in REST (because it feels more like the way they
always did it)
I programmer shared this perspective on the SOAP/REST
spin the other day which I quite liked
I feel like REST
makes simple things easy and hard things difficult, SOAP/WS-* makes simple
things difficult and hard things easy...
REST is about
point-to-point, simple invocations where the application defines the meaning
of the data. WS-* has its strength in 'routeability' and
composability, along with security, and support of constructs more familiar
to message queuing applications, such as reliability and transactional
aspects. The other thing about SOAP is that many of these aspects are
'toolable', declarative, and composable (you don't use what you don't need)
instead of depending on implementation code.
Clearly the BIM itself is about SOAP. But if we get to
common tagging/interaction/eventing standards, we can get to standard
transforms to/from BIM/GBXML/Sel Commissioning/Document-based communications
as the next step.
Do you know any XML/BIM guru who would be willing to look
at the spec and send me some comments?
tc
Good to hear from you. Not sure if you are
aware of all of the work in progress with the International Alliance for
Interoperability - now more frequently branded "buildingSMART" and the effort
to establish a National Building Information Model Standard through the
National Institute of Building Sciences' Facility Information Council. I
sent your name to the Testing Subcommittee which is led by Mark Reinhardt and
George Percivall of the Open Geospatial Constortium. OGC is a member of
OASIS. I have a small project underway funded by NASA and a working
group of the National Science and Technology Council which concentrates on
implementing the OMSI component of the IFC model within the SpecsIntact
software and the Unified Facilities Guide Specifications (Federal construction
specifications) and a webtool used by several agencies called ProjNet.
The NIBS FMOC will have a meeting and a booth during the National Facilities
Management and Technology Conference in Baltimore next month. If anyone
from OBIX will be attending, perhaps you can point them to us.
Being I am not a member of OASIS, I am not sure if I
can get to the information on OBIX XML committee, but I expect that George
can.
Bill Brodt
Experimental Facilities
Engineer
Facilities
Engineering and Real Property Division
NASA HQ Mail Stop LD030
300 E St SW
Washington DC 20546
202 358 1117
wbrodt@nasa.gov
I am sending you this
note because, if my notes and list editing are correct, you have expressed an
interest in oBIX in the past and you are not currently getting OASIS mailings
on the subject. I may be wrong, in which case I apologize for any
duplication.
The public face of oBIX
has been quiet for a while. This must be laid at my feet, due to some
health/rehab issues that have led me to drop many issues (Don’t ask – not
because I am sensitive, or shy about them – on the contrary I find the details
fascinating will happily tell you *all* about it and there will go the rest of
your day)
Fortunately, the XML
committee has been hard at work, and the XML standard, half-baked when
last the public peaked into
peaked into the oven, now looks and smells ready to pull out and
consume. We will be having a conference call at
the end of next week to discuss the timeline for completion. If all goes as
anticipated we may have two interoperability fests during May (wan to
participate?) and have multiple implementations of a draft standard by
Summer.
If you would like to be informed, or to participate,
please let me know. If you would like to submit comments and want to know when
the formal review process starts, let me know. If you have any questions, let
me know.
If you have not read the
latest work, please do.
thanks
Toby Considine
Co-Chair,
oBIX