Closed YoucTagh closed 10 months ago
For FIPA: as the mention of fipa:AgentDescription
is inside a literal there is no syntactic problem but one could replace that qname with an expression like "an agent description based on the FIPA standard"
The foaf
prefix could be removed indeed since we moved to schema
.
The voaf
prefix could be kept if we intend to use any of these for instance: voaf:Vocabulary
, voaf:classNumber
, voaf:propertyNumber
@andreiciortea, Fabien's proposal appears to address the issue, but I'm reaching out to you because the topic is related to the FIPA OWL ontology that you have contributed.
..and there is no initiative to add AgentDescription to the fipa.ttl? It would fit there...
+1 for @FabienGandon's proposal, it is more descriptive and clear
@smnmyr we'll need to update the FIPA vocabulary. For that one, we did not follow a specific methodology. I will bring this up in today's heartbeat meeting.
this issue is now covered in PR #186
In core.ttl,
:ResourceProfile
mentionsfipa:AgentDescription
as an example. However, there is no such class in fipa.ttl.Also, the prefix
fipa
is used in thatskos:example
when it is not defined with the prefixes. Meanwhile, there are other prefixes that are defined but not used:voaf
andfoaf
.