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.
Created by peter on 25/03/16.
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 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 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 "#".
The string representation of the id
Created by peter on 26/08/16.
Created by peter on 10/02/16.
Created by peter on 25/03/16.
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.
Created by peter on 10/02/16.
Created by peter on 26/08/16.
Created by peter on 26/08/16.