Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Current »

Completion Guidance

Section: Documentation (2)
Completion: Optional
Minimum number of entries allowed: 0
Maximum number of entries allowed: Multiple
Syntax restrictions: Named link

  • Please provide any media associated with the metadata using a valid URI for content and consistent with https://schema.org/MediaObject.

  • This is an opportunity to provide additional context that could be useful for users wanting to understand more about the metadata.

  • The following formats will be accepted .jpg, .png or .svg, .pdf, .xslx or .docx

  • This could be a PDF Document that describes methodology or further detail about the datasets, or a graph or charts that provides further context about the dataset.

  • This element is composed of

    • a Header (0..1) - Text that will appear above the named link(s). It has an an AbstractText datatype, which takes characters between 5 and 255 in length.

    • a Name (1..1) for the associated media

    • a Named link (0..*) with an AbstractText datatype, which takes characters between 5 and 255 in length. This allows the editor to input a link with associated descriptive text for the link.

    • an Explanation (0..*) with a String datatype, which is an expanded explanation about the link

Mappings

The table below shows the element mappings between the Exchange data model, the Data Alliance Partnership Board (DAPB) Information Standard Notice (ISN) and the Interoperability Standards Team Guide.

Note that where there is no direct mapping to the DAPB ISN, the editor will need to glean this information from reading through all documentation for the standard.

Exchange Element

DAPB ISN element

IOPS guide

Associated media

No direct mapping

To be decided

Example

ISN element

https://theprsb.org/standards/diabetesstandards/

This could also be a place to store links to key documentation e.g. a standard's requirements document.

FAQs

No questions received to date.

If you need further clarification, feel free to raise a support desk ticket.

  • No labels