@@ -169,13 +169,13 @@ <h2>Motivation and Background</h2>
169169 </ p >
170170
171171 < p >
172- For a number of application areas the size of JSON-LD content is an obstacle. Size constraints may occur
173- when storing data as a QR or in a barcode, transmitting data over low bandwidth channels, or when relying
174- on high volume data storages . These problems are not only significant for existing applications but are also
175- obstacles for enabling new application areas (e.g., in embedded systems). CBOR-LD, based on
176- < a href ="https://cbor.io/spec.html "> CBOR</ a > (which has a large user and tool base already ), can exploit
177- the linked data features of JSON-LD, and provide a high level, and easily reversible compression of
178- JSON-LD data. The work on CBOR-LD has already begun in the < a href ="https://www.w3.org/community/json-ld/ "> JSON
172+ For a number of application areas, the size of JSON-LD content is an obstacle. Size constraints may be
173+ encountered when storing data as a QR or in a barcode, transmitting data over low bandwidth channels, or when relying
174+ on high volume data storage . These constraints are not only significant for existing applications, but are also
175+ obstacles when enabling new application areas (e.g., in embedded systems). CBOR-LD, based on
176+ < a href ="https://cbor.io/spec.html "> CBOR</ a > (which already has a large user and tool base), can exploit
177+ the linked data features of JSON-LD, and provide a high level and easily reversible compression of
178+ JSON-LD data. Work on CBOR-LD has begun in the < a href ="https://www.w3.org/community/json-ld/ "> JSON
179179 for Linking Data Community Group</ a > , and will be finalized by the JSON-LD Working Group.
180180 </ p >
181181
0 commit comments