I just noticed that the current draft of the automation spec says the following: ------------------------------------------------------------------------------------------------------------------ OSLC service providers MUST support HTTP GET requests for retrieval of a subset of a resource's properties via the oslc.properties URL parameter ------------------------------------------------------------------------------------------------------------------
Our request/response payloads have a small number of properties and it doesn't make any sense for us to implement support for oslc.properties. I really think that this requirement should be relaxed to "SHOULD" or "MAY". Is there any reason why this has to be "MUST"? Can this be changed before the spec is finalized? ================================================ Joe Ross/Austin/IBM, [email protected] Tivoli Autonomic Computing & Component Technologies 512-286-8311, T/L 363-8311
