I agree that most Schema.org markup would be generated on the fly from a
database, so I'm a bit unclear on what kind of "tool" we (OCLC) or someone
else is being asked to develop. Perhaps someone could spell it out for this
dense person? Thanks,
Roy


On Fri, Jan 17, 2014 at 12:02 PM, Karen Coyle <[log in to unmask]> wrote:

> Dave, my impression is that most schema.org code is being generated
> programmatically out of database-driven web sites. The list of tools (not
> many) is here:
>
> http://schema.rdfs.org/tools.html
>
> As OCLC is very involved in schema.org, it would make sense to encourage
> them to develop something. Looking at what they do today in WorldCat, the
> big advantage that they seem to have is that they can locate URIs for names
> (VIAF) and subjects (LCSH).
>
> kc
>
> On 1/17/14, 10:49 AM, Bigwood, David wrote:
>
>> Is there an easy-to-use tool for schema.org microdata? I was fond of the
>> OCLC NJ COinS tool, but it has gone. Anything of that ilk?
>>
>> Thanks,
>> Dave
>>
>> -----Original Message-----
>> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
>> Michael J. Giarlo
>> Sent: Friday, January 17, 2014 12:34 PM
>> To: [log in to unmask]
>> Subject: Re: [CODE4LIB] COinS metadata format support
>>
>> Chad,
>>
>> In that case, I wonder if you might get more mileage out of
>> schema.orgmicrodata instead of COinS.  There are undoubtedly more clients
>> out there that can make sense of HTML5 microdata than COinS, which is
>> really showing its age and is a niche technology.
>>
>> -Mike
>>
>>
>>
>> On Fri, Jan 17, 2014 at 10:25 AM, Chad Mills <[log in to unmask]>
>> wrote:
>>
>>  Jodi,
>>>
>>> No.  I am working with our repository resources which is an eclectic
>>> mixture of resource types.  I just want to simply embed our metadata
>>> in our search results and record displays for other tools to use.  It
>>> seems cheap and reasonable to do I just didn't want to limit this
>>> feature to only certain resource types.
>>>
>>> Best,
>>> Chad
>>>
>>>
>>> ----- Original Message -----
>>> From: "Jodi Schneider" <[log in to unmask]>
>>> To: [log in to unmask]
>>> Sent: Friday, January 17, 2014 12:54:43 PM
>>> Subject: Re: [CODE4LIB] COinS metadata format support
>>>
>>> Hi Chad,
>>>
>>> Are these subscription images/video/audio that libraries have? The
>>> original purpose of COinS, as I understand it, was to get people to
>>> subscription copies. Depending on what you're doing (i.e. the
>>> purpose/intended use) there might be a better standard these days.
>>>
>>> In case it helps there's more info here:
>>> http://ocoins.info/
>>> (though it looks like the generator isn't up any longer, maybe due to
>>> "OCLC New Jersey" hosting?)
>>>
>>> Hopefully you'll get some more helpful advice from others!
>>>
>>> -Jodi
>>>
>>>
>>>
>>>
>>> On Fri, Jan 17, 2014 at 5:36 PM, Chad Mills <[log in to unmask]>
>>> wrote:
>>>
>>>  I was able to easily find and create COinS for books and journals.
>>>> I started thinking about images, video, audio, etc.  I see
>>>> references to 'info:ofi/fmt:kev:mtx:unknown' as a rft_val_fmt value
>>>> some places.  I
>>>>
>>> would
>>>
>>>> assume if I went down that road the rft.genre would have a value of
>>>> 'unknown' as well.  Is there some other alternative I am missing
>>>> when handling other formats?
>>>>
>>>> Thanks!
>>>>
>>>> --
>>>> Chad Mills
>>>> Digital Library Architect
>>>> Ph: 848.932.5924
>>>> Fax: 848.932.1386
>>>> Cell: 732.309.8538
>>>>
>>>> Rutgers University Libraries
>>>> Scholarly Communication Center
>>>> Room 409D, Alexander Library
>>>> 169 College Avenue, New Brunswick, NJ 08901
>>>>
>>>> http://rucore.libraries.rutgers.edu/
>>>>
>>>>
> --
> Karen Coyle
> [log in to unmask] http://kcoyle.net
> m: 1-510-435-8234
> skype: kcoylenet
>