Re: Article Proposal

Hello again,

The microdata is now fixed in the following ways:

* corrected some itemtype values, which microdata requires to be full URLs
(unlike RDFa, which can use @vocab to avoid repetition)
* the items are linked together using isPartOf
* the same entities are described throughout (instead of six disjoint
entities), using @itemid

I used @itemid this time, since at least microdata parsers producing RDF
get the data right. Unfortunately, @itemid is (also) required to be a full
URL in microdata, and it is only allowed if both itemscope and itemtype are
also present. It's either that or using @itemref, which as I showed earlier
[1] is also somewhat cumbersome (it requires you to sprinkle in @id and
glue items together from disparate parts). Though if anyone more versed in
microdata can clean it up, please do.

I also added an RDFa version (which I find to be less verbose). I really
recommend to paste that into RDFa Play [2].

The examples are verified (using RDFLib) to produce the also added Turtle
example (minus some web page related details).

(Apart from considering the weight of the markup (which gets heavy with
this much granularity in once place), the Turtle is what I usually focus on
when I reason about the merits and flaws of various properties, types and
uses thereof.)

I also added a variant with less verbose precision (but using the same
properties of course): just an Article linked to a PeriodicalIssue
(skipping the volume and periodical). Notice that name, volumeNumber and
issn is used on the PeriodicalIssue, indicating that those are, scruffily,
"inherited" from the collections above. That's the kind of flexibility I
believe we're after.

.. By the way, why do we call this an Article proposal instead of a
Periodical proposal? Of course we go from an article to a periodical in
this example. But the focus in on periodical information, right? Something
which the Comics proposal could then build upon.

Cheers,
Niklas

[1]:
http://www.w3.org/community/schemabibex/wiki/Periodical_Article_minimal#article.2C_microdata
[2]: http://rdfa.info/play/


On Fri, Dec 13, 2013 at 12:13 AM, Niklas Lindström <lindstream@gmail.com>wrote:

> I'm on the example right now. Dan, shout out if you are too – otherwise
> I'll post an update within a couple of minutes.
>
> Cheers,
> Niklas
>
>
> On Fri, Dec 13, 2013 at 12:08 AM, Wallis,Richard <Richard.Wallis@oclc.org>wrote:
>
>>  I have applied most of what Dan has suggested, except for the example
>> changes - Dan would you take a look at those.
>>
>>  ~Richard
>>
>>  On 12 Dec 2013, at 21:49, Karen Coyle <kcoyle@kcoyle.net> wrote:
>>
>>
>>
>> On 12/12/13, 1:04 PM, Dan Scott wrote:
>>
>>
>> Also, per (c) in
>> http://lists.w3.org/Archives/Public/public-schemabibex/2013Dec/0077.html,
>> we need to change the definition of "pages" to better align with Bibo,
>> now that we have the "pageEnd" and "pageStart" properties. Something
>> like:
>>
>> 'Describes the pagination of works that do not run across
>> consecutively numbered pages and thus cannot be simply described by
>> pageStart and pageEnd (for example, "1-6, 9, 55" or "10-12, 46-49").'
>>
>>
>>
>> This is one case, but there are other cases as well, so it should say
>> that it carries any paginations that are not divided into first and last,
>> for whatever reason. That includes "123-456" when the software creating the
>> data does not parse these, and things like "xxi, 356p." or "pp. 34-45".
>>
>>
>>
>> I changed the example correctly
>>
>>
>> We still need to add itemprop="isPartOf" to connect the article to the
>> issue, volume, and periodical. Are we aiming for "article isPartOf
>> issue, which isPartOf volume, which isPartOf Periodical"?
>>
>>
>> IT's there, under "CreativeWork" - moving it from Collection (which we've
>> already proposed") to CW.
>>
>> kc
>>
>>
>>
>> Add more examples - I will copy in the Lord of the Rings multi-volume work
>> example from the Collection proposal
>>
>>
>> I would also suggest adding versions of the examples from
>> http://www.w3.org/community/schemabibex/wiki/Periodical which include
>> the standard schema.org introductory sentence of the example for
>> context, as well as the before / after schema.org markup.
>>
>> Let me know if you want me to make any of these changes.
>>
>> Thanks,
>> Dan
>>
>>
>>
>> --
>> Karen Coyle
>> kcoyle@kcoyle.net http://kcoyle.net
>> m: 1-510-435-8234
>> skype: kcoylenet
>>
>>
>>
>