HCS Schema Profile Registry 1.0 Draft Specification

This document is published by the Human Consent Standard Governance Board as a Draft for review and comment. It reflects contributions and reviews from the HCS Artist Governance Board, the HCS Industry Governance Board, and the HCS Policy Governance Board.

This Draft is a work in progress, is subject to change, and MUST NOT be used for production implementation.

This document is a companion to the Human Consent Standard (HCS) 1.0 Specification. Capitalized terms not defined in this document have the meanings defined in the HCS Specification.

The keywords MUST, MUST NOT, REQUIRED, SHOULD, MAY, and OPTIONAL follow RFC 2119 and RFC 8174.

Examples in this document are non-normative unless expressly stated otherwise. JSON-LD examples are shown without XML escaping for readability.

HCS declarations use the <schema> element to provide Schema.org JSON-LD metadata that describes the Rights Subject identified by the declaration. While Schema.org provides a common vocabulary for describing objects, it does not define the rights-specific profiles needed to represent HCS Rights Subjects in a standard form that AI Systems can interpret.

The HCS Schema Profile Registry defines standardized profiles that constrain Schema.org for HCS use. Each Schema Profile specifies how a particular category of Rights Subject MUST be represented, including the permitted Schema.org type, required properties, supported identifiers, and applicable validation requirements.

This registry lists the Schema Profiles currently recognized by this document and their status. Profile status values are defined as follows:

• Finalized: Approved as a standardized industry Schema Profile under HCS and applicable to conformance under this specification.
• Draft: Defines a proposed data model for review, testing, and implementation feedback.
• Reserved: Identifies a profile category reserved for future definition, but does not define profile requirements.

Except as expressly permitted by the HCS 1.0 Draft Specification, only a Schema Profile with status Finalized is applicable for purposes of HCS schema conformance.

New Schema Profile entries, status changes, and changes to existing profile definitions are made through the HCS standards process. Changes to a Finalized profile MUST preserve backward compatibility. A change that would make a previously conforming Schema Profile object non-conforming is incompatible and MUST be published as a new Schema Profile with a distinct Profile Identifier and registry entry. The prior Profile Identifier and profile definition MUST remain available.

This section defines requirements shared by Schema Profiles in this registry. Each Schema Profile has a Profile Identifier, which is the absolute HTTPS URL specified in its registry entry. Profile Identifier values MUST match exactly, with no URL normalization.

A Schema Profile object MUST be a JSON-LD object that defines Schema.org as its vocabulary and represents a single Rights Subject identified by its @id. It MUST conform to the applicable Schema Profile as represented in the parsed JSON object before JSON-LD expansion.

Every Schema Profile object MUST contain the following common properties:

A Schema Profile object with Rights Subject mark describes the mark, design, configuration, ornamentation, or trade dress itself, rather than any individual registration, design patent, or other legal protection associated with it. Multiple registrations or legal protections for the same Rights Subject MAY be included as Identifiers and do not, by themselves, establish separate Rights Subjects.

A Schema Profile MAY require properties in addition to those listed in this section and MAY define more specific requirements for any common property.

A Schema Profile object MAY also contain optional Schema.org properties not listed in the applicable Schema Profile, unless that profile prohibits them; JSON-LD keywords other than @context, @id, and @type MUST NOT appear. Such properties MUST use value forms permitted by Schema.org. Unless this specification or the applicable Schema Profile specifies otherwise, a property MAY contain a single permitted value or an array of permitted values.

When used, datePublished MUST identify the first public release, publication, or availability of the Rights Subject in any form. A registration, completion, delivery, or revision date MUST NOT be used.

Whenever a Schema Profile permits an image or other visual representation as a URL, the value MUST be a Processor-Accessible absolute HTTPS URL. An ImageObject used as a visual representation MUST contain a contentUrl property containing a single Processor-Accessible absolute HTTPS URL.

Example

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "Person",
  "additionalType": "https://humanconsent.org/schemas/identity",
  "name": "Example Performer",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "IMDb",
      "url": "https://www.imdb.com/name/{IMDB_NAME_ID}"
    }
  ]
}

Schema Profiles use the top-level Schema.org identifier property to provide identifiers that distinguish the Rights Subject described by the Schema Profile object.

The top-level identifier property MUST contain an array of one or more Schema.org PropertyValue objects. Each object MUST use one of the following forms:

• an Identifier Value, which provides an identifier assigned to the Rights Subject by a recognized identifier system
• an Identifier URL, which provides a Processor-Accessible resource that identifies or describes the Rights Subject

Each object MUST conform to exactly one of the forms defined in Sections 2.2.1 and 2.2.2 and use a propertyID defined in Section 2.3 and supported by the applicable Schema Profile.

Each Schema Profile classifies its supported identifiers as Normative Identifiers or Additional Identifiers. Every Schema Profile object MUST contain at least one Normative Identifier supported by the applicable Schema Profile. Additional Identifiers MAY be included to provide supplemental identification information.

Every top-level Identifier Value or Identifier URL MUST identify or describe the Rights Subject itself or an edition, translation, publication format, or other manifestation covered by the applicable Schema Profile.

An identifier property within a nested Schema.org object identifies that object. Each identifier MUST use one of the forms defined in Sections 2.2.1 and 2.2.2 and a propertyID defined in Section 2.3 that identifies or describes the nested object.

An Identifier Value provides an identifier assigned by a recognized identifier system.

Example

{
  "@type": "PropertyValue",
  "propertyID": "ISNI",
  "value": "{ISNI}"
}

An Identifier URL provides a Processor-Accessible URL that identifies or describes the object to which the identifier applies. Processor-Accessible has the meaning defined in the HCS 1.0 Specification.

Example

{
  "@type": "PropertyValue",
  "propertyID": "IMDb",
  "url": "https://www.imdb.com/name/{IMDB_NAME_ID}"
}

This section defines the propertyID values used in Identifier Value and Identifier URL objects. Each Schema Profile defines which values it supports for top-level identifiers. propertyID values are case-sensitive and MUST be compared exactly as written.

This section defines the registered Schema Profiles for specific Rights Subjects.

This profile describes a feature-length, short-form, documentary, animated, or other motion picture created as a standalone audiovisual work.

A Motion Picture Schema Profile object uses the Schema.org Movie type.

A Motion Picture Schema Profile object MAY describe either the motion picture as a general work or a specific edit or version. An identifier for one edit or version MUST NOT be treated as identifying another unless the applicable Registry or the source of the identifier establishes that relationship.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "Movie",
  "additionalType": "https://humanconsent.org/schemas/movie",
  "name": "Example Motion Picture",
  "datePublished": "2026-01-01",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "EIDR",
      "value": "{EIDR}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "OfficialPage",
      "url": "https://studio.example/movies/example-motion-picture"
    }
  ]
}

This profile describes a television or streaming series, season, or episode.

A Television Schema Profile object uses the Schema.org TVSeries, TVSeason, or TVEpisode type.

A television series, season, and episode are separate Rights Subjects. An identifier for one MUST NOT be treated as identifying another unless the applicable Registry or the source of the identifier establishes that relationship.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "TVEpisode",
  "additionalType": "https://humanconsent.org/schemas/television",
  "name": "Example Episode",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "ISAN",
      "value": "{ISAN}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "OfficialPage",
      "url": "https://studio.example/television/example-series/season-1/episode-1"
    }
  ]
}

This profile describes an interactive digital game or video game series, including console, computer, mobile, browser, virtual reality, and augmented reality games.

A Video Game Schema Profile object uses the Schema.org VideoGame or VideoGameSeries type.

A Video Game Schema Profile object MAY describe either the video game as a general work or a specific edition. An identifier for one edition MUST NOT be treated as identifying another unless the applicable Registry or the source of the identifier establishes that relationship.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "VideoGame",
  "additionalType": "https://humanconsent.org/schemas/game",
  "name": "Example Video Game",
  "datePublished": "2026-01-01",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "EIDR",
      "value": "{EIDR}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "OfficialPage",
      "url": "https://games.example/example-video-game"
    }
  ]
}

This profile describes an underlying musical work, including any accompanying lyrics administered as part of the musical work.

A Musical Work Schema Profile object uses the Schema.org MusicComposition type.

A musical work and a sound recording of that work are separate Rights Subjects. An Identifier Value or Identifier URL for a musical work MUST NOT be treated as identifying a sound recording, and an identifier for a sound recording MUST NOT be treated as identifying the underlying musical work.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "MusicComposition",
  "additionalType": "https://humanconsent.org/schemas/composition",
  "name": "Example Song",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "ISWC",
      "value": "{ISWC}"
    }
  ]
}

This profile describes a sound recording, master recording, or other fixed recording of sounds.

A Sound Recording Schema Profile object uses the Schema.org MusicRecording type for a musical recording and the CreativeWork type for any other type of sound recording.

A sound recording and any underlying musical, literary, dramatic, or other work embodied in the recording are separate Rights Subjects. An identifier for one recording MUST NOT be treated as identifying another recording or version unless the applicable Registry or the source of the identifier establishes that relationship.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "MusicRecording",
  "additionalType": "https://humanconsent.org/schemas/recording",
  "name": "Example Recording",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "ISRC",
      "value": "{ISRC}"
    }
  ]
}

This profile describes a literary work published as a book, including fiction, nonfiction, scholarly, reference, and other book-length works. Scripts, articles, and other literary works use their applicable Schema Profiles.

A Book Schema Profile object uses the Schema.org Book type.

A book-level Schema Profile object MAY include ISBN values assigned to its editions, translations, or publication formats.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "Book",
  "additionalType": "https://humanconsent.org/schemas/book",
  "name": "Example Novel",
  "datePublished": "2026-01-01",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "ISBN",
      "value": "{ISBN}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "OfficialPage",
      "url": "https://publisher.example/books/example-novel"
    }
  ]
}

This profile describes a screenplay, teleplay, stage script, treatment, outline, series bible, dialogue, or other production literary material.

A Script Schema Profile object uses the Schema.org CreativeWork type.

A Script Schema Profile object MAY describe either the underlying script or a specific draft, revision, or version. An identifier for one draft, revision, or version MUST NOT be treated as identifying another unless the applicable Registry or the source of the identifier establishes that relationship.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "CreativeWork",
  "additionalType": "https://humanconsent.org/schemas/script",
  "name": "Example Motion Picture Screenplay",
  "version": "Second Revised Draft",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "WGAWRegistry",
      "value": "{WGAW_REGISTRATION_NUMBER}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "WGAERegistry",
      "value": "{WGAE_REGISTRATION_NUMBER}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "OfficialPage",
      "url": "https://studio.example/scripts/example-motion-picture"
    }
  ]
}

This profile describes a news, magazine, scholarly, professional, trade, blog, or other published article.

An Article Schema Profile object uses the Schema.org Article type.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "Article",
  "additionalType": "https://humanconsent.org/schemas/article",
  "name": "Example Article Headline",
  "datePublished": "2026-01-01",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "DOI",
      "value": "{DOI}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "OfficialPage",
      "url": "https://publisher.example/articles/example-article"
    }
  ]
}

This profile describes a poem, short story, speech, letter, essay, unpublished prose, or other literary or textual work not covered by the Book, Script, or Article Schema Profiles. Song lyrics administered as part of a musical work are covered by the Musical Work Schema Profile.

A Literary Work Schema Profile object uses the Schema.org CreativeWork type.

A Literary Work Schema Profile object MAY describe either the underlying work or a specific version, revision, or translation. An identifier for one version, revision, or translation MUST NOT be treated as identifying another unless the applicable Registry or the source of the identifier establishes that relationship.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "CreativeWork",
  "additionalType": "https://humanconsent.org/schemas/literary",
  "name": "Example Poem",
  "datePublished": "2026-01-01",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "DOI",
      "value": "{DOI}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "OfficialPage",
      "url": "https://publisher.example/works/example-poem"
    }
  ]
}

This profile describes a photographic work, including an editorial, documentary, commercial, stock, portrait, fashion, fine-art, scientific, or technical photograph.

Photographs generally lack widely adopted work-level identifier systems, requiring one or more visual representations, expressed as a Processor-Accessible HTTPS URL, a Schema.org ImageObject, or an array of either form.

A Photograph Schema Profile object uses the Schema.org Photograph type.

An ISCC or IPTCDigitalImageGUID MAY be used as a top-level identifier when it identifies the photograph or a digital manifestation covered by this profile. When included in a nested ImageObject, it identifies only that visual representation and does not satisfy the top-level Normative Identifier requirement.

A Photograph Schema Profile describes the photographic work, not any person, character, mark, artwork, object, or event depicted in the photograph.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "Photograph",
  "additionalType": "https://humanconsent.org/schemas/photo",
  "name": "Example Portrait",
  "image": {
    "@type": "ImageObject",
    "contentUrl": "https://photographer.example/works/example-portrait/preview.jpg"
  },
  "creator": {
    "@type": "Person",
    "name": "Example Photographer",
    "identifier": [
      {
        "@type": "PropertyValue",
        "propertyID": "ULAN",
        "value": "{ULAN_ID}"
      }
    ]
  },
  "dateCreated": "2026-01-01",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "ISCC",
      "value": "{ISCC}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "IPTCDigitalImageGUID",
      "value": "{IPTC_DIGITAL_IMAGE_GUID}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "OfficialPage",
      "url": "https://photographer.example/works/example-portrait"
    }
  ]
}

This profile describes a non-photographic visual artwork, including a painting, drawing, print, illustration, graphic artwork, collage, assemblage, sculpture, mixed-media work, or standalone digital artwork.

Visual artworks generally lack widely adopted work-level identifier systems, requiring one or more visual representations, expressed as a Processor-Accessible HTTPS URL, a Schema.org ImageObject, or an array of either form.

A Visual Artwork Schema Profile object uses the Schema.org VisualArtwork, Painting, or Sculpture type. Painting or Sculpture SHOULD be used when that type accurately describes the Rights Subject. VisualArtwork MAY be used for other visual artworks covered by this profile.

A Visual Artwork Schema Profile describes the artwork itself, not a photograph, scan, or other reproduction of the artwork and not any person, character, mark, object, or other Rights Subject depicted in it.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "Painting",
  "additionalType": "https://humanconsent.org/schemas/artwork",
  "name": "Example Abstract Composition",
  "image": {
    "@type": "ImageObject",
    "contentUrl": "https://artist.example/works/example-abstract-composition.jpg",
    "identifier": [
      {
        "@type": "PropertyValue",
        "propertyID": "ISCC",
        "value": "{ISCC}"
      }
    ]
  },
  "creator": {
    "@type": "Person",
    "name": "Example Artist",
    "identifier": [
      {
        "@type": "PropertyValue",
        "propertyID": "ULAN",
        "value": "{ULAN_ID}"
      }
    ]
  },
  "dateCreated": "2026-01-01",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "CONA",
      "value": "{CONA_ID}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "OfficialPage",
      "url": "https://artist.example/works/example-abstract-composition"
    }
  ]
}

This profile describes an identifiable natural person, including a professional persona of that person.

An Identity Schema Profile object conforms to the Schema.org Person type.

When an Identity Schema Profile object appears in a Rights Declaration that applies to the image or likeness Rights Scope, including when subject-scope is absent, its top-level identifier property MAY include one or more Normative Identifier URLs for a specific image or audiovisual media item depicting the Rights Subject. The object MAY also include profiles, accounts, channels, feeds, galleries, playlists, catalog pages, or other supported identifiers.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "Person",
  "additionalType": "https://humanconsent.org/schemas/identity",
  "name": "Example Performer",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "OfficialPage",
      "url": "https://example-performer.example"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "IMDb",
      "url": "https://www.imdb.com/name/{IMDB_NAME_ID}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "Wikidata",
      "url": "https://www.wikidata.org/entity/{WIKIDATA_QID}"
    }
  ]
}

This profile describes a fictional character or persona, including a human, animal, creature, object, or other entity presented as a distinct character. Characters generally lack widely adopted character-level identifier systems.

A Character Schema Profile object uses the Schema.org Person type for a human character and the Thing type for an animal, creature, object, or other non-human character.

A Character Schema Profile object MAY describe a character generally or a specific version or portrayal. An identifier for the general character MUST NOT be treated as identifying a specific version or portrayal, and an identifier for one version or portrayal MUST NOT be treated as identifying another unless the applicable Registry or the source of the identifier establishes that relationship.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "Person",
  "additionalType": "https://humanconsent.org/schemas/character",
  "name": "Example Character",
  "description": "A fictional detective appearing in the Example Stories series.",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "Wikidata",
      "url": "https://www.wikidata.org/entity/{WIKIDATA_QID}"
    }
  ]
}

This profile describes a trademark, service mark, or other conventional or non-traditional source identifier not covered by the Product Design and Configuration, Surface Ornamentation, or Trade Dress Schema Profiles.

A Trademark Schema Profile object uses the Schema.org Brand type.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "Brand",
  "additionalType": "https://humanconsent.org/schemas/trademark",
  "name": "Example Monogram",
  "description": "An interlocking E and M monogram.",
  "logo": "https://example-maison.example/marks/example-monogram.svg",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "EUIPOTrademark",
      "value": "{EU_TRADE_MARK_REGISTRATION_NUMBER}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "WIPOMadrid",
      "value": "{MADRID_INTERNATIONAL_REGISTRATION_NUMBER}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "OfficialPage",
      "url": "https://example-maison.example/marks/example-monogram"
    }
  ]
}

This profile describes the form and configuration of a product or product component, including its shape, contours, proportions, and combination of design features.

A Product Design and Configuration Schema Profile object uses the Schema.org Product type.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "Product",
  "additionalType": "https://humanconsent.org/schemas/configuration",
  "name": "Example Handbag Design",
  "description": "A structured handbag design with a trapezoidal body, curved top handle, and centered geometric clasp.",
  "image": [
    "https://example-maison.example/designs/example-handbag/front.jpg",
    "https://example-maison.example/designs/example-handbag/side.jpg"
  ],
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "EUIPODesign",
      "value": "{EU_REGISTERED_DESIGN_NUMBER}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "WIPOHague",
      "value": "{HAGUE_INTERNATIONAL_REGISTRATION_NUMBER}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "OfficialPage",
      "url": "https://example-maison.example/designs/example-handbag"
    }
  ]
}

This profile describes a design applied to a product or surface, including a pattern, print, motif, graphic, line arrangement, texture, color arrangement, or other decorative surface feature, rather than the form or configuration of the product.

A Surface Ornamentation Schema Profile object uses the Schema.org VisualArtwork type.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "VisualArtwork",
  "additionalType": "https://humanconsent.org/schemas/ornamentation",
  "name": "Example Interlocking Motif",
  "description": "A repeating surface design composed of interlocking geometric E and M forms arranged in diagonal rows.",
  "image": "https://example-maison.example/designs/example-interlocking-motif.jpg",
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "EUIPODesign",
      "value": "{EU_REGISTERED_DESIGN_NUMBER}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "WIPOHague",
      "value": "{HAGUE_INTERNATIONAL_REGISTRATION_NUMBER}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "OfficialPage",
      "url": "https://example-maison.example/designs/example-interlocking-motif"
    }
  ]
}

This profile describes the source-identifying appearance of product packaging, containers, labels, wrapping, displays, retail or service environments, and other commercial presentations. Product design and surface ornamentation use the profiles defined in Sections 3.15 and 3.16.

A Trade Dress Schema Profile object uses the Schema.org Thing type.

{
  "@context": "https://schema.org",
  "@id": "https://id.humanconsent.org/HCSI-0000-0001-1",
  "@type": "Thing",
  "additionalType": "https://humanconsent.org/schemas/tradedress",
  "name": "Example Presentation Box Trade Dress",
  "description": "A rigid rectangular presentation box with a deep blue exterior, a contrasting cream border, and a centered gold geometric clasp.",
  "image": [
    "https://example-maison.example/trade-dress/presentation-box/exterior.jpg",
    "https://example-maison.example/trade-dress/presentation-box/open.jpg"
  ],
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "USPTOTrademark",
      "value": "{USPTO_TRADEMARK_REGISTRATION_NUMBER}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "EUIPOTrademark",
      "value": "{EU_TRADE_MARK_REGISTRATION_NUMBER}"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "OfficialPage",
      "url": "https://example-maison.example/trade-dress/presentation-box"
    }
  ]
}