Whether in the context of sending actual RDF files as files (like JSON-LD), or in the context of software-to-software connections where there may be queries or content negotiation for RDF data to be exchanged, there will need to be a metadata about the file and/or system that communicates data like tier of alignment, aligned version of the data standard used, and so on.
This will become relevant very soon for an aligned vendor (and funder user) that will be aligned at Essential tier or higher, and may receive files that are either Basic Tier only, or Basic Tier + SFF, or Essential Tier, and might parse the file differently depending on which one it is.
The specific example is where information about whether or not an IndicatorReport is actually a Target will be encoded in the comment of an IndicatorReport where files are Basic Tier, or in instances of the Target class at Essential Tier or higher.
Whether in the context of sending actual RDF files as files (like JSON-LD), or in the context of software-to-software connections where there may be queries or content negotiation for RDF data to be exchanged, there will need to be a metadata about the file and/or system that communicates data like tier of alignment, aligned version of the data standard used, and so on.
This will become relevant very soon for an aligned vendor (and funder user) that will be aligned at Essential tier or higher, and may receive files that are either Basic Tier only, or Basic Tier + SFF, or Essential Tier, and might parse the file differently depending on which one it is.
The specific example is where information about whether or not an IndicatorReport is actually a Target will be encoded in the comment of an IndicatorReport where files are Basic Tier, or in instances of the Target class at Essential Tier or higher.