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: [OASIS Issue Tracker] Commented: (OFFICE-2557) Part 1 OWL includenot resolvable

    [ http://tools.oasis-open.org/issues/browse/OFFICE-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18366#action_18366 ] 

Dennis Hamilton commented on OFFICE-2557:

I agree that the way the includes need to work is separate from the best-practice minimum requirement concerning resolvability of the *URIs* defined by that ontology file.

(Note that namespace is not used in that context and the practice is about RDF vocabularies, classes, and properties denoted by HTTP URIs, not XML Namespaces.)  

The minimum best practice would be that the URIs would also retrieve that OWL file and, in the case that there are fragment IDs in the URIs, it is still appropriate to retrieve the complete OWL file rather than some selected piece of it.

I cannot figure out how to resolve this with the OASIS requirement if we choose to consider that the base URI of all the OWL-defined URIs is also an XML Namespace URI.  I suppose one way would be to incorporate information that OASIS requires in an XML comment in the application/xml+rdf file that is returned.

It would be handier if, when content negotiation is not supported, that an XHTML page be delivered from the URI that is the defined prefix (everything but the fragment IDs), but that the OWL ontology be embedded as an RDF element early in that XHTML.  (For HTML, the approach is to embed the RDF element in a comment early in the HTML and there are Semantic Web processors that mine for RDF embedded in that way.)

This discussion should probably be in a different JIRA issue, such as OFFICE-2266 where the problem was raised in a Public Comment.  Or maybe OFFICE-2266 should be split into two parts so that we capture both aspects of that Public Comment in a clean way.


> Part 1 OWL include not resolvable
> ---------------------------------
>                 Key: OFFICE-2557
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2557
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Metadata
>    Affects Versions: ODF 1.2 Part 1 CD 4 
>         Environment: This issue applies to the Public Review version of the file OpenDocument-metadata-v1.2-cd4.owl
>            Reporter: Dennis Hamilton
>            Assignee: Michael Brauer
> This is a follow-up of OFFICE-2238: It reported an issue for the metadata package ontology (part 3), but actually is an issue with the metadata ontology (part 1). The following description has been taken from OFFICE-2238, but has been slightly modified.
> In lines 43-44 of the OWL Manifest Description file,
> <owl:Ontology rdf:about="http://docs.oasis-open.org/ns/office/1.2/meta/odf#";>
> 	<owl:imports rdf:resource="http://docs.oasis-open.org/ns/office/1.2/meta/pkg#"; />
> the rdf:resource attribute of the owl:imports element is not resolvable to an OWL file.   This is in fact the location of the OASIS Nameface Description file for the OpenDocument Package Metadata Manifest Ontology namespace http://docs.oasis-open.org/ns/office/1.2/meta/pkg# 
> Consequently, the  Protégé 3.4.1 ontology browser is unable to open the file OpenDocument-package-metadata-v1.2-cd1.owl, failing with message
>     "The system cannot find the ontology:
>     "http://docs.oasis-open.org/ns/office/1.2/meta/pkg#
> The <owl:imports> element requires a resource that is resolvable to an OWL description to be incorporated by reference.   A different location would appear to be required.  It may be necessary to work with OASIS to determine what that should be.  It is likely to be more like what is done for schemas, not namespaces. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

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