<- Go to ProcessActions  ->

1 Definition 2 Protocol 3 Syntax 4 Semantics

1 Definition

The Action of a User requesting that Location Service:

  1. Move an MU-Added R-Item from a Point of View to another Point of View via a Trajectory.
  2. Grant Rights to the MU-Moved R-Item based on requested Rights.

If the request is  accepted, the Export Service moves the R-Item to the new U-Location with the assigned Spatial Attitude via a Trajectory and grants the requested Rights to the R-Item.

Note: the U-Location client of the Export Service converts the original and destination Spatial Attitudes, and the Trajectory into a Stream that moves the R-Item to the destination U-Location. If no Trajectory is provided, the Export-Import Service or the R-Item organise the movement from the source to the destination U-Location.

2 Protocol

  1. User sends “MU-Move PA Request including R-Item, Point of View1, Point of View2, U-Location, and Rights (Status=Model)” to MU-Move Service.
    1. If MU-Move Service is a free service, goto MU-Move.
    2. If MU-Move Service is a pay service:
      1. User sends “MU-Move PA Request including Service Pricing Model (Status=Model)” to MU-Move Service.
      2. MU-Move Service sends “MU-Move PA Response” to User:
        1. If “MU-Move PA Response includes Status=Err”, goto End
        2. If “MU-Move PA Response includes Status=Ack and Service Pricing Model with Transaction (both Status=Model)”, User
          1. Transacts “Value included in Transaction”.
          2. Sends “MU-Move PA Request including Service Pricing Model (Status=Model) with Transaction (both Status=Final)” to MU-Move Service.
  2. MU-Move: MU-Move Service:
    1. MM-Moves “R-Item”.
    2. Sends “MU-Move PA Response” including
      1. “Rights (Status=Final)” to MU-Moved R-Item.
      2. “Service Pricing Model (both Status=Final)”, if MU-Move is a pay service.
  3. End.

The protocol described using Workflow Description Language (WDL) is available at this link:

https://schemas.mpai.community/MMM4/V2.2/wdl/MUMovePA.wdl

3 Syntax

The structure of the input and output messages, using JavaScript Object Notation (JSON)  is available at this link:

https://schemas.mpai.community/MMM4/V2.2/actions/MUMovePA.json

4 Semantics

Label Description
Header MU-Move Process Action Header – Standard “MMM-3MP-Vx.y”
MInstanceID Identifier of M-Instance.
UEnvironmentID Identifier of U-Environment.
MUMovePAID Identifier of this PA Instance.
MUMovePATime Creation time of this PA Instance.
MUMovePAData Data included in this PA Instance.
– Time Time of PA Request emission and Time of PA Request execution, or PA Response emission.
– RQ-Complements Complements in the PA Request.
  – Nil RItemID R-Item to be MU-Moved.
  – From Point of View U-Location where the Item is MU-Added.
  – To Point of View M-Location where the Item is to be MU-Moved.
  – With U-Location The Trajectory to be used to move the R-Item.
  – With Rights Requested Rights to the MU-Moved Item.
  – With SPM Service Pricing Model, if MU-Move is a pay service.
– D-Complements Complements in the PA Response.
  – With Rights Rights based on requested Rights, if PA Request is accepted.
  – With SPM Service Pricing Model, if MU-Move is a pay service.
 – With PAStatus Status of PA Request.
    – Ack If PA Request could be performed
    – Err If Error was found
      – Clash R-Item clashes with another R-Item.
      – FaultyPA Faulty PA Request.
      – IncID Incorrect ID.
      – ULocOOR M-Location out of range.
      – InsRights Insufficient Rights.
      – InsValue Insufficient Value in Wallet.
DataXMData Identity, provenance, authorised usage, source, type, governance context, security, legality, and annotation of exchanged data.
 DescMetadata Descriptive Metadata.

<- Go to ProcessActions  ->