Uploaded image for project: 'MusicBrainz Server'
  1. MusicBrainz Server
  2. MBS-13826

JSON-LD values sometimes strings instead of URLs

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • None

      Since JSON has no URL data type, for JSON-LD, either the context has to be clear that a property expects a URL, or the property's value has to be an object with

      {"@id": "http://example.com"}

      or whatever. This is mostly right in the JSON-LD API, but there are a few fields that sneak through. I've just noticed this issue for albumReleaseType and albumProductionType. Arguably, this is a schema.org issue (on the assumption that they should be declared as requiring particular schema classes), but the easier fix might be just to change the API code?

      [Note of caution: I'm not super fluent with JSON-LD, especially contexts, and I only spotted the errors when I converted the file to turtle, at which point the strings-instead-of-URLs issue jumps out]

          Loading...
          Uploaded image for project: 'MusicBrainz Server'
          1. MusicBrainz Server
          2. MBS-13826

          JSON-LD values sometimes strings instead of URLs

            • Icon: Bug Bug
            • Resolution: Unresolved
            • Icon: Normal Normal
            • None
            • None
            • None
            • None

              Since JSON has no URL data type, for JSON-LD, either the context has to be clear that a property expects a URL, or the property's value has to be an object with

              {"@id": "http://example.com"}

              or whatever. This is mostly right in the JSON-LD API, but there are a few fields that sneak through. I've just noticed this issue for albumReleaseType and albumProductionType. Arguably, this is a schema.org issue (on the assumption that they should be declared as requiring particular schema classes), but the easier fix might be just to change the API code?

              [Note of caution: I'm not super fluent with JSON-LD, especially contexts, and I only spotted the errors when I converted the file to turtle, at which point the strings-instead-of-URLs issue jumps out]

                    Unassigned Unassigned
                    dlewis David Lewis
                    Votes:
                    0 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                      Created:
                      Updated:

                        Version Package

                          Unassigned Unassigned
                          dlewis David Lewis
                          Votes:
                          0 Vote for this issue
                          Watchers:
                          2 Start watching this issue

                            Created:
                            Updated:

                              Version Package