This relates to issue #478, which is concerned with the definition of a rack_class predicate in Prolog. What constitutes a RACK class? The answer, with a couple of notable exceptions, appears to be a class with a URI prefix of http://arcos.project/partner/, where project is the name of an ARCOS project and partner is a 2-3 letter abbreviation of the partner's name.
For example, ontologies generated by Honeywell's Clarissa project might have a URI prefix of http://arcos.clarissa/HW/.
Personally, I would have preferred a URI prefix of the form http://arcos.rack/project/partner or similar, in other words, keeping the http://arcos.rack prefix, but if the current convention has been agreed by the Jedi Council, so be it...
However, there are some notable exceptions, in particular the Turnstile example, which uses a prefix of http://turnstile/ and most of the standards, which use a prefix of http://common.
This relates to issue #478, which is concerned with the definition of a
rack_class
predicate in Prolog. What constitutes a RACK class? The answer, with a couple of notable exceptions, appears to be a class with a URI prefix ofhttp://arcos.project/partner/
, whereproject
is the name of an ARCOS project andpartner
is a 2-3 letter abbreviation of the partner's name.For example, ontologies generated by Honeywell's Clarissa project might have a URI prefix of
http://arcos.clarissa/HW/
.Personally, I would have preferred a URI prefix of the form
http://arcos.rack/project/partner
or similar, in other words, keeping thehttp://arcos.rack
prefix, but if the current convention has been agreed by the Jedi Council, so be it...However, there are some notable exceptions, in particular the Turnstile example, which uses a prefix of
http://turnstile/
and most of the standards, which use a prefix ofhttp://common
.See also #485 and #487.