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


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

William Cox updated OBIX-1:
---------------------------

    Fix Version/s: OBIX 1.1 WD34
       Resolution: 
Do not include xsd:.  The text referring to Figure 4-1 should be similar to  "All diagrams are non-normative.

The normative definition of OBIX 1.1 is in XML schema. Diagram <DiagramNumber> is a UML representation of the OBIX class structure with some liberties taken in the types. XML schema attributes in the OBIX schemas are optional with cardinality [0..1]; we have illustrated those with initial values as having cardinality [1..1]. ".

See wtcox emailto TC on 20140925.

> UML diagram and text needs clarification line 269
> -------------------------------------------------
>
>                 Key: OBIX-1
>                 URL: https://issues.oasis-open.org/browse/OBIX-1
>             Project: OASIS Open Building Information Exchange (oBIX) TC
>          Issue Type: Bug
>          Components: OBIX 1.1 Specification
>    Affects Versions: oBIX 1.1 PR01
>         Environment: William Cox
>            Reporter: William Cox
>            Assignee: William Cox
>             Fix For: OBIX 1.1 WD34
>
>
> 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 was sent by Atlassian JIRA
(v6.2.2#6258)


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