[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [egov] Countermeasures for Epidemic of Congressional Ignorance?
Farrukh Najmi wrote: > judith.jerome@cabinet-office.x.gsi.gov.uk wrote: >> And along the same lines, what about some openly developed geospatial >> information systems similar to those proposed by the Open Geospatial >> Consortium? It is the actual 'location' of the corner of Haight and >> Ashbury *and* how to get there which becomes operative in these >> emergency scenarios. And geographic information, by definition, (off >> shore, coastal, satellite imagery etc.) is cross-border. >> What about a project where we combine GIS intelligence with ebXML >> registry based info and a semantic interoperability approach? >> >> Just thoughts of the moment. >> > An excellent thought Judy. The Open GIS consortium has developed their > own specs to build upon a profile of ebXML Registry. > See link [14] in ebXML Registry metalink page: > > http://ebxmlrr.sourceforge.net/tmp/ebXMLRegistryLinks.html Oops! my mistake. That was the wrong link. I do not have the link to the the Open GIS profile for using ebXML registry. Below is a message from Richard Martell on the subject. Richard, if you send me a link to the draft spec I will be sure to include it in the ebXML Registry metalink page. Thanks. <Richard Martell> Hi all, There is a body of work in the OGC on sensor networks that you may want to explore further. A very brief overview regarding the role of catalogue/registry services follows. We're currently working on an OGC catalogue profile (CSW-ebRIM) based on ebRIM 3.0 plus a number of other OGC specs. This is currently in draft and it isn't too far from a 1.0 release (I'm the editor). The main base specs are: * OASIS ebRIM 3.0 * OGC Catalogue Services 2.0 (but only the CSW part, Clause 10) * OGC Filter grammar 1.0 * OGC Geography Markup Language 3.1 (ISO 19136) In OGC test beds we've done some work handling sensor descriptions; typically these are stationary environmental sensors or traffic sensors described using SensorML <http://vast.nsstc.uah.edu/SensorML/>. The catalogue provides access to sensor descriptions and supports non-spatial and spatial searches (e.g., find services that provide access to water quality sensor data within 100 km of Vancouver, Canada.). In this case, the services were OGC Web Feature Services that provide sensor data (real-time or archival) as GML observation data. With respect to registry functionality, we've been thinking a bit about the concept of a "SensorNet" extension package as a way to define and bundle up a cohesive set of extension elements related to sensors and sensor networks; this would use GML to represent geometry and topology, and include such artifacts as a sensor taxonomy, new object types, slots, units dictionary, etc. Publishing such a package would be a way to advertise the fact that a given registry is "sensor-aware". <Richard Martell> >> Judy >> >> Judith A. Jerome >> >> Geographic Information Specialist >> >> UK Cabinet Office, e-Government Unit (Infrastructure Services) >> >> Stockley House, 130 Wilton Road, London SW1V 1LQ >> >> Email: Judith.Jerome@Cabinet-office.x.gsi.gov.uk >> >> Tel: +44 (0)207 276 3202 >> >> Mobile: +44 (0)7887 690 616 >> >> Fax: +44 (0)207 276 3292 >> >> >> -----Original Message----- >> From: Farrukh Najmi [mailto:Farrukh.Najmi@Sun.COM] Sent: Monday, >> September 19, 2005 10:58 PM >> To: peter@justbrown.net >> Cc: 'Rex Brooks'; 'Duane Nickull'; huml@lists.oasis-open.org; >> emergency@lists.oasis-open.org; egov@lists.oasis-open.org; >> sia-pilot6@humanml.cim3; Colin.Wallis@ssc.govt.nz >> Subject: Re: [egov] Countermeasures for Epidemic of Congressional >> Ignorance? >> >> Peter F Brown wrote: >> >>> Interesting thread: just been talking in Vienna today on exactly this >>> >> sort >> >>> of use case with Edwin Bruce, head of eGov projects in the New Zealand >>> government. We both think that there are opportunities for >>> >> collaboration in >> >>> such pilots: one only has to look at the recurrence of major seasonal >>> flooding in Central Europe in the last few years or the ever present >>> background threat of a major health pandemic, such as Avian flu...these >>> >> are >> >>> all naturally cross-agency and cross-border phenomena and the ebXML >>> federated registry model coupled with some semantic interoperability >>> approach would indeed seem to fit the bill.... >>> >>> >> This scenario is very similar to one a bunch of us collaborated on at >> XML 2003. >> >> Slides are at: >> >> http://ebxmlrr.sourceforge.net/presentations/oasis-demo-xml2003.sxi >> http://ebxmlrr.sourceforge.net/presentations/oasis-demo-xml2003.ppt >> >> The scenario was of Avian Flu Epidemic when it was big news in far east >> :-) >> >> It used ebXML Registry, ebXML Messaging, ebXML CPP/A, XForms, XACML etc. >> >> If it were done today OASIS CAP would also be included and >> potentially some other standards and technologies. >> >>> Peter >>> >>> -----Original Message----- >>> From: Rex Brooks [mailto:rexb@starbourne.com] Sent: 19 September >>> 2005 21:30 >>> To: Duane Nickull; Rex Brooks; huml@lists.oasis-open.org; >>> emergency@lists.oasis-open.org; egov@lists.oasis-open.org; >>> sia-pilot6@humanml.cim3 >>> Subject: RE: [egov] Countermeasures for Epidemic of Congressional >>> >> Ignorance? >> >>> Thanks foor the reply, Duane, >>> >>> The pilot project I'm working on now does some of this and is a >>> >> Semantic >> >>> Interoperability Rachitecture Pilot as well as being SOA in a loosely >>> coupled way, and we plan to use ebXML REgistry/Repository as well as >>> >> many >> >>> other components. It's far from any kind of panacea, but i think it >>> >> will be >> >>> a small step in the right direction. >>> >>> Regards, >>> Rex >>> >>> At 12:20 PM -0700 9/19/05, Duane Nickull wrote: >>> >>> >>>> Rec: >>>> >>>> Sadly, in a previous company we proposed an architecture to the >>>> Canadian Government (prior to being acquired by Adobe) for a low costs >>>> >> >> >>>> system that would have helped alleviate some of the problems from this >>>> >> >> >>>> type of emergency. >>>> >>>> While dwelling on the past is important to learn lessons, I also think >>>> >> >> >>>> it is important to look forward and take action. The proposed >>>> system was registry based and would allow government and civilian >>>> entities >>>> >> to >>>> register the following via easy to use web forms: >>>> >>>> 1. What types of events they wish to be notified about and when. >>>> Example: If there is a landslide in the Rocky Mountains that blocks >>>> a public highway, notify me since I am a civilian trucking company >>>> and I >>>> >> >> >>>> need to know this to reroute my trucks or "Tell me about potential >>>> hurricanes 48 hours in advance since I have to collect and evacuate >>>> elderly people". >>>> >>>> 2. A list of anything they have that they would make available >>>> during an emergency. Example: I have a diesel generator and 200 >>>> gallons of fuel in my backyard >>>> >>>> 3. Details of any services they are prepared to offer during an >>>> emergency (example: I have a chainsaw and can help cut through >>>> fallen trees. >>>> >>>> 4. Details of how they can be contacted in an emergency including >>>> backup plans in case no infrastructure exists (example: If the >>>> phones are out, I will be at the corner of Haight & Ashbury. >>>> >>>> 5. Workflows and procedures for emergency workers to take. >>>> >>>> The idea is that everyone who has a stake in a situation would have >>>> a chance to play a role. Agencies from local governments to >>>> international relief workers could all use it. >>>> >>>> The architecture is public record since it was submitted to the GoC as >>>> >> >> >>>> an RFI proposal. Anyone interested in seeing it or making use of >>>> it please let me know and I can forward it to them. >>>> >>>> I think systems like this would only cost around CAD $100,000 to >>>> implement and probably minimal $$ to keep operational. A bargain >>>> compared to the chaos that can result when things go wrong. >>>> >>>> The architecture used the OASIS CAP and the ebXML >>>> Registry/Repository standards along with other web service standards. >>>> >>>> Anyone want to build it? >>>> >>>> Duane >>>> >>>> -----Original Message----- >>>> From: Rex Brooks [mailto:rexb@starbourne.com] >>>> Sent: Monday, September 19, 2005 8:06 AM >>>> To: huml@lists.oasis-open.org; emergency@lists.oasis-open.org; >>>> egov@lists.oasis-open.org; sia-pilot6@humanml.cim3 >>>> Subject: [egov] Countermeasures for Epidemic of Congressional >>>> >> Ignorance? >> >>>> Hi Everyone, >>>> >>>> Please excuse the inept and mangled metaphors, but I think I have a >>>> concussion from being hit by this um, fiscal responsibility? >>>> >>>> I note this with considerable dismay since it looks a lot like we >>>> suddenly discovered that we are hemorrhaging from a leg so we are >>>> >> going >>>> to amputate our right arm as if we could somehow save the blood in >>>> >> that >>>> arm or keep it from flowing out our gashed leg. Let's ignore how >>>> much work that arm could do, for things like, well, tying a >>>> tourniquet around the wound from which we are actually bleeding? >>>> >>>> http://fcw.com/article90814-09-16-05-Web&newsletter%3Dyes >>>> >>>> Better idea. Let's rescind the minimum wage and hire all those >>>> displaced refugees, oops, no, they're called.... what was it? Ah >>>> yes, evacuees. How much more civilized can you get? I never thought >>>> ignorance was contagious till now. >>>> >>>> Rex >>>> -- >>>> Rex Brooks >>>> President, CEO >>>> Starbourne Communications Design >>>> GeoAddress: 1361-A Addison >>>> Berkeley, CA 94702 >>>> Tel: 510-849-2309 >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this mail list, you must leave the OASIS TC >>>> that generates this mail. You may a link to this group and all >>>> your TCs in >>>> >> >> >>>> OASIS >>>> at: >>>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >>>> >>> -- >>> Rex Brooks >>> President, CEO >>> Starbourne Communications Design >>> GeoAddress: 1361-A Addison >>> Berkeley, CA 94702 >>> Tel: 510-849-2309 >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this mail list, you must leave the OASIS TC that >>> generates this mail. You may a link to this group and all your TCs in >>> >> OASIS >> >>> at: >>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this mail list, you must leave the OASIS TC that >>> generates this mail. You may a link to this group and all your TCs in >>> >> OASIS >> >>> at: >>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >>> >>> >> >> >> > > >------------------------------------------------------------------------ > >--------------------------------------------------------------------- >To unsubscribe from this mail list, you must leave the OASIS TC that >generates this mail. You may a link to this group and all your TCs in OASIS >at: >https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > -- Regards, Farrukh
begin:vcard fn:Farrukh Najmi n:Najmi;Farrukh email;internet:farrukh.najmi@sun.com tel;work:781-442-9017 url:http://ebxmlrr.sourceforge.net/tmp/farrukhRacePointIcon.jpg version:2.1 end:vcard
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]