Re: OPEN Specification)
Laverne Levenstein
An open specification is a specification created and controlled, in an open and fair process, by an association or a standardization body intending to achieve interoperability and interchangeability. An open specification is not controlled by a single company or individual or by a group with discriminatory membership criteria. Copies of Open Specifications are available free of charge or for a moderate fee and can be implemented under reasonable and non-discriminatory licensing (RAND) terms by all interested parties.
Many standards and specification are touted as open while falling short in practice. Many formal bodies charge per-copy fees for the document in order to defer the operating costs of the working group. This is rarely seen[by whom?] as negating the open status of the product, although free electronic distribution is usually seen as preferable. ADVANTAGES OF OPEN SPECIFICATIONAs there is no restriction among traders which have specific trademark, any traders can apply material satisfying open specifications, hence it creates a healthy competition among manufacturers and suppliers.Progress of work does not suffer due to short supply of materials.Similar kind of material can be procured at competitive rate.Reduction of transportation chargers and delivery time.Quality of material standardised which results in private parties select materials depending on its quality.
Through the Open Specifications program, Microsoft ishelping developers open new opportunities by making technical documents relatedto interoperability for certain popular Microsoft products available to viewand download at no charge.
All field names in the specification are case sensitive.This includes all fields that are used as keys in a map, except where explicitly noted that keys are case insensitive.
Throughout the specification description fields are noted as supporting CommonMark markdown formatting.Where OpenAPI tooling renders rich text it MUST support, at a minimum, markdown syntax as described by CommonMark 0.27. Tooling MAY choose to ignore some CommonMark features to address security concerns.
In contrast with the 3.0 specification, the format keyword has no effect on the content-encoding of the schema. JSON Schema offers a contentEncoding keyword, which may be used to specify the Content-Encoding for the schema. The contentEncoding keyword supports all encodings defined in RFC4648, including "base64" and "base64url", as well as "quoted-printable" from RFC2045. The encoding specified by the contentEncoding keyword is independent of an encoding specified by the Content-Type header in the request or response or metadata of a multipart body -- when both are present, the encoding specified in the contentEncoding is applied first and then the encoding specified in the Content-Type header.
Per the JSON Schema specification, contentMediaType without contentEncoding present is treated as if contentEncoding: identity were present. While useful for embedding text documents such as text/html into JSON strings, it is not useful for a multipart/form-data part, as it just causes the document to be treated as text/plain instead of its actual media type. Use the Encoding Object without contentMediaType if no contentEncoding is required.
The reasoning is to allow an additional layer of access control over the documentation.While not part of the specification itself, certain libraries MAY choose to allow access to parts of the documentation based on some form of authentication/authorization.
This promise applies to the identified version of thefollowing specifications. New versions of previously covered specificationswill be separately considered for addition to the list. In connection with thespecifications listed below, this Promise also applies to the required elementsof optional portions of such specifications.
On June 30, 2008, Microsoft published additionalspecifications for the Microsoft Word, Microsoft Excel, and MicrosoftPowerPoint binary file formats. Microsoft recommends that developers use themore recent documentation located on OpenSpecifications. See reference to these more recently published fileformats below.
Matrix defines a set of open APIs for decentralised communication,suitable for securely publishing, persisting and subscribing to dataover a global open federation of servers with no single point ofcontrol. Uses include Instant Messaging (IM), Voice over IP (VoIP)signalling, Internet of Things (IoT) communication, and bridgingtogether existing communication silos - providing the basis of a newopen real-time communication ecosystem.
Matrix is a set of open APIs for open-federated Instant Messaging (IM),Voice over IP (VoIP) and Internet of Things (IoT) communication,designed to create and support a new global real-time communicationecosystem. The intention is to provide an open decentralised pubsublayer for the internet for securely persisting andpublishing/subscribing JSON objects. This specification is the ongoingresult of standardising the APIs used by the various components of theMatrix ecosystem to communicate with one another.
Namespacing helps prevent conflicts between multiple applications andthe specification itself. Where namespacing is used, m. prefixes areused by the specification to indicate that the field is controlled bythe specification. Custom or non-specified namespaces used in the wildMUST use the Java package naming convention to prevent conflicts.
As an example, event types defined in the specification are namespacedunder the special m. prefix, however any client can send a customevent type, such as com.example.game.score (assuming the client hasrights to the com.example namespace) without needing to put the eventinto the m. namespace.
Additionally, the spec version may have arbitrary metadata applied to itwhen followed by a -. For example, v1.1-alpha. Usage of this is notstrictly specified but is intended for usage of pre-release builds of thespecification.
All API endpoints within the specification are versioned individually.This means that /v3/sync (for example) can get deprecated in favourof /v4/sync without affecting /v3/profile at all. A server supporting/v4/sync would keep serving /v3/profile as it always has.
An MSC is required to transition something from stable (the default) todeprecated. Once something has been deprecated for suitably long enough(usually 1 version), it is eligible for removal from the specificationwith another MSC.
A closed proprietary specification names, describes, and lists a single product or system. The specification may list only one manufacturer or a product by one manufacturer, or it could list the single manufacturer or product and provide a list of other manufacturers or products that are options (note that options differ from substitutions, which will be discussed later).
The correct use of alternate, option, and substitution is important when writing proprietary specifications as each has a fundamentally different meaning. An alternate is a product acceptable to the engineer or specification writer for which the bidder submits alternative pricing. An option is one of several, typically at least three, listed products in the specification. A substitution is a request to substitute one product for another product described in a specification. This could be in the form of a proposed substitution, where the specification do not name alternate products or manufacturers but allow submittal of substitute products, or a controlled substitution, where the desired products or systems are described and named, but substitute products with equal functionality may be submitted for review and approval.
If you choose a closed proprietary specification, note that this method limits competition, which may result in increased cost or long lead times. Additionally, the number of bidders with the required experience or certification to install the system may be limited. Also note that this method requires the engineer to specify the exact product that the owner wants, and any mistakes made when specifying the product are typically directly attributed to the engineer.
For federal projects, or projects requiring at least three options for each product to ensure fair and competitive bidding, use of a closed proprietary specification that names only one product is called sole sourcing. This may be required for some products or systems that require significant engineering work or compatibility with an existing system. You should be prepared to substantiate this decision.
An open specification that allows alternate products is similar to a closed specification in that it describes a very specific product and may name only a single product or manufacturer. However, open specifications include provisions that encourage the bidder to submit alternate or substitute products. If alternate products are requested, a list of the approved alternate products is included in the specification. The bidder must submit pricing for the named product and is permitted to submit alternate products from the list included in the specification, along with pricing information for the alternate products.
aa06259810