W3C home > Mailing lists > Public > public-semweb-lifesci@w3.org > July 2013

Re: Linked Data Glossary is published!

From: KANZAKI Masahide <mkanzaki@gmail.com>
Date: Tue, 2 Jul 2013 11:18:54 +0900
Message-ID: <CAHQ1n3A-+hvA1672fq5TZetf5jRaVZPcChhkAt4JqZgNYaw7pQ@mail.gmail.com>
To: John Erickson <olyerickson@gmail.com>
Cc: Bernadette Hyland <bhyland@3roundstones.com>, W3C public GLD WG WG <public-gld-wg@w3.org>, Linked Data community <public-lod@w3.org>, egov-ig mailing list <public-egov-ig@w3.org>, HCLS <public-semweb-lifesci@w3.org>
Hello John, thanks for reply, very much appreciated.

2013/7/2 John Erickson <olyerickson@gmail.com>

> Thus, I think we should distinguish between "plain old XML" and Office
> Open XML/OOXML/OpenXML; based on my understanding and what I read <>
> OpenXML could be listed as an example three-star format.


Well, that's true. I hope this distinction will be incorporated into this
glossary, rather simply showing "XML" as 2-stars example (which is
misleading not only for me, but also for others around me).



> * I think the POINT is that the data should be published in a way
> suited for machine consumption. A format should NOT be considered
> "machine readable" simply because someone cooked up a hack on
> Scraperwiki for getting the data out of an otherwise opaque data dump
> on a site
>

Yes, it is desirable that data is published for machine "consumption" in
Linked Data space, though my point was that the term "Machine Readable" is
too general to be redefined for LD perspective.



> * The argument against having a separate term is simply that
> (arguably) the common case for publishing "machine readable" data *is*
> structured data, and adding the a special "structured" category merely
> confuses adopters.
> * The argument for a new term is, if the reason we want "machine
> readable data" is because we expect (and usually get) structured data,
> then we should specify that what we REALLY want is "machine readable
> structured data..." (and explain what that means)
>

Well, "machine readable" data is *not necessarily* structured in general,
so the second argument seems more reasonable, although I'm not arguing to
add separate term, rather, thinking it is not good idea to redefine term
"machine readable" just for a specific community.


Thank you very much for the discussion.

cheers,


-- 
@prefix : <http://www.kanzaki.com/ns/sig#> . <> :from [:name
"KANZAKI Masahide"; :nick "masaka"; :email "mkanzaki@gmail.com"].
Received on Tuesday, 2 July 2013 02:19:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:21:34 UTC