Components

The components schema contains information regarding the individual components that are used to create products. These maybe created from:

• a single material
• a combination of materials
• other components
• a combination of materials and components

Table

Column	Status	Format	Notes
identifier	mandatory	UUID	A globally unique identifier. See identifiers section for information on how to construct this identifier
name	mandatory	String	The name of this component.
description	optional	String	A brief description of this component.
externalIdentifiers	optional	Dictionary	A dictionary of identifiers that is used to identify the component in other data standards, software systems or protocols. For example: manufacturer’s own primary key, bar codes or global trade item number (gtin). To provide external identifiers follow this format. {'externalIdentifierName1': 'identifier1', 'externalIdentifierName2': 'identifier2'}. The entries could be drawn from the External Identifiers Controlled List.
imageURLs	optional	List	A list of URLs that links to a picture of the component. Please see the guidelines below on how to capture the image and name the URL.
LOWcode	optional	String	The list of waste code for only the component, by itself. LOW code is synonymous with European Waste Catalogue Code (EWC). For example: a zip would have a LOWcode of 20 01 10. Please use Dsposal or legislation.gov to find the LOWcode. Note: The LOWcode can based on its combination with other components and the actual product contained in the products. Be sure to only include the component LOWcode.
constituentIdentifiers	mandatory	List	The information regarding the constituents that are combined to create this component. The entries should be from the Component Constituents List identifier.
measurements	mandatory	List	The information regarding the measurements of the component. The entries should be from the Measurements Relationship List.
shape	optional	String	What is the shape of the component? The entry should contain the shapes controlled list identifier for the component.
function	optional	String	What is the function of the component? The entry should contain the functions controlled list identifier for the component.
branding	optional	Boolean	Does the component contain your own brand (logo, trademark, or any distinctive mark)? Answer as: TRUE for yes and FALSE for no.
componentEndOfLifeRoutes	optional	List	The information regarding this component’s proposed end of life routes. The entries should be the component end of life routes identifiers.
colour	optional	String	The actual colour of the component at point of production using CMYK (Cyan-Magenta-Yellow-blacK) values. The format is specified according to cmyk(C%, M%, Y%, K%), where C, M, Y, and K are the percent values for the cyan, magenta, yellow, and black values of the color. For example: black is cmyk(0%,0%,0%,100%). If there are multiple colours input decorative.
loaned	optional	Boolean	Is the component hired or loaned? Answer as: TRUE for yes and FALSE for no. This is for this component ONLY, if the entire product is loaned or hired then use the product schema.
reuseSystems	optional	List	The system(s) that facilitates the reuse of the component e.g., ????. The entries should be the reuse systems controlled list identifier(s).
partOfMultipack	optional	Boolean	Is the component part of a multipack? Answer as: TRUE for yes and FALSE for no.
recycledContent	optional	Decimal	Positive decimal only, maximum value is 100.00. Value should equated to a percentage (e.g. 30 = 30%) The minimum allowable percent of how much recycled content is included in the makeup of the component.
recycledContentClaims	optional	List	The information regarding the recycled contents. The entries should be the recycled content claims relationship list indentifiers.
recyclability	optional	Boolean	Is the component recyclable (as determined by a reputable source)? Answer as: TRUE for yes and FALSE for no.
recyclabilityClaims	optional	List	The information regarding this recyclability claims. The entries should be the recyclability claims relationship list identifiers.
certification	optional	Boolean	Does the component have a certificate (e.g. FSC, REACH, FSA etc.)? Answer as: TRUE for yes and FALSE for no.
certificationClaims	optional	List	The information regarding the certifications. The entries should be the certification claims relationship list identifiers.
careLabel	optional	Boolean	Does the component have a care label (e.g. GINETEX, ASTM D5489, ISO 20471 etc.)? Answer as: TRUE for yes and FALSE for no.
careLabelClaims	optional	List	The information regarding the care labels. The entries should be the care label claims relationship list identifiers.
manufacturers	optional	List	The information regarding the manufacturer(s). The entries should be the [Organisations Relationship List](../relationship-lists/organisations.md identifiers.
manufacturedCountry	optional	String	The country the component was manufactured in. Use the country numeric ISO codes as described in the ISO 3166 international standard.
updateDate	mandatory	Date	The date that the component was provided/last updated. Use the format yyyy-mm-dd adhering to the ISO 8601 dateTime standard.
releaseDate	optional	Date	The date that the component will be available to use. Use the format yyyy-mm-dd adhering to the ISO 8601 dateTime standard.
discontinueDate	optional	Date	The date that the component was discontinued, meaning it was no longer available for purchase. Use the format yyyy-mm-dd adhering to the ISO 8601 dateTime standard.
listedDate	optional	Date	The date that the component was first listed for purchase. Use the format yyyy-mm-dd adhering to the ISO 8601 dateTime standard.

Diagram

erDiagram
MATERIALS }o--o{ COMPONENTS : component_constituents
  COMPONENTS {
    identifier UUID "*"
    name String
    description String
    externalIdentifiers Dictionary
    imageURLs List
    LOWcode String
    constituentIdentifiers List "*"
    measurements List "*"
    shape String
    function String
    branding Boolean
    componentEndOfLifeRoutes List
    colour String
    loaned Boolean
    reuseSystems List
    manufacturers List
    manufacturedCountry String
    recycledContent Decimal
    recycledContentClaims List
    recyclability Boolean
    recyclabilityClaims List
    partOfMultipack Boolean
    certification Boolean
    certificationClaims List
    careLabel Boolean
    careLabelClaims List
    updateDate Date "*"
    releaseDate Date
    discontinueDate Date
  }
  COMPONENTS }o..o{ CONTROLLED_LISTS : attributes
  COMPONENTS }o..o{ RELATIONSHIP_LISTS : attributes
  COMPONENTS }o--o{ PRODUCTS : products_constituents
  COMPONENTS }o..o{ MULTIPACK : multipack_constituents
  MULTIPACK }o..o{ LOADS : load_constituents
  PRODUCTS }o..o{ MULTIPACK : multipack_constituents
  PRODUCTS }o..o{ LOADS : load_constituents
  COMPONENTS }o..o{ LOADS : load_constituents
    CONTROLLED_LISTS {
    shapes optional
    functions optional
    reuseSystem optional
  }
  RELATIONSHIP_LISTS {
    measurements mandatory
    componentEndOfLifeRoutes optional
    recycledContentClaims optional
    recyclabilityClaims optional
    certificationClaims optional
    careLabelClaims optional
    organisations optional
  }

Guide for component images

As with providing measurements, please first find the default front of the component. The image capturing process and naming convention is similar to GS1. As with measurements, we altered the gs1 standard for capturing the component.

Type of Image

For the purposes of this standard, we define the differences between photographic and rendered images. Note: both types are accepted but the naming convention will differ based on image type so that images have unique names and do not having naming conflicts.

• Photographic image: the result of the electronic or chemical capture of a likeness of a physical object with the use of a camera.
• Rendered image: the result of the creation of a digital likeness of a physical object with the use of a computer and software.

Image Recommendations

• Provide coloured images. However, do not provide colour casts. Colour should be as rich, vibrant and eye-catching as possible
• Contrast and exposure should be balanced; avoid high contrast effects and “blown-out” highlights
• Images should not be overly sharpened
• Components should be centred in Margins to cover 95% on the canvas.
• Graphic rendering of a component should be realistic.
• Do not provide layers, guides or rulers in the images.
• Background layer should be white (RGB 255,255,255).
• Remove signatures, “finger printing” or visible watermarks. No compression artifacts. No interpolation (“resizing up”).

File size

• 900x900 to 2400x2400 pixels

Component faces

After determining the default front, the possible faces, in relation to the default front, are: 1. Default Front 2. Left 3. Top 7. Back 8. Right 9. Bottom

Naming convention for URL

Please follow this naming convention: - component identifier - underscore _ - type of image (photographic or rendered) - underscore _ - component face (1: Default front, 2: Left, 3: Top, 7: Back, 8: Right, 9: Bottom) - orientation (C: Centre, L: left, R: right, N: No plunge angle)

Example: An image for a component that is rendered with a default front facing image and centred orientation. identifier123_rendered_1C.jpg