Regarding dcterms:creator/schema:author, there is a use case that I'm struggling with related to authority control. Here's how I currently have it modeled: <http://www.worldcat.org/oclc/673595> a scheme:Book; schema:name "Zen and the art of motorcycle maintenance: an inquiry into values" ; schema:author <http://viaf.org/viaf/78757182> . <http://viaf.org/viaf/78757182> a schema:Person ; schema:name "Pirsig, Robert M."; madsrdf:isIdentifiedByAuthority <http://id.loc.gov/authorities/names/n83231586> . <http://id.loc.gov/authorities/names/n83231586> a skos:Concept ; skos:inScheme <http://id.loc.gov/authorities/names> . The same issue exists for dcterms:subject/schema:about as well as several others. I'm not keen on using madsrdf:isIdentifiedByAuthority, but there is no inverse property for foaf:focus (or anything remotely similar in the schema.org vocabulary. I realize that "authority control" is probably beyond the interest of the schema.org vocabulary, but still I would like to reuse as much as possible. Jeff > -----Original Message----- > From: DCMI Architecture Forum [mailto:[log in to unmask]] > On Behalf Of Dan Brickley > Sent: Friday, March 09, 2012 10:31 AM > To: [log in to unmask] > Subject: Re: Schema.org Task Group - issue tracking - Doodle poll > > On 9 March 2012 16:15, Thomas Baker <[log in to unmask]> wrote: > > Dear all, > > > > The process of finalizing a set of mappings from DCMI Metadata Terms > to > > Schema.org has been stalled. I have been the bottleneck for this, > inasmuch I > > strongly feel we should have a well-functioning issue tracking and > publication > > workflow in place before taking final decisions on the mappings > themselves. We > > decided in January to use the issue tracker of Git, but I haven't > found the > > time to get my head around how this would work in practice. > > > > Specifically, we need a way to collect issues about individual > mappings in a > > structured way without trying to do this on the dc-architecture list. > After > > we decide on the mappings, we need a way to collect comments from the > public > > in a structured way so that we can mark mappings for reconsideration > in light > > of better understanding. > > > > Thanks to Jon, I have set up a Github account for DCMI [1], which Kai > and Corey > > have graciously volunteered to help maintain. Thanks to Jon again, > the draft > > mappings have been published in Git as well as on the wiki [2]. > > > > Corey has offered to lead the way on using Git for issue tracking by > entering > > some into [1] and explaining how our use of the tracker will work. I > have several > > issues of detail with the mappings, but here is one to get us > started: > > > > Proposed: > > schema:about owl:equivalentProperty dct:subject > > Tom says: > > The relation should be subPropertyOf because the domain of > schema:about is more restricted. > > I think that one's reasonable. I don't know of anyone yet using > schema.org's 'about' with string values e.g. subject classification > codes. Or links to SKOS concepts. The main use it to point to a > 'thing'. So if a travel guide is 'about' Paris, and we have a URI for > Paris, it would link to that. Or if a movie is 'about' a Person, the > value might be an embedded description of that person. This does > correspond to one of the two main uses of dc's 'subject'. At > schema.org we're pretty flexible so having string and > indirected-via-SKOS-concept values is probably OK too. > > Re domain, ... was a domain ever declared for dc terms properties? if > not, then yes, subproperty sounds about right. > > Where is a good place to collect concrete examples? > > Over in W3C wiki I just got an extension added so we can post markup > examples there, in case that's useful. See the proposals tracker for > http://www.w3.org/wiki/WebSchemas -> > http://www.w3.org/wiki/WebSchemas/SchemaDotOrgProposals > e.g. http://www.w3.org/wiki/WebSchemas/Singularity shows some markup > examples. If useful, feel free to put notes under WebSchemas/ area of > that wiki... > > cheers, > > Dan > > > > > I have posted a Doodle poll at [3] to find a time in early April for > a call, > > by which time we hopefully will have been able to sort out the > practicalities > > of issue tracking and publication on this list... > > > > Tom > > > > [1] https://github.com/dcmi > > [2] > http://wiki.dublincore.org/index.php/Schema.org_Alignment/Mappings_Deta > ils > > [3] http://www.doodle.com/6qwfqtvcg6nk2ghr > > > > -- > > Tom Baker <[log in to unmask]>