Add Event to api types



> On Sep 24, 2014, at 6:23 PM, Daniel Smith <notifications@github.com> wrote:
> 
> In pkg/api/types.go:
> 
> > @@ -621,3 +613,58 @@ type ServerOpList struct {
> >  }
> >  
> >  func (*ServerOpList) IsAnAPIObject() {}
> > +
> > +// ObjectReference contains enough information to let you inspect or modify the referred object.
> > +type ObjectReference struct {
> > +	Kind            string `json:"kind,omitempty" yaml:"kind,omitempty"`
> > +	Name            string `json:"name,omitempty" yaml:"name,omitempty"`
> > +	UID             string `json:"uid,omitempty" yaml:"uid,omitempty"`
> > +	APIVersion      string `json:"apiVersion,omitempty" yaml:"apiVersion,omitempty"`
> > +	ResourceVersion uint64 `json:"resourceVersion,omitempty" yaml:"resourceVersion,omitempty"`
> > +
> > +	// Optional. If referring to a piece of an object instead of an entire object, this string
> > +	// should contain a valid field access statement. For example,
> > +	// if the object reference is to a container within a pod, this would take on a value like:
> > +	// "desiredState.manifest.containers[2]". Such statements are valid language constructs in
> Source: @smarterclayton
> 
> Also I really hate this and would happily change it if you have a better suggestion. Concrete problem: need to reference a container inside a pod.
> 
Strength of hate and basis?

Other concrete problem, when a deep complex object fails validation, don't make clients guess which field is invalid, provide an unambiguous locator.=