Which domain name for the ODRL profile used for TDM Policies?

[llemeurfr]

In the current proposal, edrlab.org is used. But it can be viewed as a vendor name (see PR #12).

Would W3C agree to offer its domain name for the ODRL profile identification?

[llemeurfr]

Talking with @iherman I had confirmation that the W3C management accepts the use of the W3C domain name for identifying the properties defined in the Policy specification.

Here is therefore two proposals for the definition of the "tdm" prefix:

a/ http://www.w3.org/ns/tdmrep#

Its advantage is that it is short and clear, and the structure of the URL is copied from existing namespaces like "http://www.w3.org/ns/odrl/2/". But W3C tech people must create a URL rewrite rule that sends users to a Github page in the tdm-reservation-protocol repository.

b/ https://w3c.github.io/tdm-reservation-protocol/odrl-profile#

Its advantage is that this Github space is active, we just have to create an "odrl-profile" folder in Github, there is no rewrite rule involved. But the URL is much less classy.

[llemeurfr]

The group is ok to propose this W3C URL to the W3C management.

[iherman]

@llemeurfr

The group is ok to propose this W3C URL to the W3C management.

Do you mean to use http://www.w3.org/ns/tdmrep#?

To be very clear, what I would do, if you guys are fine with it, is:

• set up a redirection from http://www.w3.org/ns/tdmrep.ttl, http://www.w3.org/ns/tdmrep.rdf, and http://www.w3.org/ns/tdmrep.html to their github counterpart or copy these to these URL-s verbatim. As you prefer.
• set up a content negotiation so that http://www.w3.org/ns/tdmrep would go for the ttl, rdf, and html versions based on the respective media types.

The ttl and rdf files would have to include the RDF schema version of the vocabulary in Turtle and RDF/XML, respectively. The HTML file should provide a human readable description of the same.

If you also want to have the vocabulary in json-ld, that can be added as well, of course.

However that does not cover the JSON-LD @context file, which is not a vocabulary file. Do you guys define such a context file? Because we will then need a separate URL for that (say, http://www.w3.org/ns/tdmcontext.jsonld or something similar).

CC @swickr for the URLs being used.

[llemeurfr]

That seems good; what you propose is equivalent to what ODRL proposes at https://www.w3.org/ns/odrl/2/.

Doing that, http://www.w3.org/ns/tdmrep# is similar to the odrl namespace "http://www.w3.org/ns/odrl/2/".

I see that W3C WG's have been very imaginative in their choices: "vcard": "http://www.w3.org/2006/vcard/ns#" "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#" "rdfs": "http://www.w3.org/2000/01/rdf-schema#" "owl": "http://www.w3.org/2002/07/owl#" "skos": "http://www.w3.org/2004/02/skos/core#" "xsd:" "http://www.w3.org/2001/XMLSchema#" "xml:" "http://www.w3.org/XML/1998/namespace"

See also "cc": "http://creativecommons.org/ns#"

Therefore if you have a preference (an emerging standard form) please advise.

Do you guys define such a context file?

I don't think so: the idea is to declare the "tdm" prefix in each instance and use if when rdf properties / values are used.

  "@context": [
      "http://www.w3.org/ns/odrl.jsonld",
      {"tdm": "http://www.w3.org/ns/tdmrep#"}
  ],

Note that the only resources we need so far are listed here.

[iherman]

That seems good; what you propose is equivalent to what ODRL proposes at https://www.w3.org/ns/odrl/2/.

Doing that, http://www.w3.org/ns/tdmrep# is similar to the odrl namespace "http://www.w3.org/ns/odrl/2/".

I see that W3C WG's have been very imaginative in their choices: "vcard": "http://www.w3.org/2006/vcard/ns# http://www.w3.org/2006/vcard/ns#" "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns# http://www.w3.org/1999/02/22-rdf-syntax-ns#" "rdfs": "http://www.w3.org/2000/01/rdf-schema# http://www.w3.org/2000/01/rdf-schema#" "owl": "http://www.w3.org/2002/07/owl# http://www.w3.org/2002/07/owl#" "skos": "http://www.w3.org/2004/02/skos/core# http://www.w3.org/2004/02/skos/core#" "xsd:" "http://www.w3.org/2001/XMLSchema# http://www.w3.org/2001/XMLSchema#" "xml:" "http://www.w3.org/XML/1998/namespace http://www.w3.org/XML/1998/namespace"

See also "cc": "http://creativecommons.org/ns# http://creativecommons.org/ns#"

Yeah well… this was indeed a mess, in fact, leading to URI-s that nobody remembers and which is a pain when one has to type in a file. After all these years, I am still unable to remember the URI for the RDF namespace…

That is exactly why W3C has introduced the /ns folder at some point (I think it was about 10 years ago). These days all RDF namespaces, XML namespaces, vocabularies, etc, are encouraged to use that folder. Hence my proposal that uses /ns

Therefore if you have a preference (an emerging standard form) please advise.

Do you guys define such a context file?

I don't think so: the idea is to declare the "tdm" prefix in each instance and use if when rdf properties / values are used.

@.***": [ "http://www.w3.org/ns/odrl.jsonld", {"tdm": "http://www.w3.org/ns/tdmrep#"} ], Great, that simplifies things greatly.

You should give me (or point at github) the respective HTML, Turtle, etc, files and I will copy them to /ns and set up the redirection.

[llemeurfr]

I started creating the files related to the TDM Policy ontology. The first is https://github.com/w3c/tdm-reservation-protocol/blob/main/ontology/tdmrep.html, i.e. the html introduction, to be copied after validation to the w3c repository where is will be correctly associated with its css.

[iherman]

I started creating the files related to the TDM Policy ontology. The first is https://github.com/w3c/tdm-reservation-protocol/blob/main/ontology/tdmrep.html, i.e. the html introduction, to be copied after validation to the w3c repository where is will be correctly associated with its css.

Shouldn't there be a JSON-LD version of the vocabulary, too?