OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

obix message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (OBIX-156) 3.3 URIs -Normative?

     [ https://tools.oasis-open.org/issues/browse/OBIX-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated OBIX-156:

Replace text with "OBIX objects are named with Uniform Resource Indicators (URIs) as defined in [RFC3986]."

> 3.3 URIs -Normative?
> --------------------
>                 Key: OBIX-156
>                 URL: https://tools.oasis-open.org/issues/browse/OBIX-156
>             Project: OASIS Open Building Information Exchange (oBIX) TC
>          Issue Type: Bug
>          Components: OBIX 1.1 Specification
>    Affects Versions: OBIX 1.1 PR02
>         Environment: TAB Review
>            Reporter: Toby Considine
>            Assignee: William Cox
> "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."" 
> "

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]