Hi ALTOers,
After some internal discussions, we are happy to update to WG that we are
finalizing the unified properties draft. And below are some key design
points:
---
1. Consider UP (Unified Property Map) service as a unified ATLO information
resources query mechanism
ALTO defines different types of information resources, which have different
representation formats. But every information resource can map some kinds
of entities to some kinds of properties. e.g., a network map can map ipv4
to pid. UP provides a query mechanism to allow clients to get different
ALTO information resources in the unified representation format.
2. Each UP resource declares a set of (resource_i, DT) -> { (resource_ok,
Pk) } mappings
Here, resource_ok MUST be either resource_i or this (the current UP
resource itself).
- When resource_ok == resource_i, the mapping means the client can query
the property mapping DT -> Pk defined by resource_i. e.g., "ipv4" -> "pid"
defined by "networkmap-1".
- When resource_ok == this, the mapping means the client can query entities
in the entity domain resource_i.DT, and UP will return the property P
defined in its own backend database.
The semantics of entity domain resource_i.DT MUST be defined in the IANA
registry of resource type of resource_i
The semantics of mapping DT -> Pk MUST be defined in the IANA registry of
resource type of resource_ok.
2.1. Use DT -> { (resource_ok, Pk) } as a shortcut of the aggregation
A UP resource can declare "ipv4" -> { ("net1", "pid"), ("net2", "pid") }.
It is equivalent to the outer join of ("net1", "ipv4") -> ("net1", "pid")
and ("net2", "ipv4") -> ("net2", "pid"). In this UP, "ipv4" indicates the
union of entity domain "net1.ipv4" and "net2.ipv4".
3. The client sends the UP query based on the declaration
The client queries a list of entities in resource_i.DT or DT, and a subset
of properties { (resource_ok, Pk) }.
---
We will finish the document revision in the next two days. In the meantime,
your comments and feedback are highly welcomed.
Thanks,
Jensen
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
