4. Data Staging & Activity Credential Revision * FileStaging element in JSDL optional - we may Fault if present or silently ignore
The correct "JSDL way" of handling something is to throw a fault (with meaning "I don't/won't do that") if a unsupported feature is used.
Yeah. But the JSDL model having xsd:any everywhere makes it tricky for implementers to define what is explicitly out of bounds.
* Define a list of minimally supported authentication tokens and protocols that an implementation MUST support (e.g. username/password and ftp, others...)
I'd be a bit concerned about requiring support for a specific token type/protocol. Recommending is OK though, and requiring some mechanism for discovery of what is supported would be good.
To get interoperability we need a minimal core supportable set. People can (& will) go beyond that - that's fine. Steven