You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

The objective of notice management is to reduce the number of interactions (‘clicks’ and other ‘interruptions’) users face in order to achieve their actual desired objectives, both on first use and on subsequent use of the same services in a similar workflow. As proposed in AARC-G083, Guidance for Notice Management by Proxies:

All notice presenters (proxies, communities, and service and data providers) SHOULD provide machine-readable identifiers and associated registry meta-data for the notices they can present to users.

Ideally Research Infrastructures should converge on the same policies, but that is often not feasible due to internal requirements (e.g. geographical, risk-tolerance etc.) In this case, a meta-data structure is proposed to clarify which additional policies are augmented by a policy, or included within it. 

What are these "Notifications"?

Concretely, the notifications that impact usability are acceptance of Acceptable Use Policies and Privacy Notices. 

What does notification meta-data look like? 

{
    "policy": {
        "augments_policy_uris": ["https://documents.egi.eu/document/2623"],
        "aut": "https://cern.ch",
        "aut_name": "CERN",
        "aut_name#dk_DK": "CERN",
        "contacts": [{
            "email": "notSupicious@mikrosoft.xyz",
            "type": "standard"
        }],
        "description": "A research community beyond suspicion.",
        "description#dk_DK": "Et trovaerdigt forsknings institut.",
        "id": "https://another-community.org",
        "includes_policy_uris": ["https://some-community.org", "https://wise-community.org/wise-baseline-aup/v1/"],
        "notice_refresh_period": null,
        "policy_class": "sla",
        "policy_url": "https://another-community.org",
        "ttl": 31104300,
        "valid_from": "2019-06-10T23:59:59Z"
    }
}

Resources

  • No labels