Default Behavior of URI Dereferencing / Alternates / Landing Page

[dblodgett-usgs]

Discuss and close out of "Default Behavior of URI Dereferencing" problem.

Use this issue to discuss. Use this wiki page

[dblodgett-usgs]

I drafted what I think is a reasonable start on this here: https://github.com/opengeospatial/ELFIE/wiki/Default-Response-to-Get-Alternate-Representations Please help improve word choice and technical content.

[rob-metalinkage]

This looks pretty good to me. I'd suggest adding that the wider topic is on the table in standards space at https://www.w3.org/2017/dxwg

[dblodgett-usgs]

Thanks! Added a link to that in the first paragraph.

[abhritchie]

The first few mentions of 'non-information resources' aren't quite right. These are the real world features, the subject here is non-information resource identifiers. Change that and the first two sentences make much more sense.

[abhritchie]

Some missing words in sentence 3? My additions in bold:

There is a basic conundrum with non information resource identifers in that there can only be one default response when derefencing a URI and only one member of a distributed system can be the source of that response.

[abhritchie]

I'm not sure what you're saying when you say Range 14 and Cool URIs provide a basis for the conundrum. That they articulate it?

[abhritchie]

There's some other editorial nits that only need to be picked if they are still there when the document review is complete. Otherwise, I think this hits the spot, try to say any more and we'll burrow down the slippery can of elephants.

[dblodgett-usgs]

Incorporated your suggestions. Definitely some words in there that I was leaving out.

[dblodgett-usgs]

We need to add some concrete examples in this section. Some discussion of that on a telecom.

See notes from discussion on 10-4 here: https://docs.google.com/document/d/1DFYAgydFY8vQcrqY_axXB-vh8mHlg_-BqWQUvReRiyo/edit

Related to discussion of multiple representation in: https://github.com/opengeospatial/ELFIE/blob/master/docs/json-ld/xample-elf-tsml-observation-byref.json

[rob-metalinkage]

suggest introduce as "Non-information resources" to show the term scope, and use the hyphen as per w3c

I find issue 6 wording confusing - i dont get why optional/mandatory is related to "where can an agent find them"

There are multiple default resources, currently negotiated by http headers such as locale, mime type and agent type - these are all expected to return the same information model however.

Link to DXWG should perhaps explicitly mention that versioning and profile-based negotiation are the key points of overlap.

[dblodgett-usgs]

Needs to be a section in the engineering report. Will close this issue for now.