Changes between Version 40 and Version 41 of GEC13Agenda/InstrumentationAndMeasurement


Ignore:
Timestamp:
04/04/12 11:29:10 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC13Agenda/InstrumentationAndMeasurement

    v40 v41  
    172172
    173173
    174 Summary of current status [[BR]]
    175 
     174Summary of current status  (Giridhar Manepalli): [[BR]]
     175 [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T5%29%20%20MDOD%20Status%20-%20CNRI.pptx  slides]  [[BR]]
     176
     177 Conclusions: [[BR]]
     178
     179 Good things: [[BR]]
     180  Excellent start [[BR]]
     181  Collaborative Specification    [[BR]]
     182  Great Coverage [[BR]]
     183  Nicely broken down into elements [[BR]]
     184  Mandatory vs. optional elements identified [[BR]]
     185  Genuine Use Cases:  Gathering, transferring, and sharing [[BR]]
     186
     187 Jensen's proposal (NetKarma): [[BR]]
     188  Current:  Identifiers, Descriptors, Holders [[BR]]
     189  Proposed:  Identification, Lineage/Provenance, Constraints/Security, MDO Description [[BR]]
     190
     191 Zurawski's comments: [[BR]]
     192  Too many secondary identifiers [[BR]]
     193  Descriptors should be contextualized [[BR]]
     194  Variations based on the type of object [[BR]]
     195  GENI specific descriptions should be clearly marked and separated [[BR]]
     196  Slight changes to names & enclosing elements recommended [[BR]]
     197
     198 Comments/suggestions based on metadata practices: [[BR]]
     199  Too many optional elements [[BR]]
     200   Too many choices given to users [[BR]]
     201   Users bound to take the path of least resistance [[BR]]
     202   Keep the scope restricted to only mandatory elements – at least in the beginning [[BR]]
     203   Try those out. Implement them. [[BR]]
     204  One size fits all ---- No! [[BR]]
     205   Capturing descriptions, formats, policies, transactions, etc. in a monolithic fashion [[BR]]
     206   Register individual components separately [[BR]]
     207   E.g., Capture legal formats & interpretations in their own records, and reference them here   [[BR]]
     208   E.g., Same with accepted policies [[BR]]
     209  Identifiers cannot be semantic [[BR]]
     210    Domain, sub-domain, and object-type are part of an ID [[BR]]
     211    World view changes frequently [[BR]]
     212    Non-semantic Ids are worth every penny [[BR]]
     213    Search engines & registries mask the opaqueness [[BR]]
     214    After all, IDs are just entities behind the scenes [[BR]]
     215  Object Type controlled vocabulary enumerates apples and oranges [[BR]]
     216   Collection, flow, directory, file, database, gui are not mutually exclusive [[BR]]
     217   Doesn’t help the recipient make any decision looking at the descriptor [[BR]]
     218   Bundle type & format into format interpretation method [[BR]]
     219   Covers too many corner cases, e.g., flow-rate [[BR]]
     220   Expects too many details, e.g., locator (type, access method, etc.) [[BR]]
    176221
    177222