1296days since
Demo Capture

Recent site activity

May 10 Telecon

posted May 7, 2010, 11:23 AM by Joshua Lieberman   [ updated May 10, 2010, 8:12 AM ]
Agenda:

1) Scenario development methodology, particularly the "meta" part - how to design user requirements analysis, how to incorporate testing, how to manage vocabularies.

2) What are the 19115 elements which can be used to describe the relationships we discussed last week (data - service, service - client, data - societal benefit)?

3) Where are we with development of the GEOSS Common Record wrt queryables versus returnables, publication, federated update?

4) Processing Use Case

TIme: 10am EDT / 14h00 UTC / 16h00 CET

Logistics:

Site: http://sites.google.com/a/aip3.ogcnetwork.net/home/home/end2engineering-2/e2e-telecons/may10telecon
Local time: http://timeanddate.com/worldclock/fixedtime.html?month=5&day=10&year=2010&hour=14&min=0&sec=0&p1=0
Dimdim & Telecon Info: http://my.dimdim.com/joshlieberman

Attending:


Josh Lieberman, Lionel Menard, Steve Browdy, George Percivall

Topics:


1) Scenario development methodology, particularly the "meta" part - how to design user requirements analysis, how to incorporate testing, how to manage vocabularies.

Discussion:
  • (Browdy): What is the division of labor between UIC and AIP-3?
  • (Lieberman): UIC is longer term "menu", AIP is developing "choices". In practice, AIP-3 user analysis needs to feed back into UIC process.
  • (Menard): Energy has the same users in AIP-3 as in AIP-2
  • (Lieberman): Meta-scenario involves reconsideration of users to see if there are unexpected uses and types of users discovering / utilizing the scenario resources.
  • (Menard): This is already happening in Energy, that there are users interested in skin cancer risk as well as PV potential.
  • (Browdy): User meta-scenario advice should include the UIC interaction
  • (Lieberman): Should include both feedback path to UIC and feedback / stats from portal / clearinghouses on interests of users discovering / utilizing resources.
  • (Menard): What role should the UIC survey (usability testing) play here? Drawing from experience of other SBA's for example. Particularly for new participants and scenario developers in AIP-3
  • (Lieberman / Browdy): Should we advise to incorporate a smaller survey into each scenario?
  • (Menard): Also interest in population density services for various purposes.
  • (Percivall): Should build on both the developing UIC user (consumer so far) taxonomy and the (4?) actors described in the CFP. For example, subtyping the four actor types (User, Provider, Integrator, GCI Operator).
  • (Lieberman): Do we need another term for the building blocks of scenarios?
  • (Percivall): For some events in scenarios, their templates may be other types of building blocks, but still can be described as events.
  • (Menard): Energy has used more specialized terms for its scenario actors. More detailed for users than for providers. Need to add these to the overall actor taxonomy. Other suggestions: add Community Catalog Provider (Librarian?) type.
  • (Percivall): Further important community resource providers, e.g. community portal provider.



2) What are the 19115 elements which can be used to describe the relationships we discussed last week (data - service, service - client, data - societal benefit)?


3) Where are we with development of the GEOSS Common Record wrt queryables versus returnables, publication, federated update?
  • (Browdy): Active topic of inquiry by SIF: broadest set of fields which make sense to adopt as basis of "GEOSS-friendly" registration.
  • (Menard): Data quality elements in GEOSS metadata, particularly propagated through services. Hot topic for Energy!
  • (Lieberman): Application-specific quality is often the critical property, e.g. as expert recommendations.


4) Processing Use Case
  • Postponed until next week

Actions:

  • Look at UIC usability testing questions to see if we can build a user survey use case for scenario incorporation.
  • Add actors to the "engineering use case components" for scenario development specialization. Document an emerging actor taxonomy and which specializations are recommended to incorporate.
  • Develop ownership of use cases and components for update / creation in AIP-3. E.g. semantics use cases for AIP-3
  • Port over the use case summaries from AIP-2 and connect to the table in the AIP-3 home page.

Next meeting:

  • May 17



Comments