[OBIX-148] 2.1 Design Philosophy - OASIS Technical Committees Issue Tracker

XML

Word

Printable

Resolution:

Hide

I think here in the encodings it is about the fact that the XML syntax is not affected through the contracts. As the OBIX object representation wil always stick to the basic object model.

Anyways, I think the last sentence can be avoided since it does not provide any additional benefit to the reader.

Show
I think here in the encodings it is about the fact that the XML syntax is not affected through the contracts. As the OBIX object representation wil always stick to the basic object model. Anyways, I think the last sentence can be avoided since it does not provide any additional benefit to the reader.

"2.1 Design Philosophy reads in part:

- - - - Higher level semantics are captured via contracts. Contracts ""tag"" an object with a type and can be applied dynamically. This is very useful for modeling systems which are dynamically configured in the field. What is important is that contracts are optionally understood by clients. Contracts do not affect the XML syntax nor are clients required to use them for basic access to the object tree. *Contracts are merely an abstraction which is layered cleanly above the object tree and its fixed XML syntax.*

The last sentence appears to be a direct contradiction of:

OBIX 1.1 3.5 Contracts

Terminology, especially terminology central to a standard, should be used consistently across all parts of the standard."