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] Commented: (OBIX-34) Section 3 - Simple editorial comments

    [ http://tools.oasis-open.org/issues/browse/OBIX-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34826#action_34826 ] 

Craig Gemmill  commented on OBIX-34:

155: TC discussion 2013-09-19 resolved this one
156-161: done
would like to retain REST - seek TC input...
158: referenced RFC and expanded acronym
164 - reworded
208-9: merged this text in
240-242: reworded similarly
244: reworded similarly to suggestion

> Section 3 - Simple editorial comments
> -------------------------------------
>                 Key: OBIX-34
>                 URL: http://tools.oasis-open.org/issues/browse/OBIX-34
>             Project: OASIS Open Building Information Exchange (oBIX) TC
>          Issue Type: Improvement
>          Components: OBIX 1.1 Specification
>    Affects Versions: oBIX 1.1 PR01
>         Environment: Toby Considine
>            Reporter: Toby Considine
>            Assignee: Craig Gemmill 
>            Priority: Minor
> 155: replace with The oBIX design philosophy recognizes a commonality of functionality of the components of all control systems while hiding the underlying mechanisms and protocols. To that end, OBIX relies on the principles in Table [n].
> 156-161. Replace bullet points with a named table.
> Should REST be replaced with CRUD? We can then add a sentence that suggests "For this document, we use REST operations as examples of CRUD operations in oBIX."
> 158: A better definition of URI, including translation of acronym. Reference to RFC 3986 would be good.
> 164: Remove "cleverly"
> 208-209L "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 to 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 document are for illustration only.
> Or, see detailed comment on URLs. Below.
> 240-242: Consider replacing first 3 sentences with:
> In oBIX, these patterns are modeled as a template object named the Contract.
> 244: Remove words "In Geek Speak". Replace with "Formally" if desired.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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