-
Notifications
You must be signed in to change notification settings - Fork 127
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
[TF-AP/Thing API] ThingFilter server attribute #50
Comments
@ClaesNilsson after Nice F2F Meeting, we need to refine this more. We agreed that the filter parameters are different for various discovery technologies. I see these options on how we can proceed on this:
filter = {
"ble": {
"proximity": ...
} ,
"sparql": {
"query": ...
}
}; What do you think? |
I'm in favor of the first. Considering an example: let filter = { "query" : "...", "endpoint" : "..." };
ThingRequest("sparql",filter).start().then( (things) => console.dir(things) );
let otherfilter = { "foo" : bar"" };
ThingRequest("somethingelse",otherfilter).start().then( (things) => console.dir(things) ); |
Continuing at w3c/wot-scripting-api#226 . Closing |
So this is the address, URL, of a server containing a directory of "things", e.g. an IETF CoRE Resource Directory?
The text was updated successfully, but these errors were encountered: