W3C home > Mailing lists > Public > public-lod@w3.org > April 2010

Re: attaching multiple licenses

From: Michael F Uschold <uschold@gmail.com>
Date: Wed, 14 Apr 2010 15:05:27 -0700
Message-ID: <t2z406b38b51004141505o781a85aej5e6fd42ab125780a@mail.gmail.com>
To: public-lod@w3.org
All,

I carefully examined this Dec 2009 thread on how to attach multiple licenses
for a resource in one rdf document.  Below is a concise summary. For
posterity, a more detailed description and
summary<http://ontologydesignpatterns.org/wiki/Community:Resource_multiple_attribution>has
been added to the Catalog
of Modeling Issues
<http://ontologydesignpatterns.org/wiki/Community:Main>in the Ontology
Design Pattern Wiki <http://ontologydesignpatterns.org/wiki> (see below for
additional information).

Note that the thread was about a particular example. I generalized it into a
modeling issue that could arise in different contexts and called it
"resource multiple attribution".

*Resource multiple
attribution<http://ontologydesignpatterns.org/wiki/Community:Resource_multiple_attribution>
*

*Issue*: How to attribute a single resource with two values of the same
property in one document

*Example: *publishing multiple licenses along with one rdf document.

*Source*: The thread: attaching multiple
licenses<http://lists.w3.org/Archives/Public/public-lod/2009Dec/0046.html>(
Markmail <http://markmail.org/thread/xu4hywhgexdmrzje>) in the W3C Linked
Open Data Discussion List. <http://lists.w3.org/Archives/Public/public-lod/>

*Conclusions:*

   1. One way is to use RDF reification, but this has some issues.
   2. OWL 2 has Axiom Annotations designed to do this.
   3. Caution: approaches often won't work unless the community adopts
   conventions and follows them.
   4. Principles:
      1. two documents about the same resource should serve the same data
      2. data should not be replicated all over the place


Feel free to add to the discussion in the wiki for this or any other
modeling issue.

*To  Contribute:*

   1. Visit *Ontology Design Patterns Wiki*<http://ontologydesignpatterns.org/>
   2. Click the "*How to
register*<http://ontologydesignpatterns.org/wiki/Odp:Register>" link
at
   lower left of the page; follow instructions to get a login name and
   password.
   3. Visit the "*Ontology Modeling
Issues<http://ontologydesignpatterns.org/wiki/Community:Main>
   *" page for further information, examples and instructions


Michael
======



More about the Catalog of Modeling
Issues<http://ontologydesignpatterns.org/wiki/Community:Main>
:

*WHY: *There is a ton of content about ontology modeling issues in
discussion list archives, BUT:

   1. the same issues get discussed over and over on different lists;
   2. the information you want is hard to find;
   3. if you do find a relevant thread,
      1. the content is raw and hard to digest;
      2. the summary you want is hard to find, even it is there.
   4. there is no agreed place to go to find out about modeling issues;
   5. it is often easier just to ask the question again, and the cycle
   continues.

We have created the * ontology modeling
issues<http://ontologydesignpatterns.org/wiki/Community:Main>
* section in the ODP Wiki <http://ontologydesignpatterns.org/wiki> to
address these problems.

*HOW:  *We envision the following steps in the evolution of a modeling
issue:

   1. Lively discussion happens on some mailing list.
   2. Post a summary to the list of the key points raised, including the
   pros and cons of proposed solutions.
   3. Post a modeling issue on the ODP Wiki (based on that summary).
   4. Post a note to any relevant discussion lists inviting them to
   contribute to the Wiki.
   5. Discuss and refine the issue further in the ODP Wiki
   6. Post major updates back to relevant discussion lists.

OR, start with step 3, and post the modeling issue directly on the ODP Wiki.


*Examples: *(from discussion lists)

   1. Proliferation of URIs, Managing
Coreference<http://ontologydesignpatterns.org/wiki/Community:Proliferation_of_URIs%2C_Managing_Coreference>
   2. Overloading owl
sameAs<http://ontologydesignpatterns.org/wiki/Community:GI_Overloading_owl_sameAs>
   3. Versioning and
URIs<http://ontologydesignpatterns.org/wiki/Community:Versioning_and_URIs>
   4. Representing
Species<http://ontologydesignpatterns.org/wiki/Community:epresenting_Species>
   5. Using SKOS
Concept<http://ontologydesignpatterns.org/wiki/Community:Using_SKOS_Concept>
   6. Resource multiple
attribution<http://ontologydesignpatterns.org/wiki/Community:Resource_multiple_attribution>
Received on Wednesday, 14 April 2010 22:06:03 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:26 UTC