[OASIS Issue Tracker] Created: (OBIX-213) 9.4 Alternate Hierarchies

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

9.4 Alternate Hierarchies
-------------------------

                 Key: OBIX-213
                 URL: http://tools.oasis-open.org/issues/browse/OBIX-213
             Project: OASIS Open Building Information Exchange (oBIX) TC
          Issue Type: Improvement
          Components: OBIX 1.1 Specification
    Affects Versions: OBIX 1.1 XSD PR02
         Environment: Brian Frank
            Reporter: Toby Considine
            Assignee: Craig Gemmill 


There isn't any definition of what an alternate hierarchy actually means.  Its a link to some other object, so why wouldn't any normal URI suffice?  In what cases is the semicolon style URI required?
 
If this is the design for how to integrate Haystack tagging into oBIX, then it won't work well.  Haystack takes a design approach that data and metadata is flattened into a simple associative array to model the entity.  Therefore everything about the entity would be identified with one URI and object extent in oBIX.  Instead the design should address how the notation of marker tags might be represented in the oBIX contract model (and/or extent). Discussion on haystack forum:
 
  http://project-haystack.org/forum/topic/28

-- 
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