Ted Thibodeau Jr

[`20-Dec-23`](https://github.com/w3c/vc-jose-cose/issues/160#issuecomment-1866602543) -> `20-Dec-2023`

Both our text and IETF's should include mention of where the least-significant and/or most-significant bit is (leftmost or rightmost), similar to what NIST has (regrettably, different text in different docs)...

[Is most significant bit left-most or right-most](https://github.com/w3c/vc-bitstring-status-list/issues/93#issuecomment-1894631772)?

@ericprud -- Please edit your https://github.com/json-ld/yaml-ld/issues/19#issuecomment-1179545426 to put a code fence around `@context` so that GitHub user doesn't get pinged every time this issue is updated.

@ioggstream -- I realize this may seem like a quibble, but please note that while the name `RDF*` was used in early drafts and discussion, it was changed to `RDF-star`...

@rob-metalinkage -- Please edit your last comment, https://github.com/json-ld/yaml-ld/issues/17#issuecomment-1207728874, to put `@context` into a code fence (like ``` `@context` ```), so that GitHub user doesn't get endlessly pinged on threads about...

@gkellogg -- Several unfenced `@` entities are in the last several lines of the bot-posted conversation https://github.com/json-ld/yaml-ld/issues/17#issuecomment-1263840815 causing more unintended alerts to be fired in their direction.... Maybe the bot...

Yeah, I'm sure they were unfenced on IRC. There's no consistent value to fencing there. Weirdly, now that they're single-backtick fenced here, those backticks are showing as part of the...

I'd suggest wrapping the larger element including the `@`, so `{"@id": "someone"}`, which makes overall sense anyway, the larger element *being* code.

Regarding media types with multiple plus signs, see Draft RFC [Media Types with Multiple Suffixes](https://datatracker.ietf.org/doc/draft-ietf-mediaman-suffixes/). They're not yet officially permitted nor sanctioned by IANA nor IETF, but at least [one...