[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [bt-spec] BTP Issue 102 : Is entity identity modification to beallowed within BTP.
As for 102, we'd like to propose (for a post 1.0 consideration) adding
another message:
RENAME/RENAMED, whose sole responsibility is similar to REDIRECT but
replaces the identifier an actor was known about with another.
I've treated this as the basis for a proposed solution:
Proposed solution:
Defer until
after 1.0
Suggestion:
add another message
pair:
RENAME/RENAMED
whose sole responsibility is similar to REDIRECT but replaces the identifier
an actor was known about with another.
-----Original Message-----
From: BTP issues maintainer [mailto:peter.furniss@choreology.com]
Sent: 02 February 2002 19:10
To: bt-spec@lists.oasis-open.org
Subject: [bt-spec] BTP Issue 102 : Is entity identity modification to be allowed within BTP.This issue has been added to the BTP issue list
BTP Issue 102 : Is entity identity modification to be allowed within BTP.
Submitter: Mark Little, HP
Category: minor technical
Description:
In migration (as with REDIRECT), shall it be possible for the identification of the migrated entity (transaction, superior, inferior) to change, or shall it be required that the same name be retained at each endpoint address
Related issue: issue 78 : Addresses used for identification
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).
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC