AdCOM 1.0 JSON Schema Unofficial

Decision records ·

D-009 List: IP Location Services gives standard codes 511 and 512 to 51Degrees, inside the range other lists reserve for vendors. Are they core terms?

Gap Cited on main and at the tag AdCOM1.0-202607.

What the schemas do

Core terms: 511 and 512 are codes the list names, and the list reserves no vendor range, so its vocabulary is closed.

Options

  • core-terms Chosen

    Core terms: 511 and 512 are codes the list names, and the list reserves no vendor range, so its vocabulary is closed.

  • vendor-codes

    Vendors' codes, since they are at least 500.

Why

The list writes no 500+ row, so it reserves no vendor range, and 511 and 512 are two of its codes like 1 to 4. Their place in the numbering is surprising, since other lists reserve 500 and up for vendors, but the table settles what they are.

What we ask the specification to state

Number standard codes below 500, as every other list does, or say that IP Location Services reserves no vendor range and that 511 and 512 are standard codes. An exchange that already uses 511 or 512 as private codes on another list's pattern now collides with a standard one.

The specification lines it rests on

Each line is quoted as the record pins it. Expand an item to read the quote.

main

  • List: IP Location Services, the row of 511 L3815 at 26c59ba
    511 | 51Degrees (High Confidence)
  • List: IP Location Services, the row of 512 L3819 at 26c59ba
    512 | 51Degrees (Medium Confidence)
  • List: IP Location Services, the row of 1 L3799 at 26c59ba
    1 | ip2location

Tag AdCOM1.0-202607

  • List: IP Location Services, the row of 511 L3815 at d67a6a8
    511 | 51Degrees (High Confidence)
  • List: IP Location Services, the row of 512 L3819 at d67a6a8
    512 | 51Degrees (Medium Confidence)
  • List: IP Location Services, the row of 1 L3799 at d67a6a8
    1 | ip2location

The record's YAML file