Kurt Kavanaugh wrote:
Thanks for the replies. Understood. Methinks the place to start is the spec as indicated.
As any technology comes to maturity and usage patterns emerge specifications should be updated to incorporate new or modified elements of functionality. API's should ultimately be written not to serve the spec in an inwardly looking fashion but outwardly to those who use them.
I stick to my guns that it would be more intuitive to incorporate this kind of meta data in the Resource and not in the content. Few want their data modified by a persistence layer.
Kurt,
Do you have any specific suggestions, proposed changes to the resource classes, etc? If yes, you can create bugzilla entry and describe it here. It's easier to track RFEs through bugzilla than keep them in the mail archive, especially in this case, when many folks agree with your suggestion.
Vadim
