- From: Kathi Schleidt <kathi@datacove.eu>
- Date: Thu, 3 Oct 2024 15:17:01 +0200
- To: Rob Atkinson <ratkinson@ogc.org>, Luís Moreira de Sousa <luis.moreira.de.sousa@tecnico.ulisboa.pt>
- Cc: Robert Warren <warren@glengarryag.com>, SDW WG <public-sdw-wg@w3.org>
- Message-ID: <d0123336-1b94-4a68-aac8-a9fe1398e5da@datacove.eu>
Hi all, based on the feedback received, I'll try and update all examples to / in place of # My next question is if we keep all the examples with the FoI-Specific ObsProps, or if we adjust them to have neutral ObsProps. Have we had any feedback from Maxime on this? To my understanding, he's the proponent of the FoI-Specific ObsProps. I'll try and evaluate the entire batch of examples to see if anything is redundant (to my memory they're not), or if we'd need any additional examples. However, I'll need help in formulating them, as I'm not an RDF/TTL expert, and simply don't have the resources to become one at present. :) Kathi On 30.09.2024 23:41, Rob Atkinson wrote: > In addition to QC, the questions we need to answer are: > > 1. Are the examples we need in place in-line? > 2. Are any examples in place not necessary and could be move to appendix > 3. Are the examples the best (specifically can we provide best > practice guidance for observed properties using property descriptions > of some sort (classes or SKOS - punning meaning we could use a URI and > have either or both) > 4. Can the examples be cleaned and trimmed at all- e.g. suppressing > common namespace prefixes we define once - e.g. > https://github.com/w3c/sdw-sosa-ssn/issues/246 > > Note the validation of example files is now available at > https://opengeospatial.github.io/ogcapi-sosa/bblock/ogc.sosa.properties.spec-examples > - and is one PR away from passing > https://github.com/w3c/sdw-sosa-ssn/pull/247 > > > Rob Atkinson > *Senior Research Engineer * | Open Geospatial Consortium (OGC) > Mobile: +61 419 202973 > ratkinson@ogc.org <mailto:ratkinson@ogc.org>| ogc.org > <http://ogc.org/>| @opengeospatial > > > > Sign up for OGC News > <https://ogc.us4.list-manage.com/subscribe?u=704e02f81107a6caab1568067&id=4e4528fd9d> > > > On Mon, Sep 30, 2024 at 7:26 PM Luís Moreira de Sousa > <luis.moreira.de.sousa@tecnico.ulisboa.pt> wrote: > > Dear all, > > on this topic there have been objective recommendations by the W3C: > https://www.w3.org/TR/cooluris/#choosing > > Hashes are fine in small graphs, like an ontology, but complicate > matters in larger graphs. Moreover, the trend towards ReST also > benefits the forward slashes. > > Regards. > > -- > Luís Moreira de Sousa > > INESC-ID > Instituto Superior Técnico > University of Lisbon > > On Mon, 2024-09-30 at 18:53 +1000, Rob Atkinson wrote: > > Whilst all legal URI forms are valid, the inconsistency is > > unhelpful, and these particular examples are idiosyncratic and > > inconsistent with the original O&M model of a GF_Property. > > SOSA is more agnostic, but real systems are going to need to have an > > identifiable architecture pattern for properties. So can we > > decide which style of examples we need to show - and push the others > > to a register of examples? > > > > > > Rob Atkinson > > Senior Research Engineer | Open Geospatial Consortium (OGC) > > Mobile: +61 419 202973 > > ratkinson@ogc.org | ogc.org <http://ogc.org> | @opengeospatial > > > > > > > > Sign up for OGC News > > > > > > On Sat, Sep 28, 2024 at 12:11 AM Robert Warren > > <warren@glengarryag.com> wrote: > > > It strikes me as wrong. -rhw > > > > > > On Fri, Sept 27, 2024, 6:08 a.m. Kathi Schleidt > <kathi@datacove.eu> > > > wrote: > > > > > > > > Hi all, > > > > going through and analysing the examples for SOSA/SSN, I've > > > > noticed two different notations, sometimes used interchangeably. > > > > Has to with associations from a class, I see both '/' and '#' > > > > being used, at times within the same example. See C.4 Tree > height > > > > measurement, where the ObsProp is tightly bound to the FoI. Here > > > > we find both versions, e.g.: > > > > * <tree/124/height> > > > > * <tree/124#height> > > > > Does the # version convey some subtly of meaning that I'm not > > > > aware of, or are these 2 syntax options just being used > > > > interchangeably? If they're the same, I'd be for using / > > > > everywhere > > > > > > > > :? > > > > Kathi > > > > > > > > On 24.09.2024 12:40, Simon Cox wrote: > > > > > > > > > > > > > > > > > > i.e. in 24 hours and 20 minutes time > > > > > > > > > > > > > > > > > > > > > > > > > Agenda and rolling notes > > > > > here: > https://docs.google.com/document/d/15TBmYhgRjncdd_bvmTKyg > > > > > CD8aIhQo1-Tkg3eOKjYNTw/edit > > > > > > > > > > > > > > > > > > > > > > > > > Highlights: > > > > > > > > > > 1. Completion plan - Triage topics so we can finish this > > > > > century > > > > > 2. Issues > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Cheers - Simon > > > > > > > > > > > > > > > dr.shorthair@pm.me > > > > > https://github.com/dr-shorthair > > > > > > > > > > +61 403 302 672 > > > > > > > > > > > > > > > On Boonwurrung land > > > > > > > > > > > > > > > > > > > > Sent with Proton Mail secure email. > > > > > > > > > > > > > > > -- *Katharina Schleidt* CEO, Data Modeler, Data Networking Expert ** *DataCove e.U.*, Robert Hamerlingg. 1/14, 1150 Vienna, Austria Tel: Mobile: Skype: E-Mail: Web: +43 (1) 89 234 26 +43 (650) 89 234 26 Kathi Schleidt Kathi@DataCove.eu www.DataCove.eu ** *FAIR information cube*, Horizon EU project, https://doi.org/10.3030/101059238 <https://doi.org/10.3030/101059238> E-mail: Web: fairicube@nilu.no www.fairicube.eu <http://www.fairicube.eu> In the twenty-first century censorship works by flooding people with irrelevant information. -- Homo Deus, Yuval Noah Harari Do what you can, when you can, because you can -- Anonymous, paraphrasing Theodore Roosevelt Please note that the fact that you have received this email implies that your mail address is stored on my system's address book. If this bothers you, please get in touch, and I will delete your information.
Received on Thursday, 3 October 2024 13:17:12 UTC