[Prev]

2.12.1 SOL1 Query String Attributes

urn:tas3:sol:vers

Identifies the version of SOL. Always "1" for SOL1.

urn:tas3:sol1

Special value reserved to be used as ObligationId or in general to identify this dialect of SOL.

urn:tas3:sol1:pledge

Special value reserved to be used as AttributeId

urn:tas3:sol1:require

Special value reserved to be used as AttributeId

urn:tas3:sol1:use

How information can or will be used and shared. A comma separated list of enumerators in the order of principally intended use (ordered here, in our opinion, from least aggressive to more aggressive as indicated; however this ordering is subjective and other opinions may exist). The urn:tas3:sol1:use:purpose should be favoured over urn:tas3:sol1:use, unless the vague meaning of urn:tas3:sol1:use is desired.

urn:tas3:sol1:use:transaction (0)

Information will only be used for the transaction for which it was collected

urn:tas3:sol1:use:session (1)

Information will only be used within the current session

urn:tas3:sol1:use:user (2)

Information can be used in the user's other sessions in the same app

urn:tas3:sol1:use:forpurpose (3)

Information will be used only for the purpose it was collected, in abstract. This usage is discouraged. Instead the specific purpose should be specified using format

          urn:tas3:sol1:use:purpose=business-process-model-id; or
          urn:tas3:sol1:use:purpose=business-process-instance-id

These two forms allow the obligation to be tied into the model in abstract, or to the specific business process instance in particular, e.g. for exceptional processing such as Break-the-Glass.

urn:tas3:sol1:use:serveranon (4)

Information can be used by other processes on same server as long as user is not explicitly identified

urn:tas3:sol1:use:serverident (5)

Information can be used by other processes on same server (user may be identified)

urn:tas3:sol1:use:appanon (6)

Information can be used by the application towards other purposes as long as the user is not explicitly identified

urn:tas3:sol1:use:appident (7)

Information can be used by the application towards other purposes (user may be identified)

urn:tas3:sol1:use:organon (8)

Information can be used by the organization for other nonmarketing purposes as long as the user is not explicitly identified

urn:tas3:sol1:use:orgident (9)

Information can be used by the organization for other nonmarketing purposes (user may be identified)

urn:tas3:sol1:use:mktanon (10)

Information can be used by the organization for marketing purposes as long as the user is not explicitly identified

urn:tas3:sol1:use:mktident (11)

Information can be used by the organization for marketing purposes (user may be identified)

urn:tas3:sol1:use:grpanon (12)

Information can be used within the business group for other nonmarketing purposes as long as the user is not explicitly identified

urn:tas3:sol1:use:grpident (13)

Information can be used within the business group for other nonmarketing purposes (user may be identified)

urn:tas3:sol1:use:grpmktanon (14)

Information can be used within the business group for marketing purposes as long as user is not explicitly identified

urn:tas3:sol1:use:grpmktident (15)

Information can be used within the business group for marketing purposes (user may be identified)

urn:tas3:sol1:use:shareanon (16)

Information can be shared with anyone for other nonmarketing purposes as long as the user is not explicitly identified

urn:tas3:sol1:use:shareident (17)

Information can be shared with anyone for other nonmarketing purposes (user may be identified)

urn:tas3:sol1:use:sharemktanon (18)

Information can be shared with anyone for marketing purposes as long as user is not explicitly identified

urn:tas3:sol1:use:sharemktident (19)

Information can be shared with anyone for marketing purposes (user may be identified)

urn:tas3:sol1:use:anyall (20)

Information can be used for any and all purposes without restriction.

urn:tas3:sol1:use:purpose

Specific business process that is allowed to use the data. This can be specified either as abstract business-process-model-id or as business-process-instance-id. For example:

      urn:tas3:sol1:use:purpose=business-process-model-id; or
      urn:tas3:sol1:use:purpose=business-process-instance-id

These two forms allow the obligation to be tied into the model in abstract, or to the specific business process instance in particular, e.g. for exceptional processing such as Break-the-Glass.

urn:tas3:sol1:delon

Delete data on as Unix seconds since epoch. This obligation effectively allows control of data retention, but instead of being expressed in relative terms, it is expressed in absolute terms that are legally easier to interpret.

urn:tas3:sol1:retention

Maximum data retention period as Unix seconds. This obligation is meant for database storage. Upon act of data access, retention should be converted to delon using current wall clock time.

urn:tas3:sol1:certdel

Certify deletion by legally binding report to the audit bus.

urn:tas3:sol1:preauth

Before each use of the data, user's explicit consent - preauthorization - has to be obtained. Value specifies where to obtain preauthorization.

urn:tas3:sol1:callback

When about to use data, call back to the user for opportunity to modify the data, or deny it. Value specifies where to call back.

urn:tas3:sol1:repouse

Report use to the audit bus. Comma separated list of enumerators:

urn:tas3:sol1:repouse:never

No need to report use (seldom appears)

urn:tas3:sol1:repouse:all

Report any and all use

urn:tas3:sol1:repouse:oper

Report operational use, but not statistical or administrative use.

urn:tas3:sol1:repouse:stat:immed

Report use in near real time. for day need to be reported, if there was any use.

urn:tas3:sol1:repouse:stat:daily

No need to report individual use, but summary statistics for day need to be reported, if there was any use.

urn:tas3:sol1:repouse:stat:weekly

No need to report individual use, but summary statistics for week need to be reported, if there was any use.

urn:tas3:sol1:repouse:stat:monthly

No need to report individual use, but summary statistics for month need to be reported, if there was any use.

urn:tas3:sol1:repouse:stat:quarterly

No need to report individual use, but summary statistics for quarter (last 3 months) need to be reported, if there was any use.

urn:tas3:sol1:repouse:stat:semestral

No need to report individual use, but summary statistics for semester (last 6 months) need to be reported, if there was any use.

urn:tas3:sol1:repouse:stat:yearly

No need to report individual use, but summary statistics for year need to be reported, if there was any use.

If no urn:tas3:sol1:repouse:stat is specified, default is urn:tas3:sol1:repouse:stat:immed.

If conflicting enumerators are specified, the most strict one applies.

urn:tas3:sol1:xborder

Enumerator describing what sort of cross border data sharing can occur:

urn:tas3:sol1:xdom:eu

Only within EU common market.

urn:tas3:sol1:xdom:safeharbour

Common market and safe harbour participants

urn:tas3:sol1:license

Use of information is subject to license specified in the value part. The value part should be either URL to online accessible license text, or it should be a URN pointing to a well known license.

The general assumption is that the license terms are either well known to the system (and programmed in) or machine readable. While the user may have to consent to the license at some level, it is not meant that this license reference be displayed to user and he required to read and consent on the spot.

urn:tas3:sol1:contract-fwk

Framework or governance contract identifier.

urn:tas3:sol1:contract

Contract identifier.

urn:tas3:sol1:contract-sub

Subcontract or amendment identifier

urn:tas3:sol1:contract-part

Part, exhibit, annex, or clause identifier.


[Prev | Next]