iand / vocab-bio Goto Github PK
View Code? Open in Web Editor NEWBIO: A vocabulary for biographical information
Home Page: http://vocab.org/bio/0.1/
BIO: A vocabulary for biographical information
Home Page: http://vocab.org/bio/0.1/
This project contains the source schema for the RDF Schema at http://vocab.org/bio/0.1/ I am sharing the schema in github so others can contribute edits and improvements. It is an experiment to see how well a service like github can work for collaboratively managing schemas. To edit the schema, clone the repository, make your changes, check to make sure your change results in valid RDF (and says what you think you're saying) using a tool like rapper (http://librdf.org/raptor/rapper.html). If you are satisfied with your edits, send me a pull request (http://help.github.com/pull-requests/) I'll consider merging and publishing to vocab.org (Inspiration for this approach comes from https://github.com/rsinger/LinkedMARCCodes)
Hello,
For information, you can visualise the vocabulary online via OWLGrEd.
The description of bio:position
indicates it's value is a foaf:Person
, but does that make sense for that property? An "employment position or public office" sounds like it needs a different sort of Class altogether, one that indicates the name of the position, date it was first opened for applicants, other applicants to the position, etc.
In the "Core Classes" diagram, the arrow for bio:participant
seems to indicate the property is supposed to exist on the foaf:Person
and point to a bio:Relationship
. However, the description for bio:participant
indicates it is placed on the Agent Relationship (bio:Relationship
), and points to a foaf:Agent
.
Its inverse, bio:relationship
is the one that is on a foaf:Agent
and points to an Agent Relationship. So, should those arrows should be labeled as bio:relationship
or modified to point the other direction?
Additionally, having the inverse relationships indicated in the Core Classes diagram could be useful (or create a separate diagram for relationships flowing in the other direction?):
bio:agent
or bio:partner
or bio:principal
(bio:Event
to foaf:Agent
)bio:event
(foaf:Agent
to bio:Event
)bio:participant
(bio:Relationship
to foaf:Agent
)bio:relationship
(foaf:Agent
to bio:Relationship
)bio:eventInterval
(bio:Event
to bio:Interval
)bio:initiatingEvent
or bio:concludingEvent
(bio:Interval
to bio:Event
)bio:interval
(bio:Relationship
to bio:Interval
)I believe there's no inverse for the bio:interval
property to put on a bio:Interval
to mark what bio:Relationship
it causes?
I think it would be useful to include a diagram of the class hierarchies laid out by this namespace, to more easily pick a more/less specific class/property:
bio:agent
(bio:Event
to foaf:Agent
)
bio:employer
bio:officiator
bio:organization
bio:parent
bio:partner
bio:position
bio:principal
bio:spectator
bio:witness
bio:state
bio:Event
bio:IndividualEvent
bio:Accession
bio:Adoption
bio:Baptism
bio:BarMitzvah
bio:BasMitzvah
bio:Birth
bio:Burial
(concluding Death)bio:Coronation
bio:Cremation
(concluding Death)bio:Death
bio:Execution
bio:Murder
bio:Assassination
bio:Disbanding
(concluding Organization)bio:Dismissal
(concluding Employment; should be a bio:PositionChange
child?)bio:Emigration
bio:Employment
(initiating)bio:Enrollment
(initiating Education)bio:Formation
(initiating Organization)bio:Graduation
(concluding Education)bio:Imprisonment
bio:Inauguration
bio:Investiture
bio:Funeral
bio:NameChange
bio:Naturalization
bio:Ordination
bio:PositionChange
(concluding Employment and initiating next)
bio:Demotion
(concluding Employment and initiating next)bio:Promotion
(concluding Employment and initiating next)bio:Redundancy
(concluding Employment; should be a bio:PositionChange
child?)bio:Resignation
(concluding Employment; should be a bio:PositionChange
child?)bio:Retirement
(concluding Employment; should be a bio:PositionChange
child?)bio:GroupEvent
bio:Annulment
(concluding Marriage)bio:Divorce
(concluding Marriage)bio:Marriage
(initiating)bio:Performance
bio:organization
indicates its value is a foaf:Person
, which doesn't make sense (people are not organizations); it should be relaxed to be a foaf:Agent
(which is the parent class of foaf:Person
), which includes organizations in the classification.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.