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-226) Metadata Recommendations (Section 14)

Toby Considine created OBIX-226:

             Summary: Metadata Recommendations (Section 14)
                 Key: OBIX-226
                 URL: https://issues.oasis-open.org/browse/OBIX-226
             Project: OASIS Open Building Information Exchange (oBIX) TC
          Issue Type: Improvement
          Components: OBIX 1.1 Schema, OBIX 1.1 Specification
    Affects Versions: OBIX 1.1 PR03
         Environment: Brian Frank
            Reporter: Toby Considine
            Assignee: Craig Gemmill 

9.4 Metadata
This is a better design than the last version.  But it still seems unsatisfactory when it comes to how it will be applied to Haystack tags.  In Haystack the vast majority of tags are marker tags which the proposed oBIX spec requires those tags to be sub-objects.  But in reality marker tags are much closer to oBIX contracts.  I think it would be cleaner to define marker tags in the "is" attribute using their tagspace as their prefix.  Consider:

  // proposed version
  <obj displayName="Discharge Temp Sensor">
     <obj ts="h" name="discharge"/>
     <obj ts="h" name="temp"/>
     <obj ts="h" name="air"/>
     <obj ts="h" name="sensor"/>
     <obj ts="h" name="point"/>

  // versus simpler design
  <obj displayName="Discharge Temp Sensor"
   is="h:discharge h:temp h:air h:sensor h:point">   

This message was sent by Atlassian JIRA

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