[Top] [All Lists]

[ontolog-forum] implementation issues for ontology URIs (right forum?)

To: ontolog-forum@xxxxxxxxxxxxxxxx
From: John Graybeal <graybeal@xxxxxxxxx>
Date: Fri, 3 Oct 2008 12:37:30 -0700
Message-id: <E596CEAF-8632-4C9E-AE7A-7664ACFC064C@xxxxxxxxx>
I have a few practical implementation approach issues when dealing  
with ontology term URIs.  Is this an appropriate forum for asking such  
questions, or if not, can you suggest a better one?  As my project is  
putting together on ontology repository, we are creating a mechanism  
to resolve URLs that are used for terms, so we are forced to flatten  
many philosophical and strategic questions into more mundane  
practicalities.    (01)

For example, the first issue is as follows:  My understanding is that  
fragment identifiers are used for RDF resources to indicate the term.  
But browsers are not built to handle/resolve/present RDF/OWL  
resources, or to display particular terms from them -- they will just  
download the URI resource as a file and that's that.  Can anyone point  
me to existing examples where the server can present the results of a  
URL like
so that the user sees a page in their browser on the term wind_speed  
(either exclusively, or at least at the top of the page)?    (02)

(It would be so nice if the URL could replace the '#' with a '/', but  
then it wouldn't be a nice RDF term URI, would it?)    (03)

I can imagine how to do this but I'd like to leverage any other effort  
in the community, if such exists.    (04)

John    (05)

John Graybeal   <mailto:graybeal@xxxxxxxxx>  -- 831-775-1956
Monterey Bay Aquarium Research Institute
Marine Metadata Interoperability Project: http://marinemetadata.org    (06)

Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/  
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/  
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/ 
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx    (07)

<Prev in Thread] Current Thread [Next in Thread>