Attendees:
Discussion: - Events
- Nader: Says can change so payload name need not match event-name
- Needs to fetch the definition to determine how to de-serialize
- OK with it as long as its not part of the standard
- Discussion of attributes such as "class" which should be ignored by non-aware implementations
- Nader - Should not have implementation specific details
- Should use a complex-type
- Nate & Kevin - Its our schema we can define whatever we want.
- Complex-types change the type so its not appropriate
- We will accept events without the attribute set
- Nate: We should clarify which elements and attributes are our extensions
- Nate: When the event type is in the xsd namespace: then the value of the payload is the root element's content. All attributes and other elements should be considered meta-data and MAY be ignored.
- Nader: Adding an attribute makes it no-longer a string, despite its declaration
- Will investigate
- InitCookie:
- Two current implementations:
- Consumer creates new a session on login
- Consumer uses the same session after logging in
- Nader & Nate: The initCookie call is tied to the consumer's session and the consumer is responsible for determining when do this.
- Nate: Create an errata stating:
- The producer SHOULD NOT require a new session for new users, but the consumer MAY choose to do so. The producer MAY invalidate and throw an appropriate fault at is choosing.
|