W3C home > Mailing lists > Public > public-xg-lld@w3.org > January 2011

Re: Fitting "goals" in an introduction to use case section

From: Antoine Isaac <aisaac@few.vu.nl>
Date: Fri, 28 Jan 2011 17:21:30 +0100
Message-ID: <4D42ED0A.4030700@few.vu.nl>
To: Mark van Assem <mark@cs.vu.nl>
CC: public-xg-lld <public-xg-lld@w3.org>
Hi Mark,

Sure, it depends on how long you want the "summary". For something as short as the SKOS thingy, it would be indeed extremely hard!

Antoine


> Hi Antoine,
>
> It seems the goals can be useful as inspiration for the summaries, or as a checklist on what to include in the summaries! But for two-line summaries it might be hard to include all goals of a cluster, so I guess it should stay at just inspiration.
>
> Mark
>
> On 28/01/2011 0:14, Antoine Isaac wrote:
>> Hi,
>>
>> A small comment on:
>> ACTION: emma to put the Goals page content at the beginning of the use
>> case section [recorded in
>> http://www.w3.org/2005/Incubator/lld/minutes/2011/01/27-lld-minutes.html#action02]
>>
>>
>> Today I have suggested:
>>
>>> <Zakim> antoine, you wanted to discuss an "exec summary" on UCs?
>>> antoine: the page could be a good list of reminders for introducing
>>> the section on use cases. an executive summary style of what linked
>>> data would do in terms of applications.
>>> ... one sentence that digested the ideas.
>>> ... we could have something in the same spirit to make relationships
>>> and exploit them.
>>
>>
>> I was especially thinking of what was done for the abstract of the SKOS
>> Primer [1]. There are two sentences there that just capture everything
>> that SKOS allows to do:
>>
>>> In basic SKOS, conceptual resources (concepts) are identified with
>>> URIs, labeled with strings in one or more natural languages,
>>> documented with various types of note, semantically related to each
>>> other in informal hierarchies and association networks, and aggregated
>>> into concept schemes.
>>> In advanced SKOS, conceptual resources can be mapped across concept
>>> schemes and grouped into labeled or ordered collections. Relationships
>>> can be specified between concept labels. Finally, the SKOS vocabulary
>>> itself can be extended to suit the needs of particular communities of
>>> practice or combined with other modeling vocabularies.
>>
>>
>> We could have sthg similar for UCs, re-using the words used for the
>> goals. Like (please imagine a more beautiful style, I'm assembling this
>> in 30sec!):
>>
>> "LLD use cases typically use linked data technology to identify with
>> URIs resources of interest in the library domain and PUBLISHing data
>> about them in interoperable formats. [...] Many application scenarios
>> aim at making explicit EXISTING RELATIONSHIPS between these objects or
>> create NEW ones, potentially providing end users or data consumers with
>> brand new AGGREGATION objects [...]".
>>
>> Antoine
>>
>> [1] http://www.w3.org/TR/skos-primer/
>>
Received on Friday, 28 January 2011 16:19:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 28 January 2011 16:19:37 GMT