Hi Alan, Where can Joel get the definitive current schema or schemata belonging to OCCI ? That's my question.. :) -gary On 4/4/2011 4:45 PM, Sill, Alan wrote:

Usually these are created when the document s published. We ran into this on another recent document now in public comment also, and decided to put it in on a tentative basis in that case to facilitate testing. We can do that this time also, since things are so close to publication.

Where can Joel get the definitive current schema or schemata belonging to OCCI, and how likely is it / are they to change before final publication?

Alan

On Apr 4, 2011, at 5:24 PM, "Gary Mazz" wrote:

...

Hi

There is no scheme @ http://schemas.ogf.org/occi/

cheers, gary

_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

See Section 3.2 and e.g. Table 3 of the current Infrastructure document. Alan On Apr 5, 2011, at 12:21 PM, "alexander.papaspyrou@tu-dortmund.de" wrote:

Hm, not sure what schema you mean...

What would you expect to see there?

-Alexander

Am 05.04.2011 um 01:36 schrieb Gary Mazz:

...

Hi Alan,

Where can Joel get the definitive current schema or schemata belonging to OCCI ?

That's my question.. :)

-gary

On 4/4/2011 4:45 PM, Sill, Alan wrote:

...

Usually these are created when the document s published. We ran into this on another recent document now in public comment also, and decided to put it in on a tentative basis in that case to facilitate testing. We can do that this time also, since things are so close to publication.

Where can Joel get the definitive current schema or schemata belonging to OCCI, and how likely is it / are they to change before final publication?

Alan

On Apr 4, 2011, at 5:24 PM, "Gary Mazz" wrote:

...

Hi

There is no scheme @ http://schemas.ogf.org/occi/

cheers, gary

_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

(Same question in the core document , with regards to the http://schemas.ogf.org/occi/ base URL reserved for OCCI and the http://schemas.ogf.org/occi/core#entity Kind instances.) Sorry for the ignorant question. Alan On Apr 6, 2011, at 12:26 AM, Sill, Alan wrote:

More specifically - in Table 1 we define the following Kind instances. Are these tken to be a namespace, so that no definite schema has to be associated with them, or is there intended to be a document returned at the following URIs (i.e., are they actual schemata URLs)?

Table 1. The Kind instances defined for the infrastructure sub-types of Resource, Link and related Mixins. The base URL http://schemas.ogf.org/occi has been replaced with <schema> in this table for a better readability experience.

Term compute storage storagelink network ipnetworking networkinterface ipnetworkinterface

Scheme <schema>/infrastructure# <schema>/infrastructure# <schema>/infrastructure# <schema>/infrastructure# <schema>/infrastructure/network# <schema>/infrastructure# <schema>/infrastucture/networkinterface#

Title Compute Resource Storage Resource StorageLink Link Network Resource IP Networking Mixin NetworkInterface Link IP NetworkInterface Mixin Related Kind

<schema>/core#resource <schema>/core#resource <schema>/core#link <schema>/core#resource – <schema>/core#link –

Thanks, Alan

On Apr 5, 2011, at 2:03 PM, Sill, Alan wrote:

...

See Section 3.2 and e.g. Table 3 of the current Infrastructure document.

Alan

On Apr 5, 2011, at 12:21 PM, "alexander.papaspyrou@tu-dortmund.de" wrote:

...

Hm, not sure what schema you mean...

What would you expect to see there?

-Alexander

Am 05.04.2011 um 01:36 schrieb Gary Mazz:

...

Hi Alan,

Where can Joel get the definitive current schema or schemata belonging to OCCI ?

That's my question.. :)

-gary

On 4/4/2011 4:45 PM, Sill, Alan wrote:

...

Usually these are created when the document s published. We ran into this on another recent document now in public comment also, and decided to put it in on a tentative basis in that case to facilitate testing. We can do that this time also, since things are so close to publication.

Where can Joel get the definitive current schema or schemata belonging to OCCI, and how likely is it / are they to change before final publication?

Alan

On Apr 4, 2011, at 5:24 PM, "Gary Mazz" wrote:

...

Hi

There is no scheme @ http://schemas.ogf.org/occi/

cheers, gary

_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

Hi Gary, On Wed, Apr 6, 2011 at 7:16 AM, Gary Mazz wrote:

Hi All,

Maybe I wasn't clear with the question. I thought we generated a scheme and published it on http://schemas.ogf.org . It been almost a year ago, so I may be wrong... or dropped another brain cell along the way :)

From what I understand from the OCCI specs, the schema locations are indeed supposed to provide a unique and well defined namespace for OCCI, and OCCI extensions. But I don't see any place in the specs where that URL is actually evaluated, and returns a schema of any kind.

Having said that, I think it might be a good idea to use that schema scheme (ha!) to implement some form of namespace verification. For example, I placed an empty document at http://schemas.ogf.org/occi/infrastructure, so that all GET operations on that document return an HTTP 200 (OK). That provides a very simple way to confirm the validity of OCCI identifiers, and also provides a straight-forward way to register OCCI extensions (or rather, their namespaces). One could also link the normative documents for the extension at http://schemas.ogf.org/occi/infrastructure#specification; one could verify the #target elements; etc. However, that is as of yet unspecified AFAICS, and is likely a rather naive proposal, given my somewhat limited knowledge of HTTP itself. Best, Andre.

cheers, gary

On 4/5/2011 10:34 PM, Alan Sill wrote:

...

(Same question in the core document , with regards to the http://schemas.ogf.org/occi/ base URL reserved for OCCI and the http://schemas.ogf.org/occi/core#entity Kind instances.)

Sorry for the ignorant question.

Alan

On Apr 6, 2011, at 12:26 AM, Sill, Alan wrote:

...

More specifically - in Table 1 we define the following Kind instances.  Are these tken to be a namespace, so that no definite schema has to be associated with them, or is there intended to be a document returned at the following URIs (i.e., are they actual schemata URLs)?

Table 1.     The Kind instances defined for the infrastructure sub-types of Resource, Link and related Mixins. The base URL http://schemas.ogf.org/occi has been replaced with<schema>  in this table for a better readability experience.

Term compute storage storagelink network ipnetworking networkinterface ipnetworkinterface

Scheme <schema>/infrastructure#<schema>/infrastructure#<schema>/infrastructure#<schema>/infrastructure#<schema>/infrastructure/network#<schema>/infrastructure#<schema>/infrastucture/networkinterface#

Title Compute Resource Storage Resource StorageLink Link Network Resource IP Networking Mixin NetworkInterface Link IP NetworkInterface Mixin Related Kind

<schema>/core#resource<schema>/core#resource<schema>/core#link<schema>/core#resource – <schema>/core#link –

Thanks, Alan

On Apr 5, 2011, at 2:03 PM, Sill, Alan wrote:

...

See Section 3.2 and e.g. Table 3 of the current Infrastructure document.

Alan

On Apr 5, 2011, at 12:21 PM, "alexander.papaspyrou@tu-dortmund.de"  wrote:

...

Hm, not sure what schema you mean...

What would you expect to see there?

-Alexander

Am 05.04.2011 um 01:36 schrieb Gary Mazz:

...

Hi Alan,

Where can Joel get the definitive current schema or schemata belonging to OCCI ?

That's my question.. :)

-gary

On 4/4/2011 4:45 PM, Sill, Alan wrote: > Usually these are created when the document s published. We ran into this on another recent document now in public comment also, and decided to put it in on a tentative basis in that case to facilitate testing. We can do that this time also, since things are so close to publication. > > Where can Joel get the definitive current schema or schemata belonging to OCCI, and how likely is it / are they to change before final publication? > > Alan > > > > On Apr 4, 2011, at 5:24 PM, "Gary Mazz"   wrote: > >> Hi >> >> There is no scheme @ http://schemas.ogf.org/occi/ >> >> cheers, >> gary >> >> >> _______________________________________________ >> occi-wg mailing list >> occi-wg@ogf.org >> http://www.ogf.org/mailman/listinfo/occi-wg _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

---

occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

---

occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

-- So much time, so little to do... [Garfield]

On Wed, Apr 6, 2011 at 8:17 AM, Gary Mazz wrote:

I did find the reference to it in one of your emails from 2 years ago..Minor comments:

...

- why the purl.org/occi namespace? OGF has an established namespace for XML schemata, see http://schemas.ogf.org/, and GFD.84 on http://www.ogf.org/docs/?cp

Ah, I think I see now where this is coming from! :-) That comment was for the ATOM rendering, which explicitly used XML -- thus the xml schema (see http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/APIDesign for details on the ATOM rendering approach). That rendering is obsolete by now I think -- a to-be-defined new ATOM rendering of OCCI, or other XML based renderings, may well introduce XML schemas again, but AFAIU that is different from the way the schema URLs are used in OCCI right now. Cheers, Andre.

cheers gary

On 4/5/2011 11:46 PM, Andre Merzky wrote:

Hi Gary,

On Wed, Apr 6, 2011 at 7:16 AM, Gary Mazz wrote:

Hi All,

Maybe I wasn't clear with the question. I thought we generated a scheme and published it on http://schemas.ogf.org . It been almost a year ago, so I may be wrong... or dropped another brain cell along the way :)

...

From what I understand from the OCCI specs, the schema locations are indeed supposed to provide a unique and well defined namespace for OCCI, and OCCI extensions. But I don't see any place in the specs where that URL is actually evaluated, and returns a schema of any kind.

Having said that, I think it might be a good idea to use that schema scheme (ha!) to implement some form of namespace verification. For example, I placed an empty document at http://schemas.ogf.org/occi/infrastructure, so that all GET operations on that document return an HTTP 200 (OK). That provides a very simple way to confirm the validity of OCCI identifiers, and also provides a straight-forward way to register OCCI extensions (or rather, their namespaces). One could also link the normative documents for the extension at http://schemas.ogf.org/occi/infrastructure#specification; one could verify the #target elements; etc. However, that is as of yet unspecified AFAICS, and is likely a rather naive proposal, given my somewhat limited knowledge of HTTP itself.

Best, Andre.

cheers, gary

On 4/5/2011 10:34 PM, Alan Sill wrote:

(Same question in the core document , with regards to the http://schemas.ogf.org/occi/ base URL reserved for OCCI and the http://schemas.ogf.org/occi/core#entity Kind instances.)

Sorry for the ignorant question.

Alan

On Apr 6, 2011, at 12:26 AM, Sill, Alan wrote:

More specifically - in Table 1 we define the following Kind instances.  Are these tken to be a namespace, so that no definite schema has to be associated with them, or is there intended to be a document returned at the following URIs (i.e., are they actual schemata URLs)?

Table 1.     The Kind instances defined for the infrastructure sub-types of Resource, Link and related Mixins. The base URL http://schemas.ogf.org/occi has been replaced with<schema>  in this table for a better readability experience.

Term compute storage storagelink network ipnetworking networkinterface ipnetworkinterface

Scheme <schema>/infrastructure#<schema>/infrastructure#<schema>/infrastructure#<schema>/infrastructure#<schema>/infrastructure/network#<schema>/infrastructure#<schema>/infrastucture/networkinterface#

Title Compute Resource Storage Resource StorageLink Link Network Resource IP Networking Mixin NetworkInterface Link IP NetworkInterface Mixin Related Kind

<schema>/core#resource<schema>/core#resource<schema>/core#link<schema>/core#resource – <schema>/core#link –

Thanks, Alan

On Apr 5, 2011, at 2:03 PM, Sill, Alan wrote:

See Section 3.2 and e.g. Table 3 of the current Infrastructure document.

Alan

On Apr 5, 2011, at 12:21 PM, "alexander.papaspyrou@tu-dortmund.de"  wrote:

Hm, not sure what schema you mean...

What would you expect to see there?

-Alexander

Am 05.04.2011 um 01:36 schrieb Gary Mazz:

Hi Alan,

Where can Joel get the definitive current schema or schemata belonging to OCCI ?

That's my question.. :)

-gary

On 4/4/2011 4:45 PM, Sill, Alan wrote:

Usually these are created when the document s published. We ran into this on another recent document now in public comment also, and decided to put it in on a tentative basis in that case to facilitate testing. We can do that this time also, since things are so close to publication.

Where can Joel get the definitive current schema or schemata belonging to OCCI, and how likely is it / are they to change before final publication?

Alan

On Apr 4, 2011, at 5:24 PM, "Gary Mazz"   wrote:

Hi

There is no scheme @ http://schemas.ogf.org/occi/

cheers, gary

_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

-- So much time, so little to do... [Garfield]

Ralf, thanks for clarifying the HTTP semantics for the fragments. That semantics makes sense I think, as the whole document needs to be retrieved anyway. Cheers, Andre. On Wed, Apr 6, 2011 at 8:54 AM, Ralf Nyren wrote:

On Wed, 6 Apr 2011 07:46:36 +0200, Andre Merzky wrote:

...

One could also link the normative documents for the extension at http://schemas.ogf.org/occi/infrastructure#specification; one could verify the #target elements; etc.  However, that is as of yet unspecified AFAICS, and is likely a rather naive proposal, given my somewhat limited knowledge of HTTP itself.

There is a little problem with the fragment part of the URI, i.e. the #xxxx. According to the RFCs it is not part of the URL sent to the HTTP server. It is something that the client has to handle by itself.

For example: - Clicking on the http://schemas.ogf.org/occi/infrastructure#compute URL in your favorite browser will yield an HTTP request as follows: GET /occi/infrastructure HTTP/1.1

- In other words the _whole_ infrastructure "document" will be retrieved. The client (in this case your browser) will attempt to translate the #compute part into something useful with regard to the content-type of the document received. In case of text/html it is to jump to the fragment marker in the document. - How to handle the URL fragments in a future OCCI schema definition must be defined together with the format. However it is still the client which has to do the processing.

regards, Ralf

-- So much time, so little to do... [Garfield]

On Wed, Apr 6, 2011 at 11:11 AM, Alan Sill wrote:

So what I get from this discussion is that for the infrastructure URL semantics, the blank-document approach is OK.

What about the others - for example, http://schemas.ogf.org/occi/core (#resource and #link) - which still return 404 Not Found ?  Should the same solution be applied?

Done - please let me know if others are missing... Cheers, Andre.

Alan

On Apr 6, 2011, at 3:51 AM, Andre Merzky wrote:

...

Ralf, thanks for clarifying the HTTP semantics for the fragments. That semantics makes sense I think, as the whole document needs to be retrieved anyway.

Cheers, Andre.

On Wed, Apr 6, 2011 at 8:54 AM, Ralf Nyren wrote:

...

On Wed, 6 Apr 2011 07:46:36 +0200, Andre Merzky wrote:

...

One could also link the normative documents for the extension at http://schemas.ogf.org/occi/infrastructure#specification; one could verify the #target elements; etc.  However, that is as of yet unspecified AFAICS, and is likely a rather naive proposal, given my somewhat limited knowledge of HTTP itself.

There is a little problem with the fragment part of the URI, i.e. the #xxxx. According to the RFCs it is not part of the URL sent to the HTTP server. It is something that the client has to handle by itself.

For example: - Clicking on the http://schemas.ogf.org/occi/infrastructure#compute URL in your favorite browser will yield an HTTP request as follows: GET /occi/infrastructure HTTP/1.1

- In other words the _whole_ infrastructure "document" will be retrieved. The client (in this case your browser) will attempt to translate the #compute part into something useful with regard to the content-type of the document received. In case of text/html it is to jump to the fragment marker in the document. - How to handle the URL fragments in a future OCCI schema definition must be defined together with the format. However it is still the client which has to do the processing.

regards, Ralf

-- So much time, so little to do... [Garfield] _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

-- So much time, so little to do... [Garfield]