Stephen Gadd
Stephen Gadd
Agreed. We're not really looking at _precision_ but rather at _granularity_. Would that do? In my experience granularity is _such_ a common question when dealing with geodata that I think...
Thanks, Ryan. Yes, `@id` is the logical way to go. I've updated [this](https://github.com/docuracy/Locolligo/blob/main/schemas/LP.json#:~:text=%7D%2C-,%22geometries%22%3A%20%7B,-%22description%22%3A%20%22***TO%20DISCUSS) draft JSON Schema. --- Regarding RFC 7946, I don't think this proposal interferes with the semantics of...
I think that would be determined by the nature of the items in the dataset: this proposal has arisen only because we are creating sets of non-place objects (e.g. archaeological...
The primary problem we faced with implementing Linked Traces was in providing resolvable references to the _many_ thousands of geo-points in our datasets: it is both impractical and of extremely...
Ah, I didn't spot this, and have drafted an as-yet somewhat [unorthodox version here](https://github.com/docuracy/Locolligo/blob/main/schemas/LP.json) that includes various comments and proposals. At @kgeographer's invitation I'm going to add the proposals as...
My understanding is that this property provides a means for recording an item's real-world label in situations where that label does not exactly match the label provided by the vocabulary...
Thanks, Ryan - I think your understanding, succinctly and elegantly explained above, is probably shared by most of the members of this group. I don't want my suggestions to be...
Ah, so they do - but these smaller examples do not: https://github.com/LinkedPasts/linked-places-format#geometry-required https://github.com/LinkedPasts/linked-places-format#relations-optional
[UPDATED] I wondered about that too, mainly to improve the human-readability/comprehension. What we're looking for (in addition to the existing specification so as to preserve backward-compatibility) is a single-string expression...
Yes, I like your wariness, Ryan. However, under this proposal 'complicated needs' would still be met by the existing `when` specification: the idea is to offer an alternative to that...