This is a "how to read this eye chart" issue. Might be that the heading needs work (better), or that the table text needs tweaking for clarity (ok), I have not looked in context since no URL was provided and I can't dig where I am right now ;-) I think the _intended reading_ would be: "The [origin = OSLC Core] spec says 'If you support partial resource representations, then [meaning =...MUST...]'. The OSLC spec says that providers SHOULD support partial representations." So the MUST only becomes active if you satisfy the SHOULD. If you fail to satisfy the SHOULD, Automation still likes you and the rest is irrelevant for you.
It's structurally like saying (although the Automation construction is readable other ways IMO): IF you're flying a plane, you MUST have a pilot's license. Which says nothing about the vast majority of us who never fly (pilot) a plane. Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario From: Joe Ross/Austin/IBM@IBMUS To: [email protected] Date: 09/13/2012 08:14 PM Subject: Re: [Oslc-Automation] OSLC Automation spec updates Sent by: [email protected] Although support for oslc.properties has been relaxed to "SHOULD". I notice that the meaning still says "MUST". I assume that it should be "SHOULD" in both places: Requirement: Partial Resource Representations Level: SHOULD Origin: Core Meaning: OSLC service providers MUST support HTTP GET requests for retrieval of a subset of a resource’s properties via the oslc.properties URL parameter ================================================ Joe Ross/Austin/IBM, [email protected] Tivoli Autonomic Computing & Component Technologies 512-286-8311, T/L 363-8311_______________________________________________ Oslc-Automation mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
