RE: Proposing Article

The content-negotiation feature of Linked Data (aka "Cool URIs for the Semantic Web<http://www.w3.org/TR/cooluris/>") means that both humans and machines can do a useful HTTP GET from the same URI. Browser agents will get redirected to a human-friendly Web document, whereas semantic agents will get redirected to an RDF document. The former can be observed by resolving the DOI URI from a browser:

http://dx.doi.org/10.1080/01639374.2012.682254

Jeff

> -----Original Message-----
> From: Karen Coyle [mailto:kcoyle@kcoyle.net]
> Sent: Tuesday, January 14, 2014 1:40 PM
> To: Young,Jeff (OR); public-schemabibex@w3.org
> Subject: Re: Proposing Article
>
> Jeff - on many web sites that include DOIs, the DOI is there to be
> clicked on by humans. Will treating the DOI as a URI value to "sameAs"
> provide the clickable link as well? (Maybe an example would help.)
>
> kc
>
> On 1/14/14, 7:14 AM, Young,Jeff (OR) wrote:
> > I don't see how it can be a matter of interpretation. Here's the data
> that the DOI Linked Data delivers:
> >
> > http://bit.ly/1dsJhOF
> >
> > This makes it clear that the DOI URI identifies the article, not the
> content-negotiated description of the article (which is located at this
> URI):
> >
> > http://data.crossref.org/10.1080%2F01639374.2012.682254
> >
> > Jeff
> >
> >
> >> -----Original Message-----
> >> From: Karen Coyle [mailto:kcoyle@kcoyle.net]
> >> Sent: Tuesday, January 14, 2014 9:57 AM
> >> To: public-schemabibex@w3.org<mailto:public-schemabibex@w3.org>
> >> Subject: Re: Proposing Article
> >>
> >> I agree that it is a matter of interpretation, and that is because
> >> the DOI itself can be ambiguous.
> >>
> >> kc
> >>
> >> On 1/14/14, 6:48 AM, Wallis,Richard wrote:
> >>> Good point.
> >>>
> >>> I suppose the schema:url property would be expected to be a link to
> >>> the 'thing', whereas a doi url links you to a description of the
> >>> article which is the sameAs the description we are building in our
> >> examples.
> >>>
> >>> I presume in some cases that the URI would be the same (for the
> >>> article text and the description) in others it would be different.
> >>> Personally I would lean towards using schema:sameAs in at least
> some
> >> of our examples.
> >>>
> >>> ~Richard
> >>>
> >>> On 14 Jan 2014, at 14:13, Young,Jeff (OR) <jyoung@oclc.org
> >>> <mailto:jyoung@oclc.org>> wrote:
> >>>
> >>>> It seems to me that the DOI should be schema:sameAs rather than
> >>>> schema:url.
> >>>> I notice that the schema:author/publisher/about are treated as
> text
> >>>> strings sometimes and blank node typed entities in others. Perhaps
> >>>> this was intentional?
> >>>> Other than that, it looks good.
> >>>> Jeff
> >>>> *From:*Wallis,Richard [mailto:Richard.Wallis@oclc.org]
> >>>> *Sent:*Tuesday, January 14, 2014 6:51 AM
> >>>> *To:*public-schemabibex@w3.org <mailto:public-schemabibex@w3.org>
> >>>> *Subject:*Proposing Article
> >>>> Hi and Happy New Year!
> >>>> A simple one to start the conversation in 2014.
> >>>> Can I have +/- 1's for submitting the Article proposal
> >>>> <http://www.w3.org/community/schemabibex/wiki/Article> to the
> >>>> public-vocabs list.
> >>>> The only change I would make is to it's name which I think should
> >>>> be "Periodicals, Articles & Multi-volume Works"
> >>>> ~Richard
> >>>
> >>
> >> --
> >> Karen Coyle
> >> kcoyle@kcoyle.net<mailto:kcoyle@kcoyle.net> http://kcoyle.net
> >> m: 1-510-435-8234
> >> skype: kcoylenet
> >
> >
> >
>
> --
> Karen Coyle
> kcoyle@kcoyle.net<mailto:kcoyle@kcoyle.net> http://kcoyle.net
> m: 1-510-435-8234
> skype: kcoylenet