WoWAPI

Spatial Asset Provisioning

Core Requirements and Feature

Core requirements enabled with simple, proven and robust HTTP 1.1 feature plus some modern extensions.

Requirements	Feature
Data Security	E2E authorization for data provisioning and validation ( HTTP 1.1 authentication + Modern SSO implementation )
Data Change	Essential indication of data change ( HTTP 1.1, etag )
Multi-format	Single- und Multi-format requests with and without content negotiation ( HTTP 1.1: Content Negotiation )

Model type definition

We expect the data to comply with the RFC2077 model definition

• Orthogonal space
  • Orthogonal system
  • Spatial (3 or more) and temporal dimensions
• Model structure
  • Models are composed of Objects
  • Objects are instantiated/transformed elements
  • Elements are local or extern linked data with aggregatio sematic (e.g. referencing a VRML and IGES )
• Structured Data
  • Multidimensional structures
  • Conversion should be structure preserving

Model type registration

There is a gowing number of IANA Registration for model types which enable the multi format support.

Name	IANA Registration	In domain Links
3mf	model/3mf
e57	model/e57
gltf-binary	model/gltf-binary
gltf+json	model/gltf+json
JT	model/JT	jt
iges	model/iges
mtl	model/mtl
obj	model/obj
prc	model/prc
step	model/step	Any model format
step+xml	model/step+xml	Any model format
step+zip	model/step+zip	Any model format
step-xml+zip	model/step-xml+zip	Any model format
stl	model/stl
u3d	model/u3d
vnd.usda	model/vnd.usda	usd
vnd.usdz+zip	model/vnd.usdz+zip	usd
x3d-vrml	model/x3d-vrml	Any model format
x3d+fastinfoset	model/x3d+fastinfoset	Any model format
x3d+xml	model/x3d+xml	Any model format
las	😦
glExtRef	😦	gltf
SPZ	😦

Optional Feature

The following API feature are option and only provided in some implementation

Additon asset aspects

Additional information provided in a separate data package

• Generator
• Copyright
• etag
• Formats
• 3D volume
• GeoPose

Data Fragment adresssing

Links inside the (model) domain and fragments of data. URI Fragment standards allow to address sub-data

• W3C Media Frment URI: Spatially-, temporally- and structure-based addressing schema
  • example.com/media/movie.mpg#xywh=100,100,10,10&t=10,20
  • example.com/media/movie.mpg#id=cap
• Open Opportunity: Missing “Model Fragment URI”: Spatially-, temporally- and structure-based addressing
  • example.com/model/434/#xyzwhz=100,100,100,20,20,20&t=10,20
  • example.com/model/434/#include=node.tire

OpenAPI spec

Source

API

Preview

Preview

This site is open source. Improve this page.