Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Describe how to convert non-string primitives for protocols which only support strings #2343

Merged
merged 6 commits into from
Mar 3, 2022
Merged

Describe how to convert non-string primitives for protocols which only support strings #2343

Changes from 4 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
40e4830
Describe how to handle converting non-string primitives for protocols…
dashpole Feb 14, 2022
f8a6ab9
update wording to make clear that only non-string values are converte…
dashpole Feb 14, 2022
573da87
unify language
dashpole Feb 15, 2022
287e994
Update specification/common/common.md
dashpole Feb 16, 2022
04cead5
Merge branch 'main' into attribute_update
bogdandrutu Mar 3, 2022
07bfc90
Merge branch 'main' into attribute_update
bogdandrutu Mar 3, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions specification/common/common.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,9 @@ An `Attribute` is a key-value pair, which MUST have the following properties:
- The attribute value is either:
- A primitive type: string, boolean, double precision floating point (IEEE 754-1985) or signed 64 bit integer.
- An array of primitive type values. The array MUST be homogeneous,
i.e., it MUST NOT contain values of different types. For protocols that do
not natively support array values such values SHOULD be represented as JSON strings.
i.e., it MUST NOT contain values of different types.

For protocols that do not natively support non-string values, non-string values SHOULD be represented as JSON-encoded strings. For example, the expression `int64(100)` will be encoded as `100`, `float64(1.5)` will be encoded as `1.5`, and an empty array of any type will be encoded as `[]`.
dashpole marked this conversation as resolved.
Show resolved Hide resolved

Attribute values expressing a numerical value of zero, an empty string, or an
empty array are considered meaningful and MUST be stored and passed on to
Expand Down