[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OBIX-155) 6.2 Href
[ https://tools.oasis-open.org/issues/browse/OBIX-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Gemmill updated OBIX-155:
--------------------------------
Description:
"6.2 Href reads in part:
*****
The href of an Object is represented using the href attribute. If specified, the root Object MUST have an absolute URI. All other hrefs within an OBIX document are treated as URI references which may be relative. Because the root href is always an absolute URI, it may be used as the base for normalizing relative URIs within the OBIX document. The formal rules for URI syntax and normalization are defined in RFC3986. OBIX implementations MUST follow these rules. We consider a few common cases that serve as design patterns within OBIX in Section 6.3.
*****
In 3.3, URIs were implied to be a way to name OBIX objects, now that seems to not be the case.
But shouldn't the first href be the URI of an Object? If so, then what does ""All other hrefs within an OBIX document are treated as URI references"" mean? Won't they all be URI references? There is no ""root href"" rather the href attribute of the root element. Yes? What are ""these rules?"" RFC3986? That should have already been stated elsewhere."
was:
"6.2 Href reads in part:
*****
The href of an Object is represented using the href attribute. If specified, the root Object MUST have an absolute URI. All other hrefs within an OBIX document are treated as URI references which may be relative. Because the root href is always an absolute URI, it may be used as the base for normalizing relative URIs within the OBIX document. The formal rules for URI syntax and normalization are defined in RFC3986. OBIX implementations MUST follow these rules. We consider a few common cases that serve as design patterns within OBIX in Section 6.3.
*****
In 3.3, URIs were implied to be a way to name OBIX objects, now that seems to not be the case.
But shouldn't the first href be the URI of an Object? If so, then was does ""All other hrefs within an OBIX document are treated as URI references"" mean? Won't they all be URI references? There is no ""root href"" rather the href attribute of the root element. Yes? What are ""these rules?"" RFC3986? That should have already been stated elsewhere."
> 6.2 Href
> --------
>
> Key: OBIX-155
> URL: https://tools.oasis-open.org/issues/browse/OBIX-155
> Project: OASIS Open Building Information Exchange (oBIX) TC
> Issue Type: Bug
> Components: OBIX 1.1 Specification
> Affects Versions: OBIX 1.1 PR02
> Environment: TAB Review
> Reporter: Toby Considine
> Assignee: Craig Gemmill
> Priority: Minor
>
> "6.2 Href reads in part:
> *****
> The href of an Object is represented using the href attribute. If specified, the root Object MUST have an absolute URI. All other hrefs within an OBIX document are treated as URI references which may be relative. Because the root href is always an absolute URI, it may be used as the base for normalizing relative URIs within the OBIX document. The formal rules for URI syntax and normalization are defined in RFC3986. OBIX implementations MUST follow these rules. We consider a few common cases that serve as design patterns within OBIX in Section 6.3.
> *****
> In 3.3, URIs were implied to be a way to name OBIX objects, now that seems to not be the case.
> But shouldn't the first href be the URI of an Object? If so, then what does ""All other hrefs within an OBIX document are treated as URI references"" mean? Won't they all be URI references? There is no ""root href"" rather the href attribute of the root element. Yes? What are ""these rules?"" RFC3986? That should have already been stated elsewhere."
--
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]