Re: Discussion about previous proposal

Hi there,

Following on from Owen’s example, I thought I would share the basic idea I have (applying to ‘collection' only for now):

 Richard’s proposal:
 
#An ArchiveCollection <http://archive.example.com/boolarchive>    
a schema:ArchiveCollection;    
schema:name "The Boolean Papers Collection:;    
schema:creator "Sir Binary Boolean";    
schema:accessAndUse "Public view, in archive location, no image reproductions";    
schema:itemLocation <http://archive.example.com>.
 
Archives Hub example:  
 
#An ArchiveCollection < https://archiveshub.jisc.ac.uk/data/gb71-thm/407 >    
a schema:ArchiveCollection;    
schema:name Ronnie Barker Collection  
schema:dateCreated 1929/2005  
schema:creator Ronnie Barker    
schema:url https://archiveshub.jisc.ac.uk/data/gb71-thm/407

schema:about Television comedy
schema:about Radio comedy
schema:about Musical comedy
schema:mentions  Corbett,  Ronnie. ( 1930-2016)
schema: provider V&A Theatre and Performance Archive

Richard says: 

>> try to mark up your resources describing as fully as possible the attributes of those resources that would be of relevance and interest to search engines and the wider web

I had thought that really want we wanted was the core information and the aboutness, as I’m thinking of discovery.  I can’t see that I would want to map the whole description into schema.org….we’d start getting into creating a whole raft of properties, reflecting ISAD(G) and EAD and we would be including paragraphs of text. 

I thought that having subjects and names would be important, as for discovery these are the usual access points. 

Does this make any sense?  It is only a starting point  

cheers
Jane



> On 15 Feb 2017, at 11:06, Owen Stephens <owen@ostephens.com> wrote:
> 
> Thanks Dan and Richard,
> 
> I definitely felt when working on the bibextend schema.org group that working from existing representations on the web was a useful starting point.
> It probably helps with Adrian’s question as well - what can be done now.
> 
> To this end, I’ve put some HTML excerpts from the ArchivesHub (begging Adrian and Jane’s pardon!) on the wiki. I’ve done excerpts for Archive Collections, Sections, and Items both in search results lists and for the full view. This is at https://www.w3.org/community/architypes/wiki/Sample_Archives_HTML_excerpts

> 
> I’ve chosen examples from a particular Archive collection picked at random - so not sure if this is “typical” (maybe there isn’t a typical archive!)
> 
> I’m hoping that working from this kind of example might help ground this work in practical examples - if others want to add examples from other sources it would give us some good material to start looking at I think
> 
> Owen
> 
> Owen Stephens
> Owen Stephens Consulting
> Web: http://www.ostephens.com

> Email: owen@ostephens.com
> Telephone: 0121 288 6936
> 
>> On 14 Feb 2017, at 17:17, Richard Wallis <richard.wallis@dataliberate.com> wrote:
>> 
>> Thank you @danbri for asking the general schema.org-esque questions, it always places, such discussions as this, in contexts.
>> 
>> Also stepping back to first steps of this, and other Schema.org oriented community groups I have participated in and chair…..
>> 
>> Much of the structured data shared on the web, in about 30% of pages from millions of domains (a useful overview of a subset can be seen at webdatacommons.org), uses the Shema.org vocabulary.  That data is harvested in to the knowledge graph and similar technologies hosted by the search engines.
>> 
>> The search engines use this data to drive many services alongside providing SERPs, in fact up until recently it was explicitly stated by some that Schema.org data did not influence SERPs ratings. These other services however are believed to improved the visibility and discoverability on the web.
>> 
>> Much of the archival resource we are talking about does not have any such data openly published in a way that is easily consumed by the search engines, and is therefore invisible to them.  Consulting the advisory pages provided by the search engines, they advise including structured data using Schema.org in one of its supported serialisation.
>> 
>> Assuming the above leads you want to publish Schema.org data about your resources, the high level approach I have found from working with several community groups and on consultancy & training engagements is as follows:
>>  • Using Schema.org as it is currently described, try to mark up your resources describing as fully as possible the attributes of those resources that would be of relevance and interest to search engines and the wider web.
>> 
>>  • Identify what elements are missing from Schema that are preventing you from doing that.
>> 
>>  • Can these missing elements be overcome by enhancements to current terms - adjusting term definitions, recommending the use of a combination of types, expanding the domain and/or range of current properties.
>> 
>>  • Finally, propose new terms to extend the vocabulary.
>> ~Richard
>> 
>> Richard Wallis
>> Founder, Data Liberate
>> http://dataliberate.com

>> Linkedin: http://www.linkedin.com/in/richardwallis

>> Twitter: @rjw
>> 
>> On 14 February 2017 at 16:34, Dan Brickley <danbri@google.com> wrote:
>> Backing up a bit, and asking some general schema.org-esque questions:
>> 
>> Are there currently existing public sites that publish this sort of
>> structured information? Are there any examples of these (sites +
>> typical pages) collected?
>> 
>> Dan
>> 
> 

Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.

Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 2881024, VAT number GB 197 0632 86. The registered office is: One Castle Park, Tower Hill, Bristol BS2 0JA. T 0203 697 5800.

Received on Wednesday, 15 February 2017 16:37:48 UTC