How to represent references to TextResources

[tomkxy]

In the MDP project, we need to represent "links" to reference files. I know about the sample property which does not fit here. What is the most and easiest was to represent that in IDS?

[HaydarAk]

Hi!

Can you elaborate, what we need to represent "links" to reference files means ? Something directly related to the resource ?

We have some relations ids:Resources modeled:

• ids:variant and ids:sample: As the names suggest, these properties can be used to refer to variants of resources and samples / snippets. Both properties point to ids:Resource .
• ids:contentStandard & ids:representationStandard with some IRI as range: Can be used to refer to some kind of document, which describes the standard the ids:Resource / ids:Representation conforms to.
• the ids:Contract class can refer to contract-related resources via ids:contractAnnex (range ids:Resource) & ids:contractDocument (range ids:TextResource).

You could also have the file represented as an additional artifact for the given Resource.

[tomkxy]

Hi Haydar,

yes it is directly related to the resources. Those are files which provide additional context for the resources and are required or helpful to understand resource content. ids:sample is known to me, but doesn't really fit. I would expect there sample content files. So far, I interpreted contentStandard and representationStandard rather for things like schema file. However, they could fit. Could you please elaborate on the difference between contentStandard and representationStandard?
Let's assume I have a JSON schema file, I would like to attach to the resource. What would be the appropriate property?

[HaydarAk]

Could you please elaborate on the difference between contentStandard and representationStandard?

As you may know, a ids:Resource may contain multiple ids:Representations.
A contentStandard covers the resource as a whole while representationStandard is more related to a concrete representation. E.g., JSON/XML schema should be refered to via representationStandard because they are related to the given ids:Representation. Even if there is only one ids:Representation. This somestimes leads to complementary information between the mediaType and representationStandard property. Think of a scenario, where you want to share a RDF/Turtle file.
There is a IANA media type for turtle, but you could also provide the W3C turtle spec as a representationStandard.
A valid but trivial example :)

The contentStandard a bit more like a general purpose property used to describe the resoruce as a whole. E.g., conformance to some regulations or the content is related to some kind of standard which is representation agnostic. Although I am not an expert in spatial data, I'd say that one should refer to the geodetic reference system (e.g., WGS84) via the contentStandard.
How the data is shared (JSON, XML, SQL Dump) is surely related to the contentStandard but a XML file with WGS84 coordinates is on high level similar to a JSON file with WGS84 coordinates.

[tomkxy]

Thanks. Based on that input, I would model the schema file using the representationStandard property and would use contentStandard to store any additional contextual file information. The field is of range anyURI. Would it work in combination with the Java classes if I would reference a TextResource through this property?

[HaydarAk]

The field is of range anyURI. Would it work in combination with the Java classes if I would reference a TextResource through this property?

Should be. xsd:anyURI maps to a corresponding URI representation in Java. As far as I know, the java standard URI class is used (java.net.URI). You can provide any kind of IRI which may also be a reference to a ids:TextResource :)

[clange]

BTW, so far it has not been specified what exactly ids:contentStandard or ids:representationStandard should link to: a specification document, a schema resource, etc. In future, it may become necessary to introduce more specific subproperties for these cases. In the Datenraum Mobilität we have discussed the technical integration of a Vocabulary Provider via ids:contentStandard / ids:representationStandard pointing to the URI of a schema known to the Vocabulary Provider, e.g., an XML namespace URI or an ontology URI. In various settings we are realizing that we may need to formally specify the interaction of other components with a Vocabulary Provider.

[tomkxy]

For me ids:representationStandard would be kind of clearly related to for instance a schema file to which content is supposed to adhere to.
For contentStandard that is not that clear. It seems to be plausible to use it to integrate a vocab provider. But then, I again would have the question how to link to additional "files" which contains what ever is required to understand content.

[JohannesLipp]

@tomkxy sorry for the late reply. Could you please comment if the issue still remains and still needs to be tackled? Thank you in advance!

[tomkxy]

If there hasn't been any changes in the Infomobil V5, then it is still present. Though, we have been worked around. But anyway, I still find it cumbersome.