197 common modeling questions

[dr-shorthair]

Streamlined Common Modeling Questions section with TTL and JSON-LD examples.
The patterns for location and unit-of-measure are now more prescriptive.

Preview here: https://raw.githack.com/w3c/sdw-sosa-ssn/197-common-modeling-questions/ssn/index.html#common-modeling-questions

[KathiSchleidt]

Are the @ in the hasSimpleResult attributes correct in ssn/examples/2024ex-uomtype.jsonld?

    "hasSimpleResult": {
        "@type": "http://qudt.org/vocab/unit/DEG_C",
        "@value": "19.9"
    }

[hylkevds]

The thing that bothers me about this example is that the number is encoded as a String. Which means the reader can't be sure the writer used decimal point or comma...
Is there a way around this?

[KathiSchleidt]

In SOSA we only have phenomenonTime and resultTime, in OMS we also have validTime. Under 8.4 Forecasts I read "A forecast may be represented as an observation where the value of sosa:phenomenonTime is later in time than the sosa:resultTime."

Do we leave this inconsistency, try to explain it, align it...?

[KathiSchleidt]

We need to clarify is sosa:System also gets a sosa:SystemOfInterest (parallel to sosa:Property and sosa:PropertyOfInterest), see #107 before we can finalize section 8.6 Generic or Specific Instances of sosa:System

Except for the bits listed here, looks good to go

[dr-shorthair]

In SOSA we only have phenomenonTime and resultTime, in OMS we also have validTime. Under 8.4 Forecasts I read "A forecast may be represented as an observation where the value of sosa:phenomenonTime is later in time than the sosa:resultTime."

Do we leave this inconsistency, try to explain it, align it...?

I don't see the inconsistency. validTime might be a useful addition, but the explanation of times for a forecast is correct with just "sosa:phenomenonTime is later than sosa:resultTime".

[dr-shorthair]

The thing that bothers me about this example is that the number is encoded as a String. Which means the reader can't be sure the writer used decimal point or comma... Is there a way around this?

Yes, I believe that in RDF any literal that is not typed as a number is a string.
If http://qudt.org/vocab/unit/DEG_C was asserted to be a sub-class of xsd:decimal then perhaps it would be OK?

In the JSON encoding if the quotes are dropped from "19.9" does that make it a number?

[dr-shorthair]

We need to clarify is sosa:System also gets a sosa:SystemOfInterest (parallel to sosa:Property and sosa:PropertyOfInterest), see #107 before we can finalize section 8.6 Generic or Specific Instances of sosa:System

The conversation seems to be converging. See #209

[hylkevds]

In the JSON encoding if the quotes are dropped from "19.9" does that make it a number?

Yes, without the quotes it's a proper number.