-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Including common Non SFA functions #536
base: geosparql-1.3
Are you sure you want to change the base?
Changes from all commits
09f1f93
bbf34f7
9e74ce6
425469b
bdd054d
fe41ae9
eef73d7
d15b067
2ae2822
cd76660
f580f57
699615f
e274933
fc0555b
b4f6b14
456a429
402ab7f
fd7ec1d
54562ce
2672416
b40f337
c5cbafb
8509daa
ef6106a
51b95c3
2bc05f3
6cfe262
6e13ea7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -57,6 +57,12 @@ The following IRI namespace prefixes are used throughout this document: | |
|
||
All of these namespace prefixes in the previous section resolve to resources that contain their namespace content except for `eg:` (`http://example.com/`), which is used just for examples, and `ogc:` (`http://www.opengis.net/`), which is used in requirement specifications as a placeholder for the geometry literal serialization used in a fully-qualified conformance class, e.g. http://www.opengis.net/ont/geosparql#wktLiteral[`+<http://www.opengis.net/ont/geosparql#wktLiteral>+`]. | ||
|
||
=== Data Types for Spatial Aggregate Functions | ||
|
||
In this specification we use the placeholder URI ogc:geomLiteral to describe any geometry literal that is defined in this specification. | ||
To express a list of such literals, for example as input parameters for spatial aggregate functions, we use the notation ogc:geomLiteral[]. | ||
We do not define the order of ogc:geomLiteral[]. The order is to be determined by implementers. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't understand that. A "list" is ordered, so how do you mean implementers can change it? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. A list is ordered. But how it is ordered, e.g., by URI alphabetically or not at all, should be up to the implementers. |
||
|
||
=== RDF Serializations | ||
|
||
Three RDF serializations are used in this document. Terse RDF Triple Language (turtle) <<TURTLE>> is used for RDF snippets placed within the main body of the document, and turtle, JSON-LD <<JSON-LD>> & RDF/XML <<RDFXML>> is used for the examples in <<GeoSPARQL Examples>>. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't you need to put ogc:geomLiteral[] in some code markers? (I'm not familiar with adoc)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not think so. However, should we find it disturbing we can still correct the styling later on