Re: (Updated) Camera Ontology

Yes, I think that's what legal RDF/OWL would look like.
I personally think that is less confusing than inventing a lot of new names.

Also note that the  <Lens> ... </Lens> is only used for specifying the
detailed properties of  a Lens.  Unless you want an anonymous Lens,
you can separate the details.  For example (I think this is legal RDF/OWL)
<Camera  aaa>
    <body  bbb />
    <lens  "HasselbladV" />
</Camera>
...
<Lens  "HasselbladV">
    <f-stop>...</f-stop>
    <focal-length>...</focal-length>
</Lens>

There is a tradeoff here -- between keeping Lens details with each Camera
instance (no searching to find details), and keeping Lens details separate
(shorter descriptions with no repetition and less chance for error).
============
Dick McCullough
knowledge := man do identify od existent done;
knowledge haspart proposition list;
----- Original Message -----
From: "Roger L. Costello" <costello@mitre.org>
To: <www-rdf-interest@w3.org>
Cc: "Costello,Roger L." <costello@mitre.org>
Sent: Thursday, April 17, 2003 7:52 AM
Subject: Re: (Updated) Camera Ontology

> "Richard H. McCullough" wrote:
> >
> > Notice that I used lower case for the "lens" Property/Part.
> > Your upper case "Lens" can be the Class that is the range of the "lens"
> > Property/Part.
> > Then, in my (your) example,
> > "ccc" ("Hasselblad_500V") is the value of the Property/Part "lens",
> > and "ccc" ("Hasselblad_500V") is an instance of the Class "Lens".
>
> Thanks Richard.  So, then an instance will look like this:
>
> <Camera>
>     <lens>
>         <Lens>
>             ...
>         </Lens>
>     </lens>
>     <body>
>         <Body>
>             ...
>         </Body>
>     </body>
> </Camera>
>
> So, a lens property contains a Lens class, and a body property contains
> a Body class.  Is this good practice?  I like it, I just thought that is
> might be confusing.  What's Best Practice?  /Roger

Received on Thursday, 17 April 2003 11:55:51 UTC