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-1) UML diagram and text needs clarification line 269

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

Markus Jung commented on OBIX-1:

- For the types maybe the xs: namespace and according XML schema types can be used to define the attribute type
- I will provide an updated XML schema since some other bugs appeared.
- The Val type has currently rather limited purpose. In an object oriented language it could be useful to define an interface that demands a getValue(IObj) and setValue(IObj), but for XML schema it is useless since it shoudl define that all sub types have an val attribute which type is defined by the sub type. I think that's not possible at all with XML schema. So I think it is best either to have a dummy type Val that is just used to mark types as value types or to leave it out completely.

> UML diagram and text needs clarification line 269
> -------------------------------------------------
>                 Key: OBIX-1
>                 URL: http://tools.oasis-open.org/issues/browse/OBIX-1
>             Project: OASIS Open Building Information Exchange (oBIX) TC
>          Issue Type: Bug
>          Components: OBIX 1.1 Specification
>    Affects Versions: oBIX PR01
>         Environment: William Cox
>            Reporter: William Cox
>            Assignee: William Cox
> Line 269ff
> The UML diagram is generally conformant UML but leaves significant questions for the reader.
> (1) what are the base types? The text suggests but does not state that the underlying types are XML Schema (xsd) types. This should be clarified in the text.
> (2) The UML diagram does not follow the schema; they are not synchronized. The final 1.1 spec must have consistent use of types and implied types in the schemas. See also notes on schemas by others.
> (3) The use of "val" seems odd in UML expression; the apparent metaindication of "<type>" is not standard UML and should be corrected.

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]