Re: Updated Schema Architypes Straw Man Proposal

On 17 May 2017 at 20:30, Roke, Elizabeth Russey <erussey@emory.edu> wrote:

> There’s a group of us working through the strawman here in the US


Great to hear!


> and we had a question about dates.  We’d like to have separate properties
> for the start date of the collection and the end date of an archival object
> rather than recording a string in temporalCoverage.


temporalCoverage <http://schema.org/temporalCoverage> can take DateTime and
URL as values in addition to a String.  Also as ArchiveCollection is a
sub-type of Collection, a sub-type of CreativeWork, you have three
properties in addition to *temporalCoverage* that can help:  *dateCreated*,
*dateModified*, *datePublished.*

We noticed that similar properties are available on CreativeWorkSeries.  We
> realize that ISO8601 allows us to record date ranges, but because archival
> management systems such as AToM allows us to record different types of
> dates, it may be difficult to consistently translate that data to and from
> the unified schema property.
>
>
I understand however the potential need for startDate & endDate, presumably
reflecting for example a collection of things about 18th Century fashion
that was created in a fixed period in the 1950s.   Do others concur?


> For what it’s worth, we are currently working on testing out the
> architypes model for both agent and collection level records, paying
> particular attention to DACS/ISAAR-CPF/ISAD(G) standards.  I should have
> more feedback in the next couple of weeks.
>

A great test - looking forward to the feedback

~Richard.

>
> Elizabeth
>
> ___________________________
> Elizabeth Russey Roke
> Digital Archivist
> Stuart A. Rose Manuscript, Archives, & Rare Book Library
> 404.727.2345 | erussey@emory.edu
>
>
>
>
> "The Stuart A. Rose Manuscript, Archives, & Rare Book Library collects and
> connects stories of human experience, promotes access and learning, and
> offers opportunities for dialogue for all wise hearts who seek knowledge.”
>
> Read the Rose Library blog: https://scholarblogs.emory.edu/marbl/
>
> Like the Rose Library on Facebook:  https://www.facebook.com/emorymarbl
>
> Follow the Rose Library on Twitter: https://twitter.com/EmoryRoseMARBL
>
> On 5/17/17, 9:52 AM, "Jane Stevenson" <Jane.Stevenson@jisc.ac.uk> wrote:
>
>     Hi Richard,
>
>     Great, thanks.
>
>     Just looking at the #Archive Collection for the time being:
>
>     1. Overall this tallies with my attempts - so I’m pleased that I seem
> to be going in the right direction.
>
>     2. can you just clarify for me the syntax re. the creator
>
>     schema:creator [ a schema:Person ;
>                 schema:name "Ronnie Barker" ;
>                 schema:sameAs <http://viaf.org/viaf/2676198> ] ;
>
>     You would do this every time you introduce Types?  So you might do it
> if you had, for example,  schema:publisher [a schema: Organization
>
>     3. just a small error really, but schema: identifier should be GB71
> THM/407  and not 407/8. You’ve put temporal coverage as 1954-2005 but its
> actually 1929-2005 for the whole collection.
>
>     4. hasPart
>
>     This particular collection has something like 500 parts (series, sub
> series, items). To my mind it is not generally going to be practical to use
> ‘has part’ in this way. I don’t think that matters, as I guess the
> principle is that you can indicate parts of a whole if you wish to. If I
> did want to do this, would it be:
>
>     schema:hasPart "https://archiveshub.jisc.ac.
> uk/data/gb71-thm/407/thm/407/1" ;
>     schema:hasPart "https://archiveshub.jisc.ac.
> uk/data/gb71-thm/407/thm/407/2” ;
>     schema:hasPart "https://archiveshub.jisc.ac.
> uk/data/gb71-thm/407/thm/407/3” ;
>     schema:hasPart "https://archiveshub.jisc.ac.
> uk/data/gb71-thm/407/thm/407/4” ;
>
>     I’m not yet sure of the benefits of listing 500 parts in this way.
>
>     5. extent
>
>     I definitely don’t want to include all the descriptive information
> within the schema.org representation, but I would tend to include the
> size of the collection as core information. At present I don’t think there
> is a property that we could use for this?
>
>     6. archiveHeld
>
>     Could this description include:
>
>     schema:archiveHeld "V&A Theatre and Performance Collections”
>
>     7. Language
>
>     From what I gather, to be compliant we would have to use ISO639-1
> codes? i.e. inLanguage: “EN” and not “eng”? All of our descriptions use ISO
> 639-2 so its a shame if we can't use them!
>
>     8. Aboutness
>
>     Finally, one of the things I assumed with schema.org is that it would
> be useful to include what the archive is about. So I thought about using
> e.g:
>
>     schema:about “Comedy”
>     schema:about “Television comedy"
>
>     I was thinking in terms of discoverability. What do you think about
> adding subjects/people/places in this way?
>
>     cheers
>     Jane
>
>
>
>
>     > On 16 May 2017, at 13:26, Richard Wallis <
> richard.wallis@dataliberate.com> wrote:
>     >
>     > Hi all,
>     >
>     > Following discussions on the mailing list and taking into account
> general evolution of the schema.org vocabulary over recent months, I have
> produced an updated version of the straw man initial proposal in the Wiki.
>     >
>     > ~Richard.
>     > Richard Wallis
>     > Founder, Data Liberate
>     > http://dataliberate.com
>     > Linkedin: http://www.linkedin.com/in/richardwallis
>     > Twitter: @rjw
>
>     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.
>
>
>
> ________________________________
>
> This e-mail message (including any attachments) is for the sole use of
> the intended recipient(s) and may contain confidential and privileged
> information. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution
> or copying of this message (including any attachments) is strictly
> prohibited.
>
> If you have received this message in error, please contact
> the sender by reply e-mail message and destroy all copies of the
> original message (including attachments).
>