I was not intending to assert that we need additional text; I just wanted to be sure that it did not get lost entirely. I was intending to crawl through 2.1 last weekend but fate intervened. Since we describe the template usage pattern ... which I continue to believe is a "higher level pattern" than HTTP message flows, i.e. it's a "how a resource is used at the application level" pattern ... in Automation, that's fine. We don't talk about rdf:type or the HTTP in RDF vocabulary in Core Actions either, we just use them, the template usage pattern seems no different to me.
Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario Martin P Pain <[email protected]> wrote on 02/04/2014 06:23:05 AM: > From: Martin P Pain <[email protected]> > To: Martin P Pain <[email protected]>, > Cc: John Arwe/Poughkeepsie/IBM@IBMUS, oslc-automation@open- > services.net, Oslc-Automation <[email protected]> > Date: 02/04/2014 06:23 AM > Subject: Re: [Oslc-Automation] OSLC Actions: Action for resource > that does not yet exist: worked example > > > > 2: I don't see text allowing them to be cleaned up "quickly", which > > > I thought we had in here already. > > > > It's in the template dialog part of the Auto spec [1]: > > "The resource MAY be temporary and the consumer SHOULD get it within > > a limited period of time (at least 15 minutes) " > > We don't seem to have any normative text for templates in the Core > Actions spec at all. So we could put non-normaitve text in the > current section on templates, or add a new normative section, but > otherwise each use of templates in interaction patterns, etc, would > have to state it separately. > > Martin > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with > number 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
