-
Related to point 3 raised by Manu in PR #70
-
TL;DR
Enable "$ref" in the Data Schema Vocabulary Definitions of a TD. It will make things clearer and easier
JSON Schema content could be reused from existing API descriptions or defined in the T…
-
In section "7.3 Basic Interaction between WoT Thing and WoT Client via a Split Proxy" of the wot-security WG note draft, Proxy and Gateway are used interchangeably. The prose uses "gateway" while the …
-
When developing "third party" Factor code I prefer to work outside the Factor tree, as I don't want to "touch" the Factor distribution. I also do not want to touch the users' init files (there might n…
-
I feel that we are missing many new papers.
-
It would be useful if you could tag schema properties and parameters as being sensitive or PII specific so that these could be tagged appropriately in API docs.
galvo updated
5 months ago
-
Previously discussed in https://github.com/w3c/wot-thing-description/issues/165 and https://github.com/w3c/wot-thing-description/issues/230
The main rationale for making the security member mandato…
-
The Argo metadata field DEPLOYMENT_PLATFORM is currently populated in a wide variety of ways, with different entries for the same ship even at the same DAC. The C17 ICES platform code vocabulary is a…
-
# PLATFORM: OMNIBUS
EA's Contact and Customer Data Platform
## IDEAS
Get the Contacts Sorted - Everything we do revolves around our ability to communicate to the right people, the right message at …
-
Affiliation information is released through the multi-valued `eduPersonScopedAffiliation` attribute (`urn:oid:1.3.6.1.4.1.5923.1.1.1.9`).
> Specifies the person's affiliation within a particular se…