protocol
registry_protocol
Registry specification protocol. Objects implementing this protocol should be named after the pack with a _registry suffix and saved in a file with the same name as the object.
Author: Paulo Moura
Version: 0:12:0
Date: 2022-06-28
Compilation flags:
staticDependencies:
(none)
Remarks:
(none)
Inherited public predicates:
(none)
Public predicates
name/1
Registry name. Preferably a valid unquoted atom.
Compilation flags:
staticTemplate:
name(Name)Mode and number of proofs:
name(?atom) - zero_or_onedescription/1
Registry one line description.
Compilation flags:
staticTemplate:
description(Description)Mode and number of proofs:
description(?atom) - zero_or_onehome/1
Registry home HTTPS or file URL.
Compilation flags:
staticTemplate:
home(Home)Mode and number of proofs:
home(?atom) - zero_or_oneclone/1
Registry git clone HTTPS URL (must end with the .git extension). Git repos should have the same name as the registry.
Compilation flags:
staticTemplate:
clone(URL)Mode and number of proofs:
clone(?atom) - zero_or_onearchive/1
Registry archive download HTTPS URL.
Compilation flags:
staticTemplate:
archive(URL)Mode and number of proofs:
archive(?atom) - zero_or_onenote/2
Table of notes per action.
Compilation flags:
staticTemplate:
note(Action,Note)Mode and number of proofs:
note(?atom,-atom) - zero_or_moreRemarks:
Action: Possible values are
add,update, anddelete. When unbound, the note apply to all actions.Note: Note to print when performing an action on a registry.
Protected predicates
(none)
Private predicates
(none)
Operators
(none)