Changes between Version 14 and Version 15 of TemporallyExtendedAttributes


Ignore:
Timestamp:
11/01/12 09:50:24 (7 years ago)
Author:
skyebend
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TemporallyExtendedAttributes

    v14 v15  
    134134 
    135135=== Questions === 
    136 Spec says get methods should return TEA value and spell list.  Skye thinks we should have a parameter "return.tea=FALSE" which would return this.  Otherwise return single matching value if one found, or the first (earliest) value matching query and throw Warning if multiple values match. I think this will cover the most common use cases better.  ADDED TO SPEC 
     136Spec says get methods should return TEA value and spell list.  Skye thinks we should have a parameter "return.tea=FALSE" which would return this.  Otherwise return single matching value if one found, or the first (earliest) value matching query and throw Warning if multiple values match. I think this will cover the most common use cases better.  ADDED TO SPEC, IMPLEMENTED 
    137137 
    138138Since spell structures forces non-overlapping, should we add an "earliest" and "latest" rule, and if it is set don't throw warning for multiple TEA match within query spell? 
     
    144144What should behavior be for activating attributes on edges that do not exist, or networks with no edge? throw error? 
    145145 
    146 In a get method, if TEA attribute is present but not active at time point (or missing for that vertex or edge) and dynamic.only=FALSE, should it consider matching non-TEA? 
     146In a get method, if TEA attribute is present but not active at time point (or missing for that vertex or edge) and dynamic.only=FALSE, should it consider matching non-TEA? (Might return object with unexpected structure if return.tea=TRUE) 
    147147 
    148 If we are returning a TEA structure, it doesn't make sense to "fall through" to non-TEA attributes, since they won't have TEA structure.  Proposing to set dynamic.only=TRUE if return.tea=TRUE 
     148If we are returning a TEA structure, it doesn't make sense to "fall through" to non-TEA attributes, since they won't have TEA structure.  Proposing to set dynamic.only=TRUE if return.tea=TRUE . IMPLEMENTED 
     149 
     150Should we add "v" and "e" params to get methods to allow fetching from a subset of vertices and edges? Doesn't seem like it would add much complexity. 
    149151   
    150152