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] OASIS namespace design and resources

Hi Mary,

of course there is no problem in reusing the official short name of the 
committee. I thought it has been changed from 'office' to 'opendocument' 
and only resists in its previous form in the URL of the TC website. 
Michael might provide further information on this, when he is back from 

Would it not be useful in terms of modularity to allow a TC in the 
guidelines to create more than one namespace?
I wonder if there is a way to create more than one namespace by the 
guidelines, when using only a TC name and a versioned NS string.
For this modularity reason I suggested the path behind the versioned NS 
string for our ODF format (in our case the strings of the sub-committee 
name & layer).

Regarding the specific iteration string, it makes perfectly sense in an 
URL to resolve a versioned resource, providing different versions of a 
spec at the same time on the web.
On the other hand, versioning is not supported by the XML namespace 
standard. Changing the namespace URI even in one single character makes 
the XML elements using the changed namespace to complete different 
elements, totally unrecognizable to existing tools, which depend on XML 
techniques as XPATH and XSL.
Furthermore, even if a TC would expand its format XML vocabulary, it 
would reuse the existing namespace (with the old version substring) on 
new elements to avoid confusion on their users.
A versioning with "odf1.2" seems therefore sufficient.

Thank you very much for the namespace template.
Perhaps the link to the RDDL template could be added to the naming 
guidelines, along with links to existing implementations.

Finally did I understand correctly that the GRDDL XSLT stylesheet may be 
hosted at
And that it is possible for OASIS to resolve resources dependent on the 
user agent (according to [2]) for URL namespaces?

Thank you very much for your help, Mary.
Seems I got quite a bundle of x-mas wishes here..


Mary McRae wrote:
> Hi Svante,
>   There's one other problem - the official shortname of the committee is
> "office" rather than "opendocument". There is also no notion of
> "subcommittee" within approved technical work, since work can only be
> incorporated/approved by the main TC.
> We always return the namespace document. There are no physical resources
> allowed at/under the namespace location. All physical resources will reside
> at http://docs.oasis-open.org/office/v1.2/ ... I recommend further
> subdivision to identify the specific iteration (i.e. cd01, prd01, cs01, os,
> etc.)
> The namespace template document can be found here:
> http://docs.oasis-open.org/templates/rddl.html
> Let me know if you have further questions - I'm happy to help!
> Best regards,
> Mary
>> -----Original Message-----
>> From: Svante.Schubert@Sun.COM [mailto:Svante.Schubert@Sun.COM]
>> Sent: Monday, December 22, 2008 1:44 PM
>> To: Mary McRae; OASIS Office
>> Subject: [office] OASIS namespace design and resources
>> Hi Mary,
>> I got some question regarding the OASIS namespace design.
>> Background: In ODF 1.2 there will be two new namespaces, described by
>> the new ODF 1.2 OWL grammar and used in ODF documents in the new
>> manifest.rdf files.
>> After reviewing your latest version of OASIS guidelines [1], I realized
>> that my current proposal
>> http://docs.oasis-open.org/opendocument/meta/pkg#
>> http://docs.oasis-open.org/opendocument/meta/odf#
>> needs adaption to:
>> http://docs.oasis-open.org/ns/opendocument/1.2/meta/pkg#
>> http://docs.oasis-open.org/ns/opendocument/1.2/meta/odf#
>> Note:
>> Behind the version, the path includes the sub-committee name 'meta',
>> because the XML elements are RDF elements and exist only in an RDF/XML
>> file as elements and as well 'pkg' or 'odf' to destinguish two sets of
>> XML elements according to the two layers of ODF 1.2:
>> 1) the ODF package layer defining the zipped package reusable by XML
>> formats than ODF XML and
>> 2) the ODF document layer related to the ODF XML schema
>> Would the naming schema consist with the OASIS rules?
>> As the desired resource behind the new namespace URLs are RDF
>> vocabularies, I would like to ask, if OASIS is able to provide a
>> mechanism as described in "Best Practice Recipes for Publishing RDF
>> Vocabularies" [2]. This approach is used by RDF related sites (e.g.
>> [3]). The basic idea is that the server returns an RDF/XML file for RDF
>> crawlers, but some human readable resource (XHTML) in case of user
>> agents/browsers. In our case the XHTML file would be a RDDL namespace
>> document [4] [5].
>> If such a mechanism [2] is possible I will create two RDDL files for
>> the
>> namespaces, otherwise the OWL grammar would be more adequate than RDDL.
>> Finally I got one further resource to be accessed from an OASIS server:
>> The XSLT GRDDL file to map the RDFa and meta.xml to RDF/XML, that I
>> would suggest to locate at
>> http://docs.oasis-open.org/ns/opendocument/1.2/odf2rdf.xsl
>> Regards,
>> Svante
>> [1]
>> http://docs.oasis-
>> open.org/specGuidelines/namingGuidelines/resourceNaming.html#NamespaceD
>> esign
>> [2] http://www.w3.org/TR/swbp-vocab-pub/#recipe3
>> [3] http://xmlns.com/foaf/spec/
>> [4] http://www.w3.org/TR/webarch/#namespace-document
>> [5] http://www.rddl.org/

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