Changes between Version 38 and Version 39 of GEC14Agenda/IMDesignTopics


Ignore:
Timestamp:
07/06/12 15:58:52 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC14Agenda/IMDesignTopics

    v38 v39  
    196196
    197197Summary  [[BR]]
    198  * Current v0.1 design [http://groups.geni.net/geni/wiki/GEC11InstMeasWorkingSession#a2MeasurementDataObjectDescriptorMDOD  references]  [[BR]]
     198 * Current v0.2 design [http://groups.geni.net/geni/wiki/GEC11InstMeasWorkingSession#a2MeasurementDataObjectDescriptorMDOD  references]  [[BR]]
    199199 * [http://groups.geni.net/geni/wiki/InstMeasTopic_4.5DescriptorsObjectsRegistriesLookupService  status at GEC13]  [[BR]]
    200  * v0.1 design reviewed at GEC13    [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T5%29%20%20MDOD%20Status%20-%20CNRI.pptx  slides] (Giridhar Manepalli)  Conclusion:  too complex  [[BR]]
     200 * v0.2 design reviewed at GEC13   
     201
     202Summary of current status  (Giridhar Manepalli): [[BR]]
     203 [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T5%29%20%20MDOD%20Status%20-%20CNRI.pptx  slides]  [[BR]]
     204
     205 Conclusions: [[BR]]
     206
     207 Good things: [[BR]]
     208  Excellent start [[BR]]
     209  Collaborative Specification    [[BR]]
     210  Great Coverage [[BR]]
     211  Nicely broken down into elements [[BR]]
     212  Mandatory vs. optional elements identified [[BR]]
     213  Genuine Use Cases:  Gathering, transferring, and sharing [[BR]]
     214
     215 Jensen's proposal (NetKarma): [[BR]]
     216  Current:  Identifiers, Descriptors, Holders [[BR]]
     217  Proposed:  Identification, Lineage/Provenance, Constraints/Security, MDO Description [[BR]]
     218
     219 Zurawski's comments: [[BR]]
     220  Too many secondary identifiers [[BR]]
     221  Descriptors should be contextualized [[BR]]
     222  Variations based on the type of object [[BR]]
     223  GENI specific descriptions should be clearly marked and separated [[BR]]
     224  Slight changes to names & enclosing elements recommended [[BR]]
     225
     226 Comments/suggestions based on metadata practices: [[BR]]
     227  Too many optional elements [[BR]]
     228   Too many choices given to users [[BR]]
     229   Users bound to take the path of least resistance [[BR]]
     230   Keep the scope restricted to only mandatory elements – at least in the beginning [[BR]]
     231   Try those out. Implement them. [[BR]]
     232  One size fits all ---- No! [[BR]]
     233   Capturing descriptions, formats, policies, transactions, etc. in a monolithic fashion [[BR]]
     234   Register individual components separately [[BR]]
     235   E.g., Capture legal formats & interpretations in their own records, and reference them here   [[BR]]
     236   E.g., Same with accepted policies [[BR]]
     237  Identifiers cannot be semantic [[BR]]
     238    Domain, sub-domain, and object-type are part of an ID [[BR]]
     239    World view changes frequently [[BR]]
     240    Non-semantic Ids are worth every penny [[BR]]
     241    Search engines & registries mask the opaqueness [[BR]]
     242    After all, IDs are just entities behind the scenes [[BR]]
     243  Object Type controlled vocabulary enumerates apples and oranges [[BR]]
     244   Collection, flow, directory, file, database, gui are not mutually exclusive [[BR]]
     245   Doesn’t help the recipient make any decision looking at the descriptor [[BR]]
     246   Bundle type & format into format interpretation method [[BR]]
     247   Covers too many corner cases, e.g., flow-rate [[BR]]
     248   Expects too many details, e.g., locator (type, access method, etc.) [[BR]]
     249
    201250
    202251
    203252Tasks  [[BR]]
    204  * Need to DRAFT simplified v0.2 MDOD schema, for XML file;  then review and finalize. (who can help?) [[BR]] 
    205  * Want to extend MDOD to cover all types of objects, i.e., software images.  [[BR]]
    206  * Want to extend MDOD schema to define Event Record schema. [[BR]]
     253 * Need to DRAFT simplified v0.4 MDOD schema, for XML file;  then review and finalize. (who can help?) [[BR]] 
     254 * Optional: extend MDOD to cover all types of objects, i.e., software images.  [[BR]]
     255 * Optional: extend MDOD schema to define Event Record schema. [[BR]]
    207256 * Do we need MDOD registry?  Include in iRODS? [[BR]]
    208257 * Need MDOD creation and editing service. [[BR]]