Open GoogleCodeExporter opened 9 years ago
Original comment by sha...@essaid.com
on 24 Sep 2012 at 8:47
The VIVO class http://vivoweb.org/ontology/core#Credential is used as to level
class for credential and it a GDC.
Original comment by sha...@essaid.com
on 4 Oct 2012 at 10:12
The object property http://vivoweb.org/ontology/core#hasGoverningAuthority and
its inverse http://vivoweb.org/ontology/core#governingAuthorityFor are added.
The asserted range/domain were Organization but they are changed to Agent to
less constrained.
http://xmlns.com/foaf/0.1/Agent was added but not asserted to be a material
entity as it was in VIVO. I think an Agent is an abstract entity and it should
not be a material one. We need to clarify what Agent is TODO. Agent used as
range/domain as described above.
Original comment by sha...@essaid.com
on 4 Oct 2012 at 10:19
There is an axiom "has subject area only Thing" in VIVO. Not sure if this is
needed if we subtype "Credential" so that there is a subtype for each type of
credential. This should address the "subject area" qualification.
Property http://vivoweb.org/ontology/core#hasSubjectArea and its inverse not
added to the credential module. Review TODO.
Original comment by sha...@essaid.com
on 4 Oct 2012 at 10:23
VIVO uses a "valid in" object property as a way for specifying a valid 3
dimensional "Geographic Location" location for the credential. It is too
restrictive to state that a credential is can only be valid in such a location.
A more flexible approach is to assert that a credential has one or more
contexts and the base context is "Thing". This can allow a user to specify a
temporal region as a context to indicate the temporal effectiveness or validity
of a credential. It can also allow the assertion of a 3-d location if needed,
an abstract entity (such as an organization) regardless of where the abstract
entity is materialized (regardless of which buildings and 3-d locations the
organization is existing in at any specific time), etc.
Added a "has context" http://purl.obolibrary.org/obo/ARG_0001000 and its
inverse "is context for" http://purl.obolibrary.org/obo/ARG_0001001 for this
use-case without specifying domain and range. Review TODO.
Original comment by sha...@essaid.com
on 4 Oct 2012 at 10:30
The "Issued credential" VIVO class, a SDC, is not used in the new model.
However, it has few properties that might be needed:
date issued (TODO if can't be handled with a temporal context)
expiration date (TODO as above)
has subject area
valid in
description (TODO how is this used?)
Original comment by sha...@essaid.com
on 4 Oct 2012 at 11:00
The object property http://vivoweb.org/ontology/core#hasCredential and its
inverse http://vivoweb.org/ontology/core#credentialOf were used to an "Issued
credential" and a "Person". I think it should relate the more general "Agent"
class but even that is too restrictive. VIVO has a "Certificate" class as a
subclass of "credential" and there are certificates that are not assigned to
"Agent". The elevator maintenance certificate is issued by an Agent but it is
not held by a Person or Agent.
Added the object properties without domain and rage. These properties could
probably be generalized to something like holds/held_by, owns/is_owned_by so
that the meaning of of belonging to/having is not mixed with the type of things
being related. TODO.
Original comment by sha...@essaid.com
on 4 Oct 2012 at 11:10
The object property http://vivoweb.org/ontology/core#hasCredential labeled
"issuance of", and its inverse
http://vivoweb.org/ontology/core#issuedCredential, are not needed with the new
model. They were used to relate an instance of "Issued Credential" to the type
of "Credential".
Original comment by sha...@essaid.com
on 4 Oct 2012 at 11:12
The object property http://vivoweb.org/ontology/core#eligibleFor was added with
the range "Credential" as it was in VIVO.
Original comment by sha...@essaid.com
on 4 Oct 2012 at 11:13
The data property http://vivoweb.org/ontology/core#description should probably
be added to a more general module. Not added to the credential module.
Original comment by sha...@essaid.com
on 4 Oct 2012 at 11:15
Added subtypes http://vivoweb.org/ontology/core#Certification and
http://vivoweb.org/ontology/core#Licensure.
Original comment by sha...@essaid.com
on 4 Oct 2012 at 11:16
Original comment by sha...@essaid.com
on 5 Oct 2012 at 6:38
[deleted comment]
Removed the subclass axiom to GDC. Will add the BFO mappings later.
Original comment by sha...@essaid.com
on 8 Oct 2012 at 9:47
Added OP:
http://vivoweb.org/ontology/core#expirationDate
http://vivoweb.org/ontology/core#dateIssued
and Class:
http://vivoweb.org/ontology/core#DateTimeValue
from the time module as referenced entities. Did not bring in any axioms (the
OP have subOP axioms).
Original comment by sha...@essaid.com
on 8 Oct 2012 at 10:13
Added the DP:
http://vivoweb.org/ontology/core#description
from the general module.
Original comment by sha...@essaid.com
on 8 Oct 2012 at 10:14
DRAFT: revision 190:
http://connect-isf.googlecode.com/svn-history/r190/trunk/src/ontology/module/cre
dential/credential.owl
Original comment by sha...@essaid.com
on 8 Oct 2012 at 10:29
[deleted comment]
[deleted comment]
[deleted comment]
Added OP:
http://vivoweb.org/ontology/core#validIn
which brings in:
http://vivoweb.org/ontology/core#GeographicLocation
as its range.
Original comment by sha...@essaid.com
on 9 Oct 2012 at 5:01
Original issue reported on code.google.com by
sha...@essaid.com
on 24 Sep 2012 at 4:48