Uploaded image for project: 'OASIS Open Building Information Exchange (oBIX) TC'
  1. OASIS Open Building Information Exchange (oBIX) TC
  2. OBIX-156

3.3 URIs -Normative?

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: OBIX 1.1 PR02
    • Fix Version/s: OBIX 1.1 WD27
    • Component/s: OBIX 1.1 Specification
    • Labels:
      None
    • Environment:

      TAB Review

    • Proposal:
      Hide

      Replace text with the following:

      OBIX identifies objects (resources) with Uniform Resource Indicators (URIs) as defined in [RFC3986]. This is a logical choice, as a primary focus of OBIX is making information available over the web. Naming authorities manage the uniqueness of the first component of a URI, the domain name.

      Conforming implementations MUST use [RFC3986] URIs to identify resources. Conforming implementations MAY restrict URI schemes and MUST indicate any restrictions in their conformance statement.

      Typically, http-scheme URIs are used, but other bindings may require other schemes. Note that while https is technically a different scheme from http [RFC2818, RFC5785] they are typically used interchangeably with differing security transport. The commonly used term URL is shorthand for what it now an http-scheme URI.

      Show
      Replace text with the following: OBIX identifies objects (resources) with Uniform Resource Indicators (URIs) as defined in [RFC3986] . This is a logical choice, as a primary focus of OBIX is making information available over the web. Naming authorities manage the uniqueness of the first component of a URI, the domain name. Conforming implementations MUST use [RFC3986] URIs to identify resources. Conforming implementations MAY restrict URI schemes and MUST indicate any restrictions in their conformance statement. Typically, http-scheme URIs are used, but other bindings may require other schemes. Note that while https is technically a different scheme from http [RFC2818, RFC5785] they are typically used interchangeably with differing security transport. The commonly used term URL is shorthand for what it now an http-scheme URI.

      Description

      "3.3 URIs reads:


              • No architecture is complete without some sort of naming system. In OBIX everything is an object, so we need a way to name objects. Since OBIX is really about making information available over the web using XML, it makes sense to leverage the URI (Uniform Resource Identifier) as defined in RFC3986. URIs are the standard way to identify ""resources"" on the web.

      Since OBIX is used to interact with control systems over the web, we use the URL to identify each resource. Just as we assume an XML encoding and a REST binding for all examples in this document, so too we assume a URL using the Hypertext Transfer Protocol (URLs beginning with http beginning with HTTP. This is not meant to forbid the use of secure transfer (https or of other protocols (ws. Neither are the examples are meant to forbid the use of alternate ports. The URLs in examples in this specification are for illustration only. Often URIs also provide information about how to fetch their resource - that's why they are often called URLs (Uniform Resource Locator). From a practical perspective if a vendor uses HTTP URIs to identify their objects, you can most likely just do a simple HTTP GET to fetch the OBIX document for that object. But technically, fetching the contents of a URI is a protocol binding issue discussed in later chapters.

      The value of URIs are that they have numerous defined and commonly understood rules for manipulating them. For example URIs define which characters are legal and which are illegal. Of great value to OBIX is URI references which define a standard way to express and normalize relative URIs. In addition, most programming environments have libraries to manage URIs so developers don't have to worry about managing the details of normalization.

      I can't find any normative language in 3.3 URIs.

      Suggest replacing present text with a simple declarative statement:

      ""OBIX objects are named with URIs as defined in RFC3986.""
      "

        Attachments

          Activity

            People

            • Assignee:
              toby.considine Toby Considine (Inactive)
              Reporter:
              toby.considine Toby Considine (Inactive)
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: