I propose to use following namespace format to distinguish between type / interface versions and to provide capability for using vendor specific extensions.
All META Web concept specific types should be under package:
meta-<version>.*
Namespaces also should support aliases such as:
@meta
for latest META Web core specification:
@meta.collection
instead of
meta-dev0_1.collection
This will be useful in a phase of core development. Later when core specifications will be stable developers can then use alias everywhere because specifications should be backwards compatible.
Also vendor specific namespaces can be used. For example some company will need very specific extension to META Web so they can extend their browser / client and use custom namespace:
cz.cryonix.hardware.robot.motorControl
Namespaces should be used when defining
- document type
- data type
- schema type
- resources interface
- etc