Open ghobona opened 2 months ago
Noting that the SensorML requirements class specifies a media type of application/sml+json
.
Since the media type is not yet registered with IANA, I think this should be in the vendor (vnd.) tree instead.
The document currently uses the following term.
UAS: Unmanned Aerial System
ISO 5305 defines UAS as unmanned aircraft system, see https://www.iso.org/obp/ui/en/#iso:std:iso:5305:ed-1:v1:en
ISO 23665, ISO 21384, and ISO 4358 also use the term ‘unmanned aircraft system’.
The UxS DWG uses the term Uninhabited System.
https://www.ogc.org/about-ogc/committees/dwg/uninhabited-systems-domain-working-group/
Some URIs appear to have placeholders (e.g. TBD) in them.
See Tables 6, 10, and 15.
See also the Example underneath Table 21
Alex -
I noticed an inconsistency on the definition of one of the Sampling Feature Associations in Table 17
sampledFeature sosa:isSampleOf he ultimate feature of interest that is being sampled or controlled. In OMS and SSN, the relation isSampleOf links a Sample to the proximate feature of interest, not the ultimate FoI. There may then be a chain of further samples before you reach the ultimate FoI. The additional properties hasOriginalSample and hasSampledFeature provide shortcuts. See diagrams in the SSN-Ext paper, which inspired OMS and the SSN update - https://www.w3.org/TR/vocab-ssn-ext/#ultimate-feature-of-interest
Perhaps we should add these diagrams and explanation into the SSN update, in the Common Modeling Questions section?
@alexrobin Please see the comments above.
@gobona I'm glad you created this issue since we wanted to seek advice from the OGC NA on these topics.
Regarding media types, is there a need/good reason to register them with IANA ultimately, or are we happy with something in vnd.ogc
namespace for the entire life of the standard? I don't mind either way. Less work is good ;-) Is the vnd.ogc
namespace registered officially?
Regarding our custom URIs, is the recommendation to host these in the OGC definition server? If so,what's the process to do that these days?
Hi Kathi,
No, the definitions haven't diverged. This just means that all the platforms that are under a System collection are both sosa:Platform and sosa:System as per the discussion we had in the SOSA/SSN WG.
See my comment here: https://github.com/opengeospatial/ogcapi-connected-systems/issues/52
Thanks,
--
Alex Robin
Chief Technology Officer | GeoRobotix Inc. | +1 302 703 7072
On Wed, May 1, 2024 at 12:52 PM Kathi Schleidt @.***> wrote:
Hi Alex,
an additional inconsistency with SOSA that I've noticed - in Table 5 you list SOSA:Platform under the connected-systems:System Types. Does this imply that your definitions of System and Platform have diverged from the base SOSA definition?
:?
Kathi System Type URI CURIE Usage Sensor http://www.w3.org/ns/sosa/Sensor sosa:Sensor When the system’s primary activity is ‘sensing’ or ‘observing’. Actuator http://www.w3.org/ns/sosa/Actuator sosa:Actuator When the system’s primary activity is ‘actuating’. Sampler http://www.w3.org/ns/sosa/Sampler sosa:Sampler When the system’s primary activity is ‘sampling’. Platform http://www.w3.org/ns/sosa/Platform sosa:Platform When the system’s primary activity is ‘carrying’ other systems. System http://www.w3.org/ns/ssn/System ssn:System For all other system types.
@alexrobin Ultimately, the goal is to register application/sml+json
with IANA. However, it may take a while, therefore a note similar to the JSON-FG one would is ideal.
So by all means, please keep application/sml+json
. However, include a note that allows for the vnd
type as well until the registration is completed.
OGC-NA,
The document(s) titled "OGC API - Connected Systems - Part 1: Feature Resources" is/are now available for review by the OGC Naming Authority (OGC-NA) Subcommittee.
https://docs.ogc.org/DRAFTS/23-001r0.html
Please review the documents by 22:00 UTC on May 3, 2024 focusing on its conformance to OGC-NA policies.
OGC-NA policies can be found at https://www.ogc.org/standards/na
The most relevant policies are:
Let us know before then if there are any comments or objections to unanimous consent to its approval by the OGC-NA.
Regards,
OGC Staff