Alias #5
Description
In order to allow existing vocabularies to be used and referenced as HTTP URIs, I propose that a specific container be allowed, defining aliases.
This is a poorer version of prefixing, it is not as rich or widely applicable, but it does enable BALD datasets to also conform to existing conventions.
A designated aliases Subject shall contain attributes and nothing else. Each attribute defines:
- an alias, the attribute name
- a value, the http URI which is used to replace the alias wherever it is found.
Any container may declare aliases, using a (not aliased) attribute: bald:isAliasedBy referencing a Subject.
I also propose that aliases never be overridden, an alias conflict should always raise an exception.
This protects aggregated data collections from conflicts in aliasing which would require careful intervention to resolve.