This HTML5 document contains 34 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

PrefixNamespace IRI
n27http://dbkwik.webdatacommons.org/resource/fONFSTg_eHtgdvgMwXYr_w==
n7http://dbkwik.webdatacommons.org/resource/h-V7lfjohrT_oSzUzI1Yog==
n10http://dbkwik.webdatacommons.org/resource/LnuIVVaOhT9D71h6kAgHYg==
n28http://dbkwik.webdatacommons.org/resource/TGVw_48bfxR4O_s_eW_eZQ==
n9http://dbkwik.webdatacommons.org/ontology/
n25http://dbkwik.webdatacommons.org/resource/eoLIE1cT3APf-yaBN8Muhw==
n2http://dbkwik.webdatacommons.org/resource/DNdBaaacj_WBqEzeB_8Qdw==
n16http://dbkwik.webdatacommons.org/resource/jMr1Mcdir6UNjUYUsflj3w==
n37http://dbkwik.webdatacommons.org/resource/3ypdH_uRH1BPvNl3n6J1aA==
n6http://dbkwik.webdatacommons.org/resource/OFn6ILh9_H9GXYdlx4AxTQ==
n34http://dbkwik.webdatacommons.org/resource/HjsGuFuu5ELlyP3hUl4m7w==
rdfshttp://www.w3.org/2000/01/rdf-schema#
n35http://dbkwik.webdatacommons.org/resource/h_VqOMkaYnW448Z3Za3nTQ==
n5http://dbkwik.webdatacommons.org/darkscape/property/
n24http://dbkwik.webdatacommons.org/resource/SlRrh3bmR3hWhfnng_hF0Q==
n12http://dbkwik.webdatacommons.org/resource/Q9TIhoEWrUE2OeLd43gyKw==
n30http://dbkwik.webdatacommons.org/resource/IF7K0Cct7niNMGpjfn7jxg==
n15http://dbkwik.webdatacommons.org/resource/lsdbyhCvDMLwhylvMheL6Q==
n22http://dbkwik.webdatacommons.org/resource/79W_e_Wl7Ts_ezruwZJqIw==
n4http://dbkwik.webdatacommons.org/resource/5Rvh4-moMr1JYE_F5cBG5A==
n31http://dbkwik.webdatacommons.org/resource/t8YPOk6uqXIx9_mVNfg15g==
n21http://dbkwik.webdatacommons.org/resource/cHJKQu4U2wutWZ4YUTqLhQ==
n32http://dbkwik.webdatacommons.org/resource/vR-6y_FipJEYkxtzI49rqg==
n18http://dbkwik.webdatacommons.org/resource/Mte4Rk9hcStqNpC3tpB4Mg==
n26http://dbkwik.webdatacommons.org/resource/x3EvtjHFj7hRuKSSCCYX-Q==
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n14http://dbkwik.webdatacommons.org/runescape/property/
n17http://dbkwik.webdatacommons.org/resource/ml2g8EnIGW51nf7TpYLohg==
n11http://dbkwik.webdatacommons.org/resource/I0JLcxAHVduS0xUgRO8o9w==
n36http://dbkwik.webdatacommons.org/resource/m5FQLQR_KEUBeQND_SlL1A==
xsdhhttp://www.w3.org/2001/XMLSchema#
n29http://dbkwik.webdatacommons.org/resource/m5268hoCy0FopVdhvAYd7w==
n20http://dbkwik.webdatacommons.org/resource/9pIO5J4kIxT5cED_FTTcPg==
n23http://dbkwik.webdatacommons.org/resource/rC0pZ5E4NyytueLWiSgGPQ==
n3http://dbkwik.webdatacommons.org/rune-scape/property/
n33http://dbkwik.webdatacommons.org/resource/RMDtloySZN3ne4xUeq7-KA==
n13http://dbkwik.webdatacommons.org/resource/IJISC3Q7KQGcubu6gRsbkA==
n19http://dbkwik.webdatacommons.org/resource/gQ2v7hCaNNtWgoARYBznQA==
Subject Item
n2:
rdf:type
n28:
rdfs:label
Task List Task list
rdfs:comment
Based on the conference on IRC - issues were segregated into Ideas/ Concerns/ Areas of Focus/ Potential of Applications. A task list has been evolved to address the various aspects of these issue-themes. If people could sign up for the various tasks over the next few days - We could quickly arrange ourselves into smaller workgroups and roll over the work so we fill as many gaps as possible. Critt Jarvis - groups working to identify obstacles to information flow. Back to main page: Humanitarian and Relief Blogging
n34:
No
n11:
No
n30:
Doric's instructions for the task he gave you.
n10:
No
n21:
No
n16:
No
n36:
You can get another of these from Doric.
n17:
No
n31:
n32:
n26:
always
n5:wikiPageUsesTemplate
n6: n18: n27:
n3:wikiPageUsesTemplate
n4: n12: n33:
n14:wikiPageUsesTemplate
n15: n23: n37:
n25:
No
n29:
Task list
n24:
1
n22:
Yes No
n20:
0.02
n19:
What's Mine is Yours
n13:
25337
n7:
No
n35:
2012-10-17
n9:abstract
Based on the conference on IRC - issues were segregated into Ideas/ Concerns/ Areas of Focus/ Potential of Applications. A task list has been evolved to address the various aspects of these issue-themes. 1. * Create a structure of respondents and stakeholders during an active disaster/emergency relief effort/operation 2. * Identify the obstacles to information flow. Listing various types of obstacles. 3. * Examine relief response scenarios. These scenarios can be generated along various factors such as "developed/developing", "geography", "extent of damage", etc. 4. * The availability of a potential application would be achieved once the following are identified: 5. 1. * The way information IS flowing (Info Flow Currently) 6. 2. * The way information SHOULD flow (Info Flow Theoretically) 7. 3. * The way information CAN flow given the various systems in effect and their limits (Info Flow Practically) Note - Although the above might seem like too much to do in a short period of time, it was agreed it would help future development when stakeholders are are not limited by the applications and technology currently available and in use. It was also suggested that, assistance for the above be obtained from within the core coordinating group using a model based on the rotation and redistribution of tasks. If people could sign up for the various tasks over the next few days - We could quickly arrange ourselves into smaller workgroups and roll over the work so we fill as many gaps as possible. Critt Jarvis - groups working to identify obstacles to information flow. Back to main page: Humanitarian and Relief Blogging