This work-in-progress Solid client-client set of protocols defines objects and rules to make interoperable apps to manage the activities of en entity that provides goods and/or services like a business or enterprise.
The Solid Goods/Services Provider (GSP) [solid-gsp] is a object in a Solid storage which holds data
about an entity that provides goods and/or services.
3.1. Access rights
By default, the GSP container is private. When one wants to make the GSP public, private properties can still be defined in a separated private document, let’s says $ROOT/index-private, linked with the public $ROOT/index document using the rdfs:seeAlso predicate.
3.2. Discovery
Type indexes is the recommended mechanism to discover Solid GSP. The RDF class to register an instance of a Solid GSP is dfc-b:Enterprise. Type indexes MUST only register the GSPs owned by the WebId owner. See [type-indexes].
Conformance
Document conventions
Conformance requirements are expressed
with a combination of descriptive assertions
and RFC 2119 terminology.
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”
in the normative parts of this document
are to be interpreted as described in RFC 2119.
However, for readability,
these words do not appear in all uppercase letters in this specification.
All of the text of this specification is normative
except sections explicitly marked as non-normative, examples, and notes. [RFC2119]
Examples in this specification are introduced with the words “for example”
or are set apart from the normative text
with class="example",
like this:
This is an example of an informative example.
Informative notes begin with the word “Note”
and are set apart from the normative text
with class="note",
like this: