Re: questions from the Vocabulary and Dataset editing.

Hi Jodi,

Trying to add to some of Karen's answers


> Quoting Jodi Schneider <jodi.schneider@deri.org>:
>
>> Here are my questions from the Vocabulary and Dataset editing:
>> http://www.w3.org/2005/Incubator/lld/wiki/index.php?title=Vocabulary_and_Dataset
>>
>> Suggestions & thoughts would be helpful -- these are the ones that stumped me.
>>


[...]


>> * "CKAN uses the concept of curated groups of data packages" -- given the special meaning of concept, is there another word that would suit here?
>
> More like "organizes" so "CKAN organizes data packages as groups that are curated by a community" ?


+1


>> * Have we decided to use "cases" as opposed to "use cases"?
>
> I could use a style guide on that!


I prefer to use "cases" for all the thing that we gathered at
http://www.w3.org/2005/Incubator/lld/wiki/UseCaseReport#Summary_of_individual_cases
As pointed out in the use case report, these are in fact not always true "use cases": we have examples of datasets, projects without a well identified usage scenario, etc.

What is closer to "use case" is what is extracted from the cases, and grouped into clusters at
http://www.w3.org/2005/Incubator/lld/wiki/UseCaseReport#Description_of_Use_Cases

The problem is that then the title of each sub-section is "use case" so the use case report does not follow my own convention (this section was precisely the point where I stopped my review, last time, in fact !)
I won't be nitpicking about removing "use" from everywhere it shouldn't apply-- I can't impose this on anyone! But I certainly would argue against putting it back when I've already transformed from "use cases" to 'cases" ;-)



>> CAPITALIZATION
>> * Should elements and values be capitalized?
>
> Don't think so.


+1. A good convention is to put them in a different font: courrier is good for this. But this is another of these roads that we maynot want to go down...

  
>> "a Subject element drawn from Dublin Core, and a value for Subject drawn from LCSH."
>> "name" from Friend of a Friend (FOAF)."
>> "including date modified and maintainer/curator elements drawn from Dublin Core."
>>
>>
>> LINKS/FURTHER INFO
>> * "The curators of these groups have arrived at a set of conventions for using the tagging facilities in CKAN to describe packages that are to be included. " -- if these are documented someplace, this would be a good place to link them, or say more. It's possible that the links below this are the documentation -- but that's not clear enough to me from the wording here.


It is the documentation indeed.



>> REPHRASING WOULD BE USEFUL
>> * "Beyond this analysis based on the Incubator Group cases, Library Linked Data community members should consider contributing to measuring the usage of element sets against more precise and up-to-date listings of datasets and value vocabularies"
>
> #1 - avoid the "-ing" form in English where possible. I don't know why, but it makes things (:-) not really an ING!) hard to read.
>
> However, I have no idea what is being measured here. Are we asking the LLD community to keep a list of datasets and value vocabs? To what purpose?


Well, people seem to like to have an idea on that kind of things. If just to pick more popular vocabularies. Or to recognize the ones that are real standards.


>> * "It is also apparent that linking to other data that do not have this central character is quite common."
>
> ??? no idea what is meant


I've directly picked Tom's sentences here. In the course of the discussion it was obvious that he was refering to the fact that there is linkage to datasets that are not central in the cloud (ie, they are not as strong "hubs" as the ones mentioned in the previous sentence). But I won't complain if you remove the sentence altogether, that point is not the strongest we want to make.


>> * "FOAF is a basic common-sense and widely used ontology for describing persons and other closely-related entities on the Web."
>
> I would never call ANY metadata vocabulary "common-sense" :-)
>
> FOAF is a widely used ontology for describing persons and their relationships to other Persons and to Web resources.


Fine with me.


>>
>> QUESTIONS ABOUT WORDING
>> * I'm not sure what this means:
>> "When publishing a new package, adding it to CKAN means that it is included in a frequently consulted list of packages. "
>
> I think it is merely that adding your package to CKAN gives it visibility through the CKAN service, which people consult to find datasets to use.


Yes.

Antoine  (not continuing, maybe Karen is doing it...)


>
> --- done up to here
> kc
>
>>
>> * I'm not sure what this means:
>> "Although ULAN not yet published as Linked Data per se, it does appears in the [http://www.w3.org/2005/Incubator/lld/wiki/Vocabulary_and_Dataset#VIAF_.28Virtual_International_Authority_File.29|VIAF]."
>>
>> * What does "their own" refer to here?
>> "In addition to the documentation made available on their own websites, the reader can view their content using generic ontology creation and visualization tools such as [http://protege.stanford.edu/ Protégé], the [http://owl.cs.manchester.ac.uk/browser/ Manchester ontology browser], [http://pellet.owldl.com/owlsight/ OWL Sight] or the [http://lode.sourceforge.net/ Live OWL Documentation Environment (LODE)] "
>>
>> ACRONYMS
>> * Does NACO stand for "name authority component"? Should we spell that out?
>> * Does TELplus stand for The European Library plus? Should we spell that out?
>> * What is the correct name for MARC21? MAchine-Readable Cataloging21?
>> * When should DC be abbreviated?
>> * Should API be spelled out?
>> * Does SKOS-XL have a long name?
>> * Ditto for OWL-DL?
>> * Does LOCAH have a long name?
>> * Does SPECTRUM have a long name?
>>
>> STRUCTURAL STUFF
>> * "As of the winter of 2011," "It contains terms in 24 languages (as of May 2011)."
>> Do we want to say "As of the date of this report"?
>>
>> * It's a little strange that the usage examples appear before the vocabs here:
>>
>> =====Preservation vocabularies from LoC=====
>>
>> * Usage examples: [[Use Case Digital Preservation]]
>>
>> ======[http://id.loc.gov/vocabulary/preservationEvents Preservation Events]======
>>
>> A concept scheme for the preservation events, i.e., actions performed on digital objects within a preservation repository.
>>
>> ======[http://id.loc.gov/vocabulary/preservationLevelRole Preservation Level Role]======
>>
>> A concept scheme for the preservation level roles, i.e., values that specify in what context a set of preservation options is applicable.
>>
>>
>>
>
>
>

Received on Thursday, 15 September 2011 16:09:09 UTC