Where We Fit with TEG Requirements...
Extensible (Position) Coordinates - we do this with ISO standards and industry engineering expertise (spec built)
Extensible (Location) Spatial reference systems - we do this with market accepted approaches (spec built)
Possessor - (metadata) we do this with ISO standards for content definition via catalogs (spec built)
Subscriber - we need help
Scalability - need requirements for taking API’s to“lite” state
Data Formats - our API’s address this comprehensively (specs built)
Privacy - we know this is a big issue we want to work with others in developing the right mechanism for use of position information
QoP - we agree this needs user requirements definition