Versions of that drawing are older than 1999. Feedback is
fielded systems talk in terms of roles, subscriptions for
forth. Outside of real-time 3D, I'm not even sure what terms like
concern is that over time, introducing more liaisons,
organizations and overlapping
standards will complicate the process, lengthen it, and dilute the
outcome. My hope
that DHS is able to create a strategy for short-term systems to be deployed in
two years, middle term for the next five to seven years, and out to ten years
realistically as far as we can play. For this to work, a Draconian
reduction in the
standards and terminology and organizations that produce them is
Otherwise, this becomes CALS again and we will watch
another $4 billion evaporate
without fielding any interoperable systems.
Actually, the work of the IETF pre-dates anything being done in this area
by OASIS, the OGC, or OMA. The original SIP Internet RFC dates back to 1999.
SIP has been extended since then and there are a number of companion RFC's
related to presence, events, and so forth. And while PIDF and PIDF-LO are
working their way through the IETF process, I think that it is excellent that
OMA is building on the work of other standards organizations rather than
re-inventing the wheel. Further, the PIDF-LO draft leverages the work of the
OGC - uses GML 3.1.
----- Original Message -----
Sent: Tuesday, June 07, 2005 12:01
Subject: RE: [emergency] RE: OMA
Specification that may be highly relevant to EDXL work. Check it out.
is amazing how many ways and terms we can find to abstract
roles and subscriptions so we can have yet another locus of
control based standard.
Standards and speeches: the full time consultant
Personally rooting for the DHS ontology efforts to tie it all
I dug around the Open Mobile Alliance (OMA) site - actually
looking for standards info OASIS can use as part of their EDXL work.
Reviewed a document titled OMA-TS-Presence_SIMPLE-V1_0-20050427-C. The intro
The document defines an application level specification for
the OMA SIP/SIMPLE-based Presence Service. It defines the presence
information semantics for presence information conveyed using the Presence
Information Data Format (PIDF) the Rich Presence Information Data Format
(RPID) and geographical information conveyed in a GEOPRIV location object
(see [PIDFLO]) specified by the IETF in conjunction with the overall
Presence Data Model defined in