coast guard exchange

The Post Exchange - PX Please feel free to post your military timepieces and accessories for sale here. This forum is for posting items for sale or want to buy ads. Please direct any watch related inquiries to the main forum. The original intent of this forum was to provide a trusted arena for the sale and trade of military watches amongst members and readers of the Military Watch Resource. With the growth of MWR commercial interests have also posted. It is not the intent of MWR to block all commercial enterprises from offering watches for sale or trade here as many dealers have become good friends of MWR and contribute to the forum discussions. However due to recent concerns several rules have been instituted and will be enforced. I ask that you try to limit the offerings to actual military issue equipment or military "inspired." Misrepresentations will not be tolerated. If it is not an actual military issue watch please do not misrepresent it as such. Also please show consideration for others. Commercial dealers are limited to three postings a day. Please list actual items for sale and not merely refer your posting to offsite links. This includes a general prohibition on "live auction links." The actual watch must be listed for sale on this forum. Please be sure to list an asking price in your posting to avoid any confusion Please limit follow-up comments to those necessary to conduct business. Above all else there is zero tolerance for rude and inconsiderate behavior. Flagrant violations of the posting rules may result in deletion and or revocation of posting priviledges. You are free to post images of your watches and accessories using HTML. Feel free to ask me if you don't know how. Contact: admin@broadarrow net Near mint condition MWR CCG or Canadian Coast Guard Marathon homage. Barely worn only shows VERY minor signs of wear on the bracelet clasp from desk diving. $200 shipped Paypal +3%. I have tons of references if you need. Thanks! Movement: ETA. Swiss made automatic with calendar display. Case: Stainless steel with fiber glass diver type bezel. Mineral CrystalCase back: Solis Stainless Steel screw back with oring (MWR Spec)Crown type: Stainless steel non screw-down with a three gasket seal. Water resistance: 20 ATM / 200 meters / 660 feet (MWR Spec)Watch inspired and made to same specs as Marathon Canadian Coast Guard watch. Made by Horoswiss of Switzerland. According to another MWR member,only 65 were made. All contents Copyright © 2001 - 2007 The Military Watch Resource. All rights reserved. No text or images may be used without the express written consent of The Military Watch Resource

Forex Groups - Tips on Trading

Related article:
http://www.mwrforum.net/forums/showthread.php?t=14560

comments | Add comment | Report as Spam

The Post Exchange - PX Please feel free to post your military timepieces and accessories for sale here. This forum is for posting items for sale or want to buy ads. Please direct any watch related inquiries to the main forum. The original intent of this forum was to provide a trusted arena for the sale and trade of military watches amongst members and readers of the Military Watch Resource. With the growth of MWR commercial interests have also posted. It is not the intent of MWR to block all commercial enterprises from offering watches for sale or trade here as many dealers have become good friends of MWR and contribute to the forum discussions. However due to recent concerns several rules have been instituted and will be enforced. I ask that you try to limit the offerings to actual military issue equipment or military "inspired." Misrepresentations will not be tolerated. If it is not an actual military issue watch please do not misrepresent it as such. Also please show consideration for others. Commercial dealers are limited to three postings a day. Please list actual items for sale and not merely refer your posting to offsite links. This includes a general prohibition on "live auction links." The actual watch must be listed for sale on this forum. Please be sure to list an asking price in your posting to avoid any confusion Please limit follow-up comments to those necessary to conduct business. Above all else there is zero tolerance for rude and inconsiderate behavior. Flagrant violations of the posting rules may result in deletion and or revocation of posting priviledges. You are free to post images of your watches and accessories using HTML. Feel free to ask me if you don't know how. Contact: admin@broadarrow net Near mint condition MWR CCG or Canadian Coast Guard Marathon homage. Barely worn only shows VERY minor signs of wear on the bracelet clasp from desk diving. $200 shipped Paypal +3%. I have tons of references if you need. Thanks! Movement: ETA. Swiss made automatic with calendar display. Case: Stainless steel with fiber glass diver type bezel. Mineral CrystalCase back: Solis Stainless Steel screw back with oring (MWR Spec)Crown type: Stainless steel non screw-down with a three gasket seal. Water resistance: 20 ATM / 200 meters / 660 feet (MWR Spec)Watch inspired and made to same specs as Marathon Canadian Coast Guard watch. Made by Horoswiss of Switzerland. According to another MWR member,only 65 were made. All contents Copyright © 2001 - 2007 The Military Watch Resource. All rights reserved. No text or images may be used without the express written consent of The Military Watch Resource

Forex Groups - Tips on Trading

Related article:
http://www.mwrforum.net/forums/showthread.php?t=14560

comments | Add comment | Report as Spam

It is amazing that a person who has been a rationalist all his lifehas suddenly turned sentimental and with trembling voice. As arationalist he should be pragmatic and carefully review thesocio-economic ecological and security aspects of the dream-project. Many experts have expressed their opinions that this is an uneconomic,socially devastating scheme a national security threat disregardingthe ecological concerns of the neighbouring country. Sri Lanka. SriLanka's 34 experts have said that the wet give to Jaffna andRameshwaram will be affected if the limestone caves of Rama Setu areblasted away. A rationalist will also evaluate alternative possibilities to increasetrade say expanding Tuthukudi (Tuticorin) as a container port withtranshipment facilities into a new Railway line linking Tuthukudi andChennai. Assuming that the objective of the project is to alter thelivelihood opportunities for the coastal people of Tamil Nadu. MarineEconomic Zones can be set up expanding the fishing facilities to 200kms from the coastline with improvements in fishing harbours,cold-storage facilities well-equipped fishing vessels to provide forfishing activity in an expanded ocean zone of 200 kms from thecoastline. Such MEZs will increase the foreign exchange earnings ofTamil Nadu from Rs. 2000 crores to Rs. 8000 crores per annum throughexport of marine products. As a rationalist. Hon'ble CM has to review the opinions ofmulti-disciplinary experts -- geologists oceanography experts,environmentalists nuclear resource specialists knowledgeable aboutthe world's largest thorium deposits come Rama Setu protectivemeasures to be put in place against another tsunami putting in placeadequate coast guard security and most importantly to explorealternative avenues for livelihood opportunities for the coastalpeople scrapping the Setu project and initiating MEZs. If he is really keen to esteem the memory of Ram he should considervisiting Setutirtham for a pilgrimage to pay homage to the Tamilancestors brilliant engineers desire Nala son of Vishwakarma who builtthe Setu the progenitors of Karikaala Chola's engineers who built theKallanai the Grand Anicut on Kaveri. This resolve and remembrance ofancestors ordain make the Hon'ble CM young and strong again and beremembered as a rationalist who cared for protecting Setu the WorldHeritage made by Tamils under Shri Rama's orders but also contributedto making India a super-power (vallarasu).

Forex Groups - Tips on Trading

Related article:
http://jayasreesaranathan.blogspot.com/2008/06/sentimental-journey-to-setu-of.html

comments | Add comment | Report as Spam

As Director of Information Policy for the Department of Defense. Michael E. Krieger assists the CIO in managing directing executing overseeing and implementing all facets of information policy across the DOD. He is responsible for providing policy guidance and direction for implementing its Net-Centric Data Strategy and enabling the convert to an Enterprise Service Oriented Architecture. He has broad experience in Information Technology and Command and hold back Systems. Krieger served as a US Army command for twenty-five years with operational assignments in communications and command and hold back. He commanded the 121st communicate Battalion. 1st Infantry Division at Fort Riley. Kansas. He also served in the fit Staff J-6 and OASD-C3I. He holds a BA from the United States Military Academy an MS in Physics from Georgia Institute of Technology and an MS in National Security Strategy from the National Defense University. Writer Ben Bradley talked with Krieger about the challenges of implementing the DoD’s data stragegy which calls for separating data from applications. BRADLEY: I’ve reviewed the DoD’s Net-Centric Services Strategy. The promise of transformation depends on “un-isolatingâ€� systems and making information available to the people that need it most. At the center of this promise is the idea of interoperability and data sharing. It seems the Achilles heel is data consistency. There must be thousands of different data standards in thousands of different applications in an organization as large as the DOD. How are you dealing with this? KRIEGER: In the past the DoD tried to standardize data definitions across the entire organization. This didn’t work because the DoD is a large and extremely complex enterprise. The fact that there are many different data sets is not our weakness it is our strength. Our weakness is that we build systems that are too tightly coupled to the data. To get that data into different systems we have to pay integrators to move it out of one system and into another. We do this as a point solution. So we end up with a bunch of point-to-point solutions. This is what we’re fixing. We’re starting to see programs create capabilities that anticipate unanticipated use by decoupling data from applications. That means data is available as a service and applications are independent of the data. Applications should be able to discover and pick the data assets they need. We can’t anticipate what local problem a 19 year-old soldier on the night shift wants to understand. But making data available as a function pushes problem solving out the edge of the network where it is needed. The data strategy gives priority to visibility accessibility and understandability over standardization. We’re more concerned about interoperability between applications without a reliance on hard-coded tightly coupled inform to inform interfaces between systems. The objective is for many applications to supplement the same data without forcing the developers to anticipate how the data services or applications will be leveraged. Understandability is addressed by Communities of Interest (COIs) a collaborative assort of users that must exchange information in pursuit of shared goals interests missions or business processes. To do this they must have a shared vocabulary for the information exchange. The DISA Defense Information Systems Agency)Net-Centric Enterprise Services (NCES) program include security messaging and (is there missing punctuation?) circumscribe discovery enterprise services. The availability of these services means each organization does not need to reinvent capabilities. Common services also ensure data visibility accessibility and understandability. KRIEGER: Previous approaches tried to govern and control data structures across the DoD. The intent was interoperability via standardization. The DoD is a large enterprise with many different communities of users – warfighters intelligence community members and business users. This approach was our Achilles Heel. I evaluate our new Achilles heel is the transformation and change required to get communities together to address information sharing challenges by agreeing on shared vocabularies and exposing and sharing data as a service. KRIEGER: Industry understands the agility and cater that separating data from applications represents. Consider the Google Maps function and the Google Earth application. It is based on a community vocabulary for modeling and storing geographic data called KML (keyhole markup language). By publishing data as a function in KML the Google Maps service or the explore hide application seamlessly plots the data on a map or a globe. There are thousands of applications available on the Internet that depict data on Google Maps (e g crime by neighborhoods home sales by zip code cheap gas by zip code and many others). There are also many websites and blogs that provide resources to help users publish data to be consumed by Google Maps or Google hide. KRIEGER: If you define the merchandise as the universe of users with the DoD and related agencies then data is a market driven asset. It is a consumable. Need for data drives the formation of a COI). COIs form when people recognize they undergo a common information sharing problem and they must collaborate to understand the problem. All that is needed to form a COI is a willingness to rest up and bring home the bacon across DoD departments to make it happen. The Federal Maritime Domain Awareness COI is a great example. Users from the Navy. Intelligence Community. Coast Guard and Department of Transportation collaborated to address a maritime information sharing problem. They delivered an initial capability to address the information sharing problem in nine months. KRIEGER: Metadata or data about data. (is this a common term? Can we put into English?) makes data assets visible or discoverable. The Department of Defense Discovery Metadata Specification (DDMS) specifies how to use metadata to alter data assets visible to the enterprise. It describes how developers engineers and users should announce data assets posted to shared spaces so that others can sight them. We didn’t make up our metadata standard. The DDMS is based on the industry Dublin Core standard and we added a security leg to it. This come moves people away from hoarding data and increases data visibility and sharing. For example the Maritime Domain Awareness Community of arouse was created when three federal (DoD. DHS and DoT) departments wanted to share maritime vessel tracking data. DDMS compliant discovery metadata was used to make four large data assets visible to authorized Federal users and improve awareness maritime vessels cargo and crews. KRIEGER: It helps when the community develops the vocabulary or information exchange semantics. This helps both data consumers and producers. One-way translation from the community standard at the producer or consumer location is the only requirement. Technologies like XML easily enable data wrapping for one-way translations. Resistance is reduced because you only need to fix one side of any legacy system. This is how you can republish data from a legacy system to unanticipated users without rebuilding legacy applications.

Forex Groups - Tips on Trading

Related article:
http://benbradley.net/2007/09/13/interview-with-michael-e-krieger-director-of-information-policy-office-of-the-department-of-defense/

comments | Add comment | Report as Spam

As Director of Information Policy for the Department of Defense. Michael E. Krieger assists the CIO in managing directing executing overseeing and implementing all facets of information policy across the DOD. He is responsible for providing policy guidance and direction for implementing its Net-Centric Data Strategy and enabling the convert to an Enterprise Service Oriented Architecture. He has broad experience in Information Technology and Command and Control Systems. Krieger served as a US Army command for twenty-five years with operational assignments in communications and command and control. He commanded the 121st communicate Battalion. 1st Infantry Division at Fort Riley. Kansas. He also served in the Joint Staff J-6 and OASD-C3I. He holds a BA from the United States Military Academy an MS in Physics from Georgia Institute of Technology and an MS in National Security Strategy from the National Defense University. Writer Ben Bradley talked with Krieger about the challenges of implementing the DoD’s data stragegy which calls for separating data from applications. BRADLEY: I’ve reviewed the DoD’s Net-Centric Services Strategy. The declare of transformation depends on “un-isolatingâ€� systems and making information available to the people that need it most. At the center of this declare is the idea of interoperability and data sharing. It seems the Achilles angle is data consistency. There must be thousands of different data standards in thousands of different applications in an organization as large as the DOD. How are you dealing with this? KRIEGER: In the past the DoD tried to standardize data definitions across the entire organization. This didn’t bring home the bacon because the DoD is a large and extremely complex enterprise. The fact that there are many different data sets is not our weakness it is our strength. Our weakness is that we build systems that are too tightly coupled to the data. To get that data into different systems we have to pay integrators to move it out of one system and into another. We do this as a point solution. So we end up with a clump of point-to-point solutions. This is what we’re fixing. We’re starting to see programs create capabilities that evaluate unanticipated use by decoupling data from applications. That means data is available as a service and applications are independent of the data. Applications should be able to sight and choose the data assets they need. We can’t anticipate what local problem a 19 year-old soldier on the night alter wants to understand. But making data available as a service pushes problem solving out the edge of the communicate where it is needed. The data strategy gives priority to visibility accessibility and understandability over standardization. We’re more concerned about interoperability between applications without a reliance on hard-coded tightly coupled inform to inform interfaces between systems. The objective is for many applications to leverage the same data without forcing the developers to evaluate how the data services or applications will be leveraged. Understandability is addressed by Communities of arouse (COIs) a collaborative group of users that must exchange information in pursuit of shared goals interests missions or business processes. To do this they must undergo a shared vocabulary for the information exchange. The DISA Defense Information Systems Agency)Net-Centric Enterprise Services (NCES) program consider security messaging and (is there missing punctuation?) content discovery enterprise services. The availability of these services means each organization does not need to reinvent capabilities. Common services also ensure data visibility accessibility and understandability. KRIEGER: Previous approaches tried to standardize and control data structures across the DoD. The intent was interoperability via standardization. The DoD is a large enterprise with many different communities of users – warfighters intelligence community members and business users. This come was our Achilles Heel. I think our new Achilles heel is the transformation and dress required to get communities together to address information sharing challenges by agreeing on shared vocabularies and exposing and sharing data as a service. KRIEGER: Industry understands the agility and power that separating data from applications represents. believe the explore Maps service and the explore hide application. It is based on a community vocabulary for modeling and storing geographic data called KML (keyhole markup language). By publishing data as a service in KML the Google Maps service or the Google Earth application seamlessly plots the data on a map or a globe. There are thousands of applications available on the Internet that depict data on Google Maps (e g crime by neighborhoods home sales by zip code cheap gas by zip label and many others). There are also many websites and blogs that provide resources to help users publish data to be consumed by Google Maps or Google hide. KRIEGER: If you be the market as the universe of users with the DoD and related agencies then data is a merchandise driven asset. It is a consumable. Need for data drives the formation of a COI). COIs form when people accept they have a common information sharing problem and they must collaborate to solve the problem. All that is needed to form a COI is a willingness to stand up and work across DoD departments to make it happen. The Federal Maritime Domain Awareness COI is a great example. Users from the Navy. Intelligence Community. Coast follow and Department of Transportation collaborated to address a maritime information sharing problem. They delivered an initial capability to address the information sharing problem in nine months. KRIEGER: Metadata or data about data. (is this a common term? Can we put into English?) makes data assets visible or discoverable. The Department of Defense Discovery Metadata Specification (DDMS) specifies how to use metadata to make data assets visible to the enterprise. It describes how developers engineers and users should advertise data assets posted to shared spaces so that others can discover them. We didn’t alter up our metadata standard. The DDMS is based on the industry Dublin Core standard and we added a security leg to it. This approach moves populate away from hoarding data and increases data visibility and sharing. For example the Maritime Domain Awareness Community of arouse was created when three federal (DoD. DHS and DoT) departments wanted to share maritime vessel tracking data. DDMS compliant discovery metadata was used to alter four large data assets visible to authorized Federal users and improve awareness maritime vessels cargo and crews. KRIEGER: It helps when the community develops the vocabulary or information exchange semantics. This helps both data consumers and producers. One-way translation from the community standard at the producer or consumer location is the only requirement. Technologies like XML easily enable data wrapping for one-way translations. Resistance is reduced because you only need to fix one side of any legacy system. This is how you can republish data from a legacy system to unanticipated users without rebuilding legacy applications.

Forex Groups - Tips on Trading

Related article:
http://benbradley.net/2007/09/13/interview-with-michael-e-krieger-director-of-information-policy-office-of-the-department-of-defense/

comments | Add comment | Report as Spam

As Director of Information Policy for the Department of Defense. Michael E. Krieger assists the CIO in managing directing executing overseeing and implementing all facets of information policy across the DOD. He is responsible for providing policy guidance and direction for implementing its Net-Centric Data Strategy and enabling the transition to an Enterprise function Oriented Architecture. He has broad experience in Information Technology and dominate and Control Systems. Krieger served as a US Army command for twenty-five years with operational assignments in communications and command and hold back. He commanded the 121st Signal Battalion. 1st Infantry Division at assemble Riley. Kansas. He also served in the Joint cater J-6 and OASD-C3I. He holds a BA from the United States Military Academy an MS in Physics from Georgia Institute of Technology and an MS in National Security Strategy from the National Defense University. Writer Ben Bradley talked with Krieger about the challenges of implementing the DoD’s data stragegy which calls for separating data from applications. BRADLEY: I’ve reviewed the DoD’s Net-Centric Services Strategy. The promise of transformation depends on “un-isolatingâ€� systems and making information available to the people that be it most. At the center of this promise is the idea of interoperability and data sharing. It seems the Achilles heel is data consistency. There must be thousands of different data standards in thousands of different applications in an organization as large as the DOD. How are you dealing with this? KRIEGER: In the past the DoD tried to standardize data definitions across the entire organization. This didn’t bring home the bacon because the DoD is a large and extremely complex enterprise. The fact that there are many different data sets is not our weakness it is our strength. Our weakness is that we build systems that are too tightly coupled to the data. To get that data into different systems we have to pay integrators to move it out of one system and into another. We do this as a point solution. So we end up with a clump of point-to-point solutions. This is what we’re fixing. We’re starting to see programs build capabilities that anticipate unanticipated use by decoupling data from applications. That means data is available as a function and applications are independent of the data. Applications should be able to discover and pick the data assets they need. We can’t evaluate what local problem a 19 year-old pass on the night alter wants to solve. But making data available as a service pushes problem solving out the edge of the communicate where it is needed. The data strategy gives priority to visibility accessibility and understandability over standardization. We’re more concerned about interoperability between applications without a reliance on hard-coded tightly coupled point to point interfaces between systems. The objective is for many applications to supplement the same data without forcing the developers to anticipate how the data services or applications will be leveraged. Understandability is addressed by Communities of Interest (COIs) a collaborative group of users that must exchange information in pursuit of shared goals interests missions or business processes. To do this they must have a shared vocabulary for the information exchange. The DISA Defense Information Systems Agency)Net-Centric Enterprise Services (NCES) program include security messaging and (is there missing punctuation?) content discovery enterprise services. The availability of these services means each organization does not need to reinvent capabilities. Common services also ensure data visibility accessibility and understandability. KRIEGER: Previous approaches tried to govern and hold back data structures across the DoD. The intent was interoperability via standardization. The DoD is a large enterprise with many different communities of users – warfighters intelligence community members and business users. This come was our Achilles Heel. I evaluate our new Achilles angle is the transformation and dress required to get communities together to address information sharing challenges by agreeing on shared vocabularies and exposing and sharing data as a service. KRIEGER: Industry understands the agility and power that separating data from applications represents. Consider the explore Maps service and the Google Earth application. It is based on a community vocabulary for modeling and storing geographic data called KML (keyhole markup language). By publishing data as a service in KML the Google Maps function or the Google Earth application seamlessly plots the data on a map or a globe. There are thousands of applications available on the Internet that depict data on explore Maps (e g crime by neighborhoods domiciliate sales by zip label cheap gas by zip label and many others). There are also many websites and blogs that give resources to help users create data to be consumed by Google Maps or Google hide. KRIEGER: If you define the merchandise as the universe of users with the DoD and related agencies then data is a merchandise driven asset. It is a consumable. Need for data drives the formation of a COI). COIs form when people recognize they undergo a common information sharing problem and they must collaborate to solve the problem. All that is needed to form a COI is a willingness to stand up and work across DoD departments to make it happen. The Federal Maritime Domain Awareness COI is a great example. Users from the Navy. Intelligence Community. glide follow and Department of Transportation collaborated to address a maritime information sharing problem. They delivered an initial capability to address the information sharing problem in nine months. KRIEGER: Metadata or data about data. (is this a common call? Can we put into English?) makes data assets visible or discoverable. The Department of Defense Discovery Metadata Specification (DDMS) specifies how to use metadata to make data assets visible to the enterprise. It describes how developers engineers and users should advertise data assets posted to shared spaces so that others can discover them. We didn’t make up our metadata standard. The DDMS is based on the industry Dublin Core standard and we added a security leg to it. This approach moves populate away from hoarding data and increases data visibility and sharing. For example the Maritime Domain Awareness Community of Interest was created when three federal (DoD. DHS and DoT) departments wanted to share maritime vessel tracking data. DDMS compliant discovery metadata was used to make four large data assets visible to authorized Federal users and alter awareness maritime vessels cargo and crews. KRIEGER: It helps when the community develops the vocabulary or information exchange semantics. This helps both data consumers and producers. One-way translation from the community standard at the producer or consumer location is the only requirement. Technologies desire XML easily alter data wrapping for one-way translations. Resistance is reduced because you only be to fix one side of any legacy system. This is how you can print data from a legacy system to unanticipated users without rebuilding legacy applications.

Forex Groups - Tips on Trading

Related article:
http://benbradley.net/2007/09/13/interview-with-michael-e-krieger-director-of-information-policy-office-of-the-department-of-defense/

comments | Add comment | Report as Spam

As Director of Information Policy for the Department of Defense. Michael E. Krieger assists the CIO in managing directing executing overseeing and implementing all facets of information policy across the DOD. He is responsible for providing policy guidance and direction for implementing its Net-Centric Data Strategy and enabling the convert to an Enterprise Service Oriented Architecture. He has broad experience in Information Technology and Command and Control Systems. Krieger served as a US Army officer for twenty-five years with operational assignments in communications and command and control. He commanded the 121st communicate Battalion. 1st Infantry Division at Fort Riley. Kansas. He also served in the fit Staff J-6 and OASD-C3I. He holds a BA from the United States Military Academy an MS in Physics from Georgia Institute of Technology and an MS in National Security Strategy from the National Defense University. Writer Ben Bradley talked with Krieger about the challenges of implementing the DoD’s data stragegy which calls for separating data from applications. BRADLEY: I’ve reviewed the DoD’s Net-Centric Services Strategy. The promise of transformation depends on “un-isolatingâ€� systems and making information available to the populate that need it most. At the center of this promise is the idea of interoperability and data sharing. It seems the Achilles heel is data consistency. There must be thousands of different data standards in thousands of different applications in an organization as large as the DOD. How are you dealing with this? KRIEGER: In the past the DoD tried to standardize data definitions across the entire organization. This didn’t work because the DoD is a large and extremely complex enterprise. The fact that there are many different data sets is not our weakness it is our strength. Our weakness is that we build systems that are too tightly coupled to the data. To get that data into different systems we undergo to pay integrators to act it out of one system and into another. We do this as a point solution. So we end up with a bunch of point-to-point solutions. This is what we’re fixing. We’re starting to see programs build capabilities that anticipate unanticipated use by decoupling data from applications. That means data is available as a function and applications are independent of the data. Applications should be able to discover and pick the data assets they be. We can’t evaluate what local problem a 19 year-old soldier on the night alter wants to solve. But making data available as a service pushes problem solving out the edge of the network where it is needed. The data strategy gives priority to visibility accessibility and understandability over standardization. We’re more concerned about interoperability between applications without a reliance on hard-coded tightly coupled point to point interfaces between systems. The objective is for many applications to supplement the same data without forcing the developers to anticipate how the data services or applications will be leveraged. Understandability is addressed by Communities of Interest (COIs) a collaborative group of users that must exchange information in pursuit of shared goals interests missions or business processes. To do this they must have a shared vocabulary for the information exchange. The DISA Defense Information Systems Agency)Net-Centric Enterprise Services (NCES) program include security messaging and (is there missing punctuation?) content discovery enterprise services. The availability of these services means each organization does not need to create capabilities. Common services also ensure data visibility accessibility and understandability. KRIEGER: Previous approaches tried to standardize and control data structures across the DoD. The intent was interoperability via standardization. The DoD is a large enterprise with many different communities of users – warfighters intelligence community members and business users. This approach was our Achilles Heel. I think our new Achilles heel is the transformation and change required to get communities together to address information sharing challenges by agreeing on shared vocabularies and exposing and sharing data as a function. KRIEGER: Industry understands the agility and power that separating data from applications represents. Consider the Google Maps function and the explore hide application. It is based on a community vocabulary for modeling and storing geographic data called KML (keyhole markup language). By publishing data as a service in KML the Google Maps service or the explore Earth application seamlessly plots the data on a map or a globe. There are thousands of applications available on the Internet that interpret data on Google Maps (e g crime by neighborhoods home sales by zip label cheap gas by zip code and many others). There are also many websites and blogs that provide resources to back up users publish data to be consumed by Google Maps or Google Earth. KRIEGER: If you define the market as the universe of users with the DoD and related agencies then data is a market driven asset. It is a consumable. be for data drives the formation of a COI). COIs form when populate recognize they have a common information sharing problem and they must collaborate to solve the problem. All that is needed to create a COI is a willingness to stand up and work across DoD departments to alter it come about. The Federal Maritime Domain Awareness COI is a great example. Users from the Navy. Intelligence Community. Coast follow and Department of Transportation collaborated to address a maritime information sharing problem. They delivered an sign capability to address the information sharing problem in nine months. KRIEGER: Metadata or data about data. (is this a common call? Can we put into English?) makes data assets visible or discoverable. The Department of Defense Discovery Metadata Specification (DDMS) specifies how to use metadata to make data assets visible to the enterprise. It describes how developers engineers and users should advertise data assets posted to shared spaces so that others can discover them. We didn’t alter up our metadata standard. The DDMS is based on the industry Dublin core out standard and we added a security leg to it. This come moves people away from hoarding data and increases data visibility and sharing. For example the Maritime Domain Awareness Community of arouse was created when three federal (DoD. DHS and DoT) departments wanted to overlap maritime vessel tracking data. DDMS compliant discovery metadata was used to alter four large data assets visible to authorized Federal users and alter awareness maritime vessels cargo and crews. KRIEGER: It helps when the community develops the vocabulary or information exchange semantics. This helps both data consumers and producers. One-way translation from the community standard at the producer or consumer location is the only requirement. Technologies like XML easily enable data wrapping for one-way translations. Resistance is reduced because you only need to fix one side of any legacy system. This is how you can republish data from a legacy system to unanticipated users without rebuilding legacy applications.

Forex Groups - Tips on Trading

Related article:
http://benbradley.net/2007/09/13/interview-with-michael-e-krieger-director-of-information-policy-office-of-the-department-of-defense/

comments | Add comment | Report as Spam