Differences between versions dated 2009-01-22 11:49:58 and 2009-01-22 13:52:43
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| == Notes on FOAF and Dublin Core == | This document addresses an action on DanBrickley and TomBaker to "investigate and assess feasibility of using FOAF for DC agent descriptions". See FoafReviewBackground for background and overview. This document focusses on the detail of expressing DC Agent requirements using FOAF's Person and Group classes. |
| Line 6: | Line 6: |
| This document addresses an action on DanBrickley and TomBaker to "investigate and assess feasibility of using FOAF for DC agent descriptions". See FoafReviewBackground for background and overview. This document focusses on the detail of expressing DC Agent requirements using FOAF's Person and Group classes. | |
| Line 11: | Line 10: |
|
==== Attributes of a Person ==== |
The following is a walk-through of the proposed properties from the DC Agents draft, discussing each in terms of FOAF or other RDF vocabularies often used with FOAF. |
| Line 33: | Line 31: |
| ----- /!\ Edit conflict! Other version: ----- | |
| Line 49: | Line 48: |
|
----- /!\ Edit conflict! Your version: ----- }}} * FOAF allows URI identifiers to be used directly for people, groups etc. * in theory dc:identifier might also be applicable * FOAF uses RDFS/OWL schemas to indicate which other properties are uniquely identifying {{{ 4.1.2 Name The name or names by which the person is known, including alternative names. }}} * FOAF provides the foaf:name property for plain text and xhtml (ruby markup etc) names * other properties in FOAF include givenName, family_name, and these names are irregularly ... named, and in need of cleanup. {{{ ----- /!\ End of edit conflict ----- |
|
| Line 52: | Line 69: |
| ----- /!\ Edit conflict! Other version: ----- | |
| Line 59: | Line 77: |
|
----- /!\ Edit conflict! Your version: ----- }}} * FOAF doesn't currently include much by way of dates * See [[http://wiki.foaf-project.org/BirthdayIssue][birthday issue]] in FOAF wiki * FOAF doesn't yet define anything beyond [[http://xmlns.com/foaf/spec/#term_birthday][birthday]] (month day) * foaf:birthdate would be a natural addition {{{ ----- /!\ End of edit conflict ----- |
This document addresses an action on DanBrickley and TomBaker to "investigate and assess feasibility of using FOAF for DC agent descriptions". See FoafReviewBackground for background and overview. This document focusses on the detail of expressing DC Agent requirements using FOAF's Person and Group classes.
FOAF and the draft DC Agents requirements
The following is a walk-through of the proposed properties from the DC Agents draft, discussing each in terms of FOAF or other RDF vocabularies often used with FOAF. The following is a walk-through of the proposed properties from the DC Agents draft, discussing each in terms of FOAF or other RDF vocabularies often used with FOAF.
This document defines the attributes of a person as the following: identifier name dates title affiliation location email other information
4.1.1. Identifier A scheme, numeric or alphabetic, or a combination of the two, used to identify unambiguously a specific individual agent. No such schemes yet exist. This element will allow for the use of such schemes when and if they are developed. ----- /!\ Edit conflict! Other version: -----
-
FOAF allows URI identifiers to be used directly for people, groups etc.
-
in theory dc:identifier might also be applicable
-
FOAF uses RDFS/OWL schemas to indicate which other properties are uniquely identifying
4.1.2 Name The name or names by which the person is known, including alternative names.
-
FOAF provides the foaf:name property for plain text and xhtml (ruby markup etc) names
-
other properties in FOAF include givenName, family_name, and these names are irregularly ... named, and in need of cleanup.
----- /!\ Edit conflict! Your version: -----
-
FOAF allows URI identifiers to be used directly for people, groups etc.
-
in theory dc:identifier might also be applicable
-
FOAF uses RDFS/OWL schemas to indicate which other properties are uniquely identifying
4.1.2 Name The name or names by which the person is known, including alternative names.
-
FOAF provides the foaf:name property for plain text and xhtml (ruby markup etc) names
-
other properties in FOAF include givenName, family_name, and these names are irregularly ... named, and in need of cleanup.
----- /!\ End of edit conflict ----- 4.1.3 Dates May include date of the person's birth and/or death, or floruit dates (ie. an indication of the period in which the person was known to be active in a given field of endeavour). ----- /!\ Edit conflict! Other version: -----
-
FOAF doesn't currently include much by way of dates
-
See [
http://wiki.foaf-project.org/BirthdayIssue[birthday issue]] in FOAF wiki
-
FOAF doesn't yet define anything beyond [
http://xmlns.com/foaf/spec/#term_birthday[birthday]] (month day)
-
foaf:birthdate would be a natural addition
----- /!\ Edit conflict! Your version: -----
-
FOAF doesn't currently include much by way of dates
-
See [
http://wiki.foaf-project.org/BirthdayIssue[birthday issue]] in FOAF wiki
-
FOAF doesn't yet define anything beyond [
http://xmlns.com/foaf/spec/#term_birthday[birthday]] (month day)
-
foaf:birthdate would be a natural addition
----- /!\ End of edit conflict ----- 4.1.4 Title A word or phrase used to identify the rank, office, nobility, honour, etc. of the person. 4.1.5 Affiliation The name of the organization, institution, company, or other body with which the person was or is associated, or by whom the person was employed or contracted. 4.1.6 Location Information about the person’s principal area of residence over time. Context may be indicated by the use of appropriate qualifiers (for example: Lived in Canberra 1991-2005). 4.1.7 Email Email address or addresses currently assigned to the person at the time of the description. 4.1.8 Other Information Any additional significant information about the person that is needed to unambiguously identify that person.
4.2 Attributes of a Group
This document defines the attributes of a group as the following: legal number name jurisdiction location dates web site other information
4.2.1 Legal number Any official number assigned by a public authority that is used to identify the group. 4.2.2. Name Names by which the group is or was known. May include other forms of the name and changes of name over time. 4.2.3 Jurisdiction The legal name of the judicial and administrative entity which has jurisdiction over the territory in which the group operates. 4.2.4 Location The place from which the group operated. 4.2.5 Dates Dates indicating the period the group operated. May include such things as date of founding and dissolution, date of legal mandate establishing the group, etc. 4.2.6 Web Site The http address of the world wide web site operated by the group. 4.2.7 Other Information Any additional significant information about the group that is needed to unambiguously identify that group.
COMMENTS
[If you have any comments, views, opinions about the review please add them here]