9e216da9ef
After go1.16, go will use module mode by default, even when the repository is checked out under GOPATH or in a one-off directory. Add go.mod, go.sum to keep this repo buildable without opting out of the module mode. > go mod init github.com/mmcgrana/gobyexample > go mod tidy > go mod vendor In module mode, the 'vendor' directory is special and its contents will be actively maintained by the go command. pygments aren't the dependency the go will know about, so it will delete the contents from vendor directory. Move it to `third_party` directory now. And, vendor the blackfriday package. Note: the tutorial contents are not affected by the change in go1.16 because all the examples in this tutorial ask users to run the go command with the explicit list of files to be compiled (e.g. `go run hello-world.go` or `go build command-line-arguments.go`). When the source list is provided, the go command does not have to compute the build list and whether it's running in GOPATH mode or module mode becomes irrelevant.
33 lines
936 B
Plaintext
33 lines
936 B
Plaintext
--
|
|
-- Example fragment of an openEHR Archetype, written in cADL, a subsyntax of the Archetype Definition Language (ADL)
|
|
-- definition available here: http://www.openehr.org/releases/trunk/architecture/am/adl2.pdf
|
|
-- Author: Thomas Beale
|
|
--
|
|
|
|
EVALUATION[id1] matches { -- Adverse Reaction
|
|
data matches {
|
|
ITEM_TREE[id2] matches {
|
|
items cardinality matches {1..*; unordered} matches {
|
|
ELEMENT[id3] matches { -- Substance/Agent
|
|
value matches {
|
|
DV_TEXT[id51]
|
|
}
|
|
}
|
|
ELEMENT[id50] occurrences matches {0..1} matches { -- Future Use
|
|
value matches {
|
|
DV_TEXT[id53]
|
|
}
|
|
}
|
|
CLUSTER[id10] matches { -- Reaction Event
|
|
items matches {
|
|
allow_archetype CLUSTER[id30] matches { -- Additional Reaction Detail
|
|
include
|
|
archetype_id/value matches {/openEHR-EHR-CLUSTER\.anatomical_location(-a-zA-Z0-9_]+)*\.v1/}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|