Dear All,
So, following our last call, I had volunteered to "lead the way" on
using GitHub's issue tracker, and Tom started this thread on managing
issues, seeding the conversation with a comment about:
schema:about owl:equivalentProperty dct:subject
Tom says: "The relation should be subPropertyOf because the domain of
schema:about is more restricted."
Jon actually led the way describing the process below, and Kirsten
Jeude has already been opening issues in exactly the way envisioned. I
just added Tom's initial issue as issue #7:
https://github.com/dcmi/schema.org/issues/7
I followed Kristen's pattern of using the current text of a particular
triple as the issue's "title", and including some text & a line number
for the *first* line of the RDF-XML of that triple:
https://github.com/dcmi/schema.org/blob/master/mappings_schema.org.xml#L57
Currently users have to be logged in to comment. We *might* be able to
change that, but may not want to. What we need to decide next is how
these get "assigned" and eventually "resolved".
I hope this makes some sense, and my apologies for not getting to this sooner.
Thanks,
-Corey
On Thu, Mar 15, 2012 at 10:24 AM, Jon Phipps <[log in to unmask]> wrote:
> Karen, You can raise an issue here:
> https://github.com/dcmi/schema.org/issues
> ...which can then be discussed.
>
> Every line in every file has a URI, so in your issue, you can reference a
> specific line number in a specific file like so:
> https://github.com/dcmi/schema.org/blob/master/mappings_schema.org.xml#L108
>
> You can also reference a specific version of a file:
> https://github.com/dcmi/schema.org/commit/9f8467cd749954963dbd8f443f1e74439bebb67a#mappings_schema.org.xml
> ...and insert a comment directly:
> https://github.com/dcmi/schema.org/commit/9f8467cd749954963dbd8f443f1e74439bebb67a#commitcomment-1089282
>
> Versions for this particular file can be discovered and browsed here:
> https://github.com/dcmi/schema.org/commits/master
>
> You need to have a GitHub account to create issues or comments there.
>
> Jon
>
> I check email just a couple of times daily; to reach me sooner, click here:
> http://awayfind.com/jonphipps
>
>
> On Fri, Mar 9, 2012 at 11:40 AM, Karen Coyle <[log in to unmask]> wrote:
>>
>> I looked at github and didn't see where to make comments, so i'll do so
>> here and maybe someone can add it to github for me...
>>
>> re: schema:productionCompany rdfs:subPropertyOf dct:creator
>>
>> I would contact a film expert to determine if production companies are
>> seen as publishers/funders or as creators.
>>
>> kc
>>
>>
>> On 3/9/12 7:15 AM, Thomas Baker 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 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_Details
>>> [3] http://www.doodle.com/6qwfqtvcg6nk2ghr
>>>
>>
>> --
>> Karen Coyle
>> [log in to unmask] http://kcoyle.net
>> ph: 1-510-540-7596
>> m: 1-510-435-8234
>> skype: kcoylenet
>
>
--
Corey A Harper
Metadata Services Librarian
New York University Libraries
20 Cooper Square, 3rd Floor
New York, NY 10003-7112
212.998.2479
[log in to unmask]
|