Skip to content

ISCC Terms#

Mapped Terms#

The following terms used in the ISCC metadata vocabulary are mapped to equivalents in other schemas. We added comments to the original term descriptions to clarify the definition in context with ISCC metadata.

name#

http://schema.org/name

The name of the item.

Comment: The title or name of the intangible creation manifested by the identified digital content. Used as input for ISCC Meta-Code generation.

Embedding: Use Iptc.Application2.Headline and Xmp.photoshop.Headline for image embedding

description#

http://schema.org/disambiguatingDescription

A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation.

Comment: Description of the digital content identified by the ISCC. Used as input for ISCC Meta-Code generation. Any user presentable text string (including Markdown text) indicative of the identity of the referent may be used.

Embedding: Use Exif.Image.ImageDescription, Iptc.Application2.Caption and Xmp.dc.description for image embedding.

creator#

http://schema.org/creator

The creator/author of this CreativeWork. This is the same as the Author property for CreativeWork.

Comment: An entity primarily responsible for making the resource.

Embedding: Use Exif.Image.Artist, Iptc.Application2.Byline and Xmp.dc.creator for emedding this field into image metadata.

license#

http://schema.org/license

A license document that applies to this content, typically indicated by URL.

Comment: URI of license for the identified digital content.

Embedding: Use Xmp.xmpRights.WebStatement for embedding as image metadata.

acquire#

http://schema.org/acquireLicensePage

Indicates a page documenting how licenses can be purchased or otherwise acquired, for the current item.

Comment: This field must contain a valid URL referring to a page showing information about how one can acquire a license for the item. This may be a page of a web shop or NFT marketplace ready for providing a license.

Embedding: Use Xmp.plus.Licensor[1]/plus:LicensorURL for embedding in images.

credit#

http://schema.org/creditText

Text that can be used to credit person(s) and/or organization(s) associated with a published Creative Work.

Comment: A line of text that you expect users of the image (such as Google Images) to display alongside the image.

Embedding: Use Iptc.Application2.Credit and Xmp.photoshop.Credit for metadata embedding.

rights#

http://schema.org/copyrightNotice

Text of a notice appropriate for describing the copyright aspects of this Creative Work, ideally indicating the owner of the copyright for the Work.

Comment: Contains any necessary copyright notice and should identify the current owner of the copyright of this work with associated intellectual property rights.

Embedding: Use Exif.Image.Copyright, Iptc.Application2.Copyright and Xmp.dc.rights for embedding.

media_id#

http://schema.org/identifier

The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links.

Comment: Vendor specific (internal) identifier for the source media file.

iscc_id#

http://schema.org/identifier

The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links.

Comment: The ISCC-ID of the digital content in canonical representation.

image#

http://schema.org/image

An image of the item. This can be a URL or a fully described ImageObject.

Comment: URI for a user-presentable image that serves as a preview of the digital content. The URI may be a Data-URL RFC2397. If ISCC metadata is used as NFT metadata according to ERC-721 or ERC-1155 the URI should reference the actual digital content represented by the NFT.

identifier#

http://schema.org/identifier

The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See background notes for more details.

Comment: Other identifier(s) referencing the work, product or other abstraction of which the referenced digital content is a full or partial manifestation.

content#

http://schema.org/contentUrl

Actual bytes of the media object, for example the image file or video file.

Comment: URI of the digital content that was used to create this ISCC.

keywords#

http://schema.org/keywords

Keywords or tags used to describe this content. Multiple entries in a keywords list are typically delimited by commas.

Comment: Keywords or tags used to describe this content. Either a list of keywords or a sting with comma separated keywords.

version#

http://schema.org/version

The version of the digital content identified by the ISCC.

Comment: The version of the CreativeWork embodied by a specified resource.

created#

http://schema.org/dateCreated

The date on which the CreativeWork was created or the item was added to a DataFeed.

Comment: Datetime the ISCC was created for the item.

filesize#

http://schema.org/fileSize

Size of the application / package (e.g. 18MB). In the absence of a unit (MB, KB etc.), KB will be assumed.

Comment: File size of media asset in number of bytes.

mediatype#

http://schema.org/encodingFormat

Media type typically expressed using a MIME format (see IANA site and MDN reference) e.g. application/zip for a SoftwareApplication binary, audio/mpeg for .mp3 etc.). In cases where a CreativeWork has several media type representations, encoding can be used to indicate each MediaObject alongside particular encodingFormat information. Unregistered or niche encoding and file formats can be indicated instead via the most appropriate URL, e.g. defining Web page or a Wikipedia/Wikidata entry.

Comment: An IANA Media Type (MIME type)

duration#

http://schema.org/duration

The duration of the item (movie, audio recording, event, etc.) in ISO 8601 date format.

Comment: Duration of audio-visual media in secondes.

pages#

http://schema.org/numberOfPages

The number of pages in the book.

Comment: Number of pages (for paged documents only)

language#

http://schema.org/inLanguage

The language of the content or performance or used in an action. Please use one of the language codes from the IETF BCP 47 standard. See also availableLanguage.

Comment: Language(s) of content BCP 47.

thumbnail#

http://schema.org/thumbnailUrl

A thumbnail image relevant to the Thing.

Comment: URI an autogenerated user-presentable thumbnail-image that serves as a preview of the digital content. The URI may be a Data-URL RFC2397.

credentials#

https://www.w3.org/2018/credentials#VerifiableCredential

A credential is a set of one or more claims made by an issuer. A verifiable credential is a tamper-evident credential that has authorship that can be cryptographically verified. Verifiable credentials can be used to build verifiable presentations, which can also be cryptographically verified. The claims in a credential can be about different subjects.

Comment: One or more Verifiable Credentials or one ore more URIs pointing to one or more VCs. A reader of ISCC metadata must interpret the value according to the following rules

  • If the value is a JSON string interpret it as an URI. The expectation is that the URI dereferences to a response with Content-type application/json where the data is a VC or an array of VCs.
  • If the value is a JSON object interpret it as a VC according to the Verifiable Credentials JSON Schema.
  • If the value is an array and an item in the array is a JSON object interpret it as a VC.
  • If the value is an array and an items is a string interpret the item as an URI that dereferences to VC(s)
  • Credentials should only be taken into account if the credentialSubject matches with the declarer (e.g. did:pkh representation of the declarers address).

ISCC Terms#

The ISCC metadata introduces the following additional properties specific to ISCC use-cases.

iscc#

http://purl.org/iscc/terms/#iscc

An ISCC-CODE in canonical representation. This is the minimal required field for a valid ISCC Metadata object.

meta#

http://purl.org/iscc/terms/#meta

Subject, industry, or use-case specific metadata encoded as Data-URL.

previous#

http://purl.org/iscc/terms/#previous

ISCC of the preceding version of this item.

filename#

http://purl.org/iscc/terms/#filename

Filename of the referenced digital content (automatically used as fallback if the name field was not specified for ISCC processing)

fps#

http://purl.org/iscc/terms/#fps

Frames per second of video assets.

width#

http://purl.org/iscc/terms/#width

Width of visual media in number of pixels.

height#

http://purl.org/iscc/terms/#height

Height of visual media in number of pixels.

characters#

http://purl.org/iscc/terms/#characters

Number of text characters (code points after Unicode normalization)

parts#

http://purl.org/iscc/terms/#parts

Indicates items that are part of this item via Content-Codes (inverse-property belongs).

part_of#

http://purl.org/iscc/terms/#part_of

Indicates that this item is part of other items via their Content-Code.

features#

http://purl.org/iscc/terms/#features

Granular features of the digital content.

generator#

http://purl.org/iscc/terms/#generator

Name and version of the software that generated the ISCC

external_url#

http://purl.org/iscc/terms/#external_url

This is the URL that will appear below the asset's image on some NFT Marketplaces and will allow users to leave the site and view the item on your site. Supports URI template (iscc-id).

animation_url#

http://purl.org/iscc/terms/#animation_url

A URL to a multi-media attachment for the item.

properties#

http://purl.org/iscc/terms/#properties

Arbitrary properties. Values may be strings, numbers, object or arrays. Properties defined here may show up on NFT marketplaces. See ERC-1155

attributes#

http://purl.org/iscc/terms/#attributes

Similar to properties but as an array of objects. These attributes will show up on some NFT marketplaces.

nft#

http://purl.org/iscc/terms/#nft

A unique URI for a non-fungible token of the identified content. The URI must contain references to the blockchain, smart-contract and token. The recommended schemes are CAIP-22 and CAIP-29.

tophash#

http://purl.org/iscc/terms/#tophash

A Multihash of the concatenation (binding) of metahash and datahash (default blake3).

metahash#

http://purl.org/iscc/terms/#metahash

A Multiformats multihash or IPFS CIDv1 of the supplied metadata. The hash is created from name and description fields or meta if supplied.

datahash#

http://purl.org/iscc/terms/#datahash

A Multihash of the digital content (default blake3).

original#

http://purl.org/iscc/terms/#original

The signee of the declaring transaction claims to be the original creator of the work manifested by the identified digital content.

redirect#

http://purl.org/iscc/terms/#redirect

URL to which an ISCC resolver should redirect the ISCC-ID. Supports URI template (iscc-id)

chain#

http://purl.org/iscc/terms/#chain

The blockchain on which an ISCC-CODE is declared.

wallet#

http://purl.org/iscc/terms/#wallet

The wallet-address that signs an ISCC declaration.

verifications#

http://purl.org/iscc/terms/#verifications

A list of self-verifications. Self-verifications are public URLs under the account/authority of the signee. The verification URL must respond to a GET request with text that contains a multihash of the ISCC declaration signees wallet address in the format of verify:<multihash-of-wallet-address>:verify.