OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [office] Linking to Ontology Files


Rob (and Chet. Paul),

I'll look into this in conjunction with our own documented rules/guidelines/best-practices (Naming Directives) for handling of HTTP-scheme URIs that serve as identifiers.  In the general case, we do have a practice of resolving  under DNS+HTTP, so the HTTP status 404 you are seeing (for: http://docs.oasis-open.org/ns/office/1.2/meta/odf# ) is not in keeping with our practice.  I don't know how that one slipped through.

On the other hand, we have had little occasion to date to deal  with OWL/RDF in this kind of application (Regrep and PLCS TCs come to mind), so I'll need to look into the details in terms of options at server level.  Initially, I think a URI rewrite would work, and we have a front end controller to handle those, in the usual case (of namespaces).  The best practices for RDF/OWL may be a bit different than for other XML-based specs (e.g., as to the resolution target), and the Net Architecture best practices have indeed changed over the years.

We'll investigate and get back to you.  There may be as many as 16 files in /office/ ( .owl) so I can't yet promise that we can definitively fix everything, but for the OASIS Standard(s), we need to try.

I apologize for what looks like a slip-up on our end.

- Robin

====== Initial details

http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#ns-pathIdentifiersResolve
"Any HTTP scheme URI matching the base pattern of a declared XML namespace, when dereferenced, will resolve under DNS+HTTP to (fetch) the corresponding namespace document which documents the namespace and the specification which formally declares it. OASIS TC Administration maintains the namespace documents in consultation with TC specification editors"

See for investigation:

Open Document Format for Office Applications (OpenDocument) Version 1.2
Part 1: OpenDocument Schema
http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2-part1.html
 lists sub Declared XML namespaces:
http://docs.oasis-open.org/ns/office/1.2/meta/odf#

Ontology files are not resolvable via their name
https://tools.oasis-open.org/issues/browse/OFFICE-2633

Linking to Ontology Files
https://lists.oasis-open.org/archives/office/201403/msg00013.html

Open Document Format TC meeting minutes 2014-03-17
https://lists.oasis-open.org/archives/office/201403/msg00012.html
Michael noted that this is related to an older JIRA issue:  https://tools.oasis-open.org/issues/browse/OFFICE-2633 
-Rob will check with Chet on what is possible on the OASIS side to make this URI resolve per W3C recommendations. 

Best Practice Recipes for Publishing RDF Vocabularies
W3C Working Group Note 28 August 2008
http://www.w3.org/TR/swbp-vocab-pub/
  - Recipe 1. Minimal configuration for a 'hash namespace'
    http://www.w3.org/TR/swbp-vocab-pub/#recipe1
  - Vocabularies that use a 'hash namespace'
    http://www.w3.org/TR/swbp-vocab-pub/#hash

"Both hash namespaces and slash namespaces are supported within the architecture of the Web. However, certain behaviors are required of the Web server that differ between these two choices. Because both the requests received by the server and the responses returned by the server are different in each case, the mechanics of setting up an HTTP server to satisfy some or all of the requirements given below also differ, and hence these two cases are treated separately."




On Fri, Mar 28, 2014 at 10:51 AM, <robert_weir@us.ibm.com> wrote:
Hi Chet,

Something that came up in discussion at our last ODF TC call, in response to a note on the comment list.

Take a look at ODF 1.2 Part 1, the cover sheet, in the "Declared XML namespaces" block:  http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2-part1.html

There is a hyperlink for http://docs.oasis-open.org/ns/office/1.2/meta/odf# that does not resolve.

The W3C in their "Best Practice Recipes for Publishing RDF Vocabularies" (http://www.w3.org/TR/swbp-vocab-pub/ ) says:

<quote>
Minimum Requirements
M1. The 'authoritative' RDF description of a vocabulary, class, or property denoted by an HTTP URI can be obtained by dereferencing the URI of that vocabulary, class, or property.
</quote>

So, by that recommendation the namespace URI should resolve to the approved OWL ontology file:  http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-metadata.owl

There is a parallel issue on the cover ODF 1.2 Part 3.

What's the OASIS practice for this?

-Rob



--
Robin Cover
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email: robin@oasis-open.org
Staff bio: http://www.oasis-open.org/people/staff/robin-cover
Cover Pages: http://xml.coverpages.org/
Newsletter: http://xml.coverpages.org/newsletterArchive.html
Tel: +1 972-296-1783


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]