[bt-spec] BTP Issue 14 : Minor editorials

[BTP issues maintainer <peter.furniss@choreology.com>]

This issue has been added to the BTP issue list

BTP Issue 14 : Minor editorials

Category: minor editorial
Submitter: Gordon Hamilton, AppliedTheory
Description:
Insertions shown with italics where no other changes to text
Page 12 2nd para:
"A Inferior:Superior relationship…"  ->  "An Inferior:Superior relationship…"

Page 12, Para 3, Sentence 3:
"The particular mechanisms by which a CONTEXT is "related" to application…"  ->  
"The particular mechanisms by which a CONTEXT is related to an application…"

Page 16,  Para 4, Sentence  1:
"A Superior may be Atomic or Cohesive. An Atomic Superior will apply the same decision to all of its Inferiors; a Cohesive Superior can apply confirm to some Inferiors and cancel to others, …"

Page 19 Para 4 Sentence  4:
"As the previous, but other access to the affected data if forbidden until the decision is known"  ->   
"As the previous, but other access to the affected data is forbidden until the decision is known"

Page 20 Para 4 Sentence  2:
"How the confirm-set is controlled, and when is not defined in this specification."  ->   
"How the confirm-set is controlled, and when, is not defined in this specification."
Page 20 Para 6 Sentence  3:
"If the Terminator asks the Decider to confirm the business transaction, it is the responsibility of the Decider…"

Page 20 Para last Sentence  1:
"An Decider also REQUEST_STATUS and …"  ->   
"A Decider also receives a REQUEST_STATUS and …"
Page 27 Para 2 Sentence  2nd last:
"… otherwise the Service cannot determine that is should bundle the messages together."   ->   
"… otherwise the Service cannot determine that it should bundle the messages together."

Page 27 Para 2 Sentence last:
"One-shot is thus a specialisation of one-wire."  ->   
"One-shot is thus a specialization of one-wire."  
Page 29 Para 5 Sentence last:
"The "superior type" parameter identifies whether the Superior will apply the same decision to all Inferiors enrolled with using the same superior identifier ("superior type" is "atom") or may apply different decisions ("superior type" is "cohesion")."  ->   
"The "superior type" parameter identifies whether the Superior will apply the same decision to all Inferiors enrolled by using the same superior identifier ("superior type" is "atom") or it may apply different decisions ("superior type" is "cohesion")."

Page 38 Para last Sentence 2:
"The level of isolation is a local matter (i.e. is the Inferiors choice, as constrained by the shared understanding of the application exchanges)..." 
 ->  
"The level of isolation is a local matter (i.e. it is the Inferiors choice, as constrained by the shared understanding of the application exchanges)…"
Page 50 :
"targtted."   ->   
"targeted"
Page 64 :
"An implementation receiving a *_STATE message with "reply_requested" as "true" is not required to reply immediately - it may choose to delay any reply until a decision event occurs…"

Page 66:
"The term "remaining Inferiors" are any actors to which this endpoint …"

-> "Remaining Inferiors" are any actors to which this endpoint…" OR "The term "remaining Inferiors" refers to any actors to which this endpoint…"
Page 70 Para 4 Sentence last:
"… there is no requirement to make the BTP state information more persistent that than the application information." -> "… there is no requirement to make the BTP state information more persistent that than the application information."

Page 121 Para 4 Sentence last - in glossary, Service:
"An actor which on receipt of an application messages may start an application operation which is appropriate.." -> "An actor, which on receipt of an application messages, may start an appropriate application operation."

---

To comment on this issue, please follow-up to this announcement on the bt-spec@lists.oasis-open.org (replying to this message should automatically send your message to that list).

The current draft, with line numbers is available in pdf format and word format.

To add a new issue, please email to Peter Furniss peter.furniss@choreology.com. It helps if you propose a category (technical, minor technical, editorial, minor editorial).