The distinction between "meta" information and "data" information is defined by the context in which it is used (the use case that demands it). (more on that in #76)
Let's consider the general SELFIE happy path use case.
As a Web user, I want to find all the information available for an environmental feature, so I can find what I'm looking for and retrieve it.
As we've dissected this use case we've embraced HTTP-Range 14 (303 redirects), we've embraced OGC-API Features (html landing pages for features), and we've embraced schema.org JSON-LD in a <script> tag of a landing page.
None of the above requires alternate media types. From the landing page, a human user or crawler with natural language tendencies is satisfied.
However, we recognize the potential to bring structure to data (including semantically enabled data) underlying the landing page content. I'll go one step further, SELFIE wouldn't be happening if we weren't layering this common 303->html+ Githubissues.
Githubissues is a development platform for aggregating issues.
The distinction between "meta" information and "data" information is defined by the context in which it is used (the use case that demands it). (more on that in #76)
Let's consider the general SELFIE happy path use case.
As a Web user, I want to find all the information available for an environmental feature, so I can find what I'm looking for and retrieve it.
As we've dissected this use case we've embraced HTTP-Range 14 (303 redirects), we've embraced OGC-API Features (html landing pages for features), and we've embraced schema.org JSON-LD in a
<script>tag of a landing page.None of the above requires alternate media types. From the landing page, a human user or crawler with natural language tendencies is satisfied.
However, we recognize the potential to bring structure to data (including semantically enabled data) underlying the landing page content. I'll go one step further, SELFIE wouldn't be happening if we weren't layering this common 303->html+ Githubissues.