RE: ACTION-326, was: Specification modularization of the SOSA/SSN terms

I agree – this is much nicer, and more user-focussed.

It also has what I think is the desired side-effect of shifting the ssn-only components down in the list. They are important of course, but only to people who will be looking past the surface.

I will be redrawing the figures, but first trying to put OWL-Time to bed.

Simon

From: Krzysztof Janowicz [mailto:janowicz@ucsb.edu]
Sent: Thursday, 20 April, 2017 05:20
To: Maxime Lefrançois <maxime.lefrancois@emse.fr>; SDW WG Public List <public-sdw-wg@w3.org>
Subject: Re: ACTION-326, was: Specification modularization of the SOSA/SSN terms

IMHO, these look excellent!

There are a few tiny details that remain to be discussed such as ObservableProperty compared to the other properties and their grouping with Observation versus FOI, respectively, but I would suggest to leave everything as is for now.

Best,
Jano


On 04/19/2017 03:47 AM, Maxime Lefrançois wrote:
Dear all,

I just closed action https://www.w3.org/2015/spatial/track/actions/326

it consisted in proposing a new grouping and ordering of the terms in the specification document, according to my previous email and the changes proposed in the meeting yesterday. Also as Raul proposed, SOSA terms are also introduced before SSN terms.

Below is the result, it is now in http://w3c.github.io/sdw/ssn/ .

Best,
Maxime

4.3.1. Observations

sosa:ObservableProperty
sosa:Observation
sosa:observedProperty
sosa:phenomenonTime
ssn:qualityOfObservation
sosa:Sensor
sosa:observes
sosa:isObservedBy
sosa:madeObservation
sosa:madeBySensor
ssn:Stimulus
ssn:isProxyFor
ssn:wasOriginatedBy
ssn:detects


4.3.2. Actuations

sosa:ActuatableProperty
sosa:Actuation
sosa:actsOnProperty
sosa:isActedOnBy
sosa:Actuator
sosa:madeActuation
sosa:actuationMadeBy

4.3.3. Sampling

sosa:Sample
sosa:hasSample
sosa:isSampleOf
sosa:Sampling
sosa:Sampler
sosa:hasResultingSample
sosa:isSamplingResultOf
sosa:madeSampling
sosa:madeBySampler

4.3.4. Features of Interest and thir Properties

sosa:FeatureOfInterest
sosa:hasFeatureOfInterest
sosa:isFeatureOfInterestOf
ssn:Property
ssn:hasProperty
ssn:isPropertyOf
ssn:forProperty

4.3.5. Results

sosa:Result
sosa:hasResult
sosa:isResultOf
sosa:hasSimpleResult
sosa:resultTime

4.3.6. Procedures

sosa:Procedure
sosa:usedProcedure
ssn:implements
ssn:implementedBy
ssn:hasInput
ssn:Input
ssn:hasOutput
ssn:Output

4.3.7. Systems and their Deployment

sosa:Platform
sosa:hosts
sosa:isHostedBy
ssn:System
ssn:hasSubSystem
ssn:Deployment
ssn:deployedSystem
ssn:hasDeployment
ssn:deployedOnPlatform
ssn:inDeployment

4.3.8. Conditions

ssn:inCondition
ssn:Condition


4.3.9. System Capabilities

ssn:hasSystemCapability
ssn:SystemCapability
ssn:hasSystemProperty
ssn:SystemProperty
ssn:MeasurementRange
ssn:ActuationRange
ssn:Accuracy
ssn:DetectionLimit
ssn:Drift
ssn:Frequency
ssn:Latency
ssn:Precision
ssn:Resolution
ssn:Repeatability
ssn:ResponseTime
ssn:Selectivity
ssn:Sensitivity


4.3.10. Operating Ranges

ssn:hasOperatingRange
ssn:OperatingRange
ssn:hasOperatingProperty
ssn:OperatingProperty
ssn:MaintenanceSchedule
ssn:OperatingPowerRange


4.3.11. Survival Ranges

ssn:hasSurvivalRange
ssn:SurvivalRange
ssn:hasSurvivalProperty
ssn:SurvivalProperty
ssn:SystemLifetime
ssn:BatteryLifetime


Le mar. 18 avr. 2017 à 04:13, Maxime Lefrançois <maxime.lefrancois@emse.fr<mailto:maxime.lefrancois@emse.fr>> a écrit :
Dear all,

Wiki page https://www.w3.org/2015/spatial/wiki/Terms describes the grouping and ordering of SOSA and SSN terms in the specification.

Having it that way was useful to ensure consistency during the last edits, however in the spec I think that we should consider grouping terms in such a way that they could be pictured easily in diagrams.

What would you think of these main sections and order of terms? I tried to use some kind of "depth first search algorithm" to introduce them progressively.


1. Features of Interest and Properties

sosa:FeatureOfInterest
ssn:Property
ssn:hasProperty
ssn:isPropertyOf
ssn:forProperty

2. Procedures, their execution, things that make those executions

sosa:Procedure
ssn:hasInput
ssn:Input
ssn:hasOutput
ssn:Output

sosa:Result
sosa:hasResult
sosa:isResultOf
sosa:hasSimpleResult
sosa:resultTime

ssn:implements
ssn:implementedBy
sosa:usedProcedure
sosa:hasFeatureOfInterest
sosa:isFeatureOfInterestOf


3. Observations

sosa:ObservableProperty

ssn:Stimulus
ssn:isProxyFor

sosa:Observation
sosa:observedProperty
ssn:wasOriginatedBy
sosa:phenomenonTime
ssn:qualityOfObservation

sosa:Sensor
sosa:observes
sosa:isObservedBy
ssn:detects
sosa:madeObservation
sosa:madeBySensor

4. Actuation

sosa:ActuatableProperty

sosa:Actuation
sosa:actsOnProperty
sosa:isActedOnBy

sosa:Actuator
sosa:madeActuation
sosa:actuationMadeBy


5. Sampling

sosa:Sample
sosa:hasSample
sosa:isSampleOf

sosa:Sampling
sosa:madeSampling
sosa:madeBySampler

sosa:Sampler
sosa:hasResultingSample
sosa:isSamplingResultOf


6. Systems and their deployment

ssn:System
sosa:Platform
sosa:hosts
sosa:isHostedBy
ssn:Deployment
ssn:deployedSystem
ssn:hasDeployment
ssn:deployedOnPlatform
ssn:inDeployment


7. Conditions

ssn:inCondition
ssn:Condition


8. System Capabilities

ssn:hasSystemCapability
ssn:SystemCapability
ssn:hasSystemProperty
ssn:SystemProperty
ssn:MeasurementRange
ssn:ActuationRange
ssn:Accuracy
ssn:DetectionLimit
ssn:Drift
ssn:Frequency
ssn:Latency
ssn:Precision
ssn:Resolution
ssn:Repeatability
ssn:ResponseTime
ssn:Selectivity
ssn:Sensitivity


9. Operating Ranges

ssn:hasOperatingRange
ssn:OperatingRange
ssn:hasOperatingProperty
ssn:OperatingProperty
ssn:MaintenanceSchedule
ssn:OperatingPowerRange


10. Survival Ranges

ssn:hasSurvivalRange
ssn:SurvivalRange
ssn:hasSurvivalProperty
ssn:SurvivalProperty
ssn:SystemLifetime
ssn:BatteryLifetime

Best,
Maxime





--

Krzysztof Janowicz



Geography Department, University of California, Santa Barbara

4830 Ellison Hall, Santa Barbara, CA 93106-4060



Email: jano@geog.ucsb.edu<mailto:jano@geog.ucsb.edu>

Webpage: http://geog.ucsb.edu/~jano/


Semantic Web Journal: http://www.semantic-web-journal.net