This is the absolute version of a fragment id.
This is the absolute version of a fragment id. It is prepended with its root's achor. E.g. "http://atomicbits.io/schema/User.json#/some/schema/path/license"
The root of this absolute fragment id.
The path that composes the fragment id.
Created by peter on 10/02/16.
Created by peter on 26/08/16.
Created by peter on 10/02/16.
Created by peter on 19/08/16.
A fragment id identifies its schema uniquely by the schema path (JSON path in the original JSON representation) from its nearest root schema towards itself.
A fragment id identifies its schema uniquely by the schema path (JSON path in the original JSON representation) from its nearest root schema towards itself. In other words, the fragment id should always match this schema path and is redundant from that point of view. It is of the form "#/some/schema/path/license"
The path that composes the fragment id.
The base class for all Id's.
Created by peter on 26/08/16.
In:
In:
/books: type: { searchableCollection: { queryParamName: title, fallbackParamName: digest_all_fields } } get: is: [ secured: { tokenName: access_token }, paged: { maxPages: 10 } ]
these are the MergeSubstitutions:
MergeSubstitution(tokenName, access_token) MergeSubstitution(maxPages, 10)
and the MergeApplications:
MergeApplication(secured, ...) MergeApplication(paged, ...)
Created by peter on 10/02/16.
Created by peter on 25/05/17.
A native id is like a relative id, but it is not expected to have an absolute parent id.
A native id is like a relative id, but it is not expected to have an absolute parent id. NativeId's should not be used in json-schema definitions. They have been added to cope with the native RAML 1.0 types that either have an NativeId or an ImplicitId.
We cannot use the RootId concept here, because a NativeID has a free format whereas the RootId is a json-schema concept that has to meet strict formatting rules.
Created by peter on 10/02/16.
Created by peter on 14/05/17.
Created by peter on 10/02/16.
A relative id identifies its schema uniquely when expanded with the anchor of its root schema.
A relative id identifies its schema uniquely when expanded with the anchor of its root schema. Its root schema is its nearest parent that has an absolute id. A schema with a relative id is the root for its child-schemas that don't have an absolute or relative id. A relative id is of the form "contact/ShippingAddress.json".
The string representation of the id
Created by peter on 10/02/16.
Created by peter on 25/05/17.
Created by peter on 10/02/16.
Created by peter on 26/08/16.
An absolute id uniquely identifies a schema.
An absolute id uniquely identifies a schema. A schema with an absolute id is the root for its child-schemas that don't have an absolute or relative id. An absolute id is of the form "http://atomicbits.io/schema/User.json" and often it ends with a "#".
Created by peter on 26/08/16.
Created by peter on 10/02/16.
Created by peter on 26/09/16.
Created by peter on 12/12/16.
UniqueId's are Id's that are expected to be unique by value within a RAML document.
An implicit id marks the absense of an id.
An implicit id marks the absense of an id. It implies that the schema should be uniquely identified by the schema path (JSON path in the original JSON representation) from its nearest root schema towards itself. In other words, an implicit id is a fragment id that hasn't been set.
It is not a UniqueId since may items can have ImplicitId's.
Created by peter on 10/02/16.
Created by peter on 25/03/16.
Placeholder object for an ID that points to nowhere.
Created by peter on 26/08/16.
Created by peter on 26/08/16.