As the presentation emphasises, the model described there is a preliminary version, and I'm fairly sure there will be further modifications/enhancements/refinements required as it is tested against some examples and use cases, but I was pleased that the meeting made a commitment to aligning the ORE work firmly with the principles described in the W3C's Architecture of the World Wide Web document.
On a related (well, slightly related!) note, also published in the last few days was the programme for a W3C workshop titled "Web of Services for Enterprise Computing: Can the Web fulfill industry and business requirements?" Although I haven't had time to read them all, the set of position papers (linked from the programme) look like interesting reading. The paper by Noah Mendelsohn on behalf of the W3C Technical Architecture Group walks through a use case from the perspectives of the Web Architecture and of Web Services; and the paper by Nick Gall of Gartner has attracted some attention for its firm conclusion:
It is my position that the W3C should extricate itself from further direct work on SOAP, WDSL, or any other WS-* specifications and redirect its resources into evangelizing and standardizing identifiers, formats, and protocols that exemplify Web architectural principles. This includes educating enterprise application architects how to design "applications" that are "native" web applications.