proposed update to 'Accessing Data through a Service Endpoint'

[smrgeoinfo]

Pull request proposes modification to recommendations for Accessing Data through a Service Endpoint, related to schemaorg/schemaorg#2340, schemaorg/schemaorg#2342.
Main points: the parameters for urlTemplate should be described in urlTemplate-input inside the sdo:target/sdo:EntryPoint object. Also includes richer example suggesting usage of the sdo:PotentialAction sdo:result and sdo:object.

[dr-shorthair]

Is SearchAction correct here? Maybe ConsumeAction or TransferAction ?

[smrgeoinfo]

I agree some other action type would likely make sense. In the original draft, searchAction was used because of the pattern for specifying the template parameters using query-input requred that 'query' is a property of the Action. See the comments in schema.org issues 2340 and 2342 (both of which the schema.org managers have 'backburnered' (ignored) by moving to suggestions-questions-brainstorming). Putting the inputs on the sdo:uriTemplate makes this a non-problem, so other action types could be used if they're more appropriate.

[rduerr]

If, as suggested above, other types of actions are useful (e.g., ConsumeAction or TransferAction from above) the the document needs to discuss that. I didn't see anything about that in the updated document.

I also note that many of the schema.org Action terms and their child actions that currently only involve people or organizations could actually be broadened in scope to include web services (e.g., createAction, interactAction, organizeAction, updateAction, etc.). May be worth discussion at an upcoming telecon.

[dr-shorthair]

@rduerr yes - if schema:Action is related to prov:Activity and obo:Process then there is a big mess of subclasses waiting to be recognised. Such as ObserveAction , SampleAction ...

[mbjones]

I amde this PR a draft as there seem to stil be outstanding discussion needed and changes to be made. So, retargeting to v 1.3 as well.

[smrgeoinfo]

Yes, good idea to table for a bit. recent testing with the https://search.google.com/test/rich-results indicates that contrary to the blogs about achema:Action, the parameters for a EntryPoint/urlTemplate need to be described using schema:query-input or the test/rich-results throws an error.

[smrgeoinfo]

I'd like to get this back in the pipe line to merge... I updated the text for distributions to treat direct download, web site selection apps (e.g. ERDDAP) and webAPI access.