Update algorithms to use new processing model.

[wes-smith]

---

Preview | Diff

[TallTed]

Suggested change

	In this section we specify the algorithms required to convert JSON-LD to CBOR-LD
	and vice versa. We first provide the context processing algorithms, which are required
	for both decompression and compression, then provide the mode-specific algorithms.
	In this section, we specify the algorithms required to convert JSON-LD to CBOR-LD
	and vice versa. We provide first the context processing algorithms, which are required
	for both decompression and compression; we then provide the mode-specific algorithms.

[TallTed]

Suggested change

	that is needed to compress or decompress to/from CBOR-LD. During compression and decompression, the
	<a href="top-level-term-codec-map-generation-algorithm"></a> is run once during setup, and the
	<a href="update-term-codec-map-with-type-scoped-context-algorithm"></a> and
	<a href="update-term-codec-map-with-property-scoped-context-algorithm"></a> are run on an as-needed basis.
	that is needed to compress to or decompress from CBOR-LD. For compression and decompression, the
	<a href="top-level-term-codec-map-generation-algorithm"></a> is run once during setup, and the
	<a href="update-term-codec-map-with-type-scoped-context-algorithm"></a> and
	<a href="update-term-codec-map-with-property-scoped-context-algorithm"></a> are run on an as-needed basis.

[TallTed]

Shouldn't this be like the other algorithms, with ({datatype} {name}) or similar for each input and output?

Suggested change

	This algorithm takes a map `typeTable` and an array of JSON-LD contexts `contexts` and
	This algorithm takes a map `typeTable` and an array of JSON-LD contexts `contexts` as inputs, and

[TallTed]

Is the parenthetical meant to be read as ignoring type-scoped and property-scoped contexts? or ignoring (type) and (property-scoped contexts)? or something else? I'm guessing it's the first, which calls for the addition of this hyphen —

Suggested change

	every entry at the top level (i.e. ignoring type and property-scoped contexts).
	every entry at the top level (i.e., ignoring type- and property-scoped contexts).

[TallTed]

This sort order should be more explicit. I'm guessing it should be by codepoint value, which sometimes means we need to force a codepage or call for it to be declared (e.g., UTF-8, UTF-16, UTF-32, etc.)....

[TallTed]

Suggested change

	document to `typeTable`. If "callerProvidedTable" appears in contextTables, populate `typeTables`
	document to `typeTable`. If "callerProvidedTable" appears in `contextTables`, populate `typeTables`

[TallTed]

Suggested change

	This algorithm takes a CBOR-LD payload `cborldBytes` as input and returns
	This algorithm takes a CBOR-LD payload `cborldBytes` as input, and returns

[TallTed]

Suggested change

	If the CBOR tag on `cborldBytes` is not in the range `0x0600-0x06FF`, throw an
	ERR_NON_CBOR_LD_TAG error.
	</li>
	<li>
	Otherwise if the CBOR tag on `cborldBytes` is in the range `0x0600-0x067F`, set `registryEntryId` to
	If the CBOR tag on `cborldBytes` is not in the range `0x0600`–`0x06FF`, throw an
	`ERR_NON_CBOR_LD_TAG` error.
	</li>
	<li>
	Otherwise if the CBOR tag on `cborldBytes` is in the range `0x0600`–`0x067F`, set `registryEntryId` to

[TallTed]

Suggested change

	ERR_INVALID_VARINT_VALUE error.
	`ERR_INVALID_VARINT_VALUE` error.

[TallTed]

Suggested change

	This algorithm takes as input CBOR-LD payload `cborldBytes` and a map `typeTable` and returns a JSON-LD document.
	This algorithm takes a CBOR-LD payload `cborldBytes` and a map `typeTable` as inputs, and returns a JSON-LD document.