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

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

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


Subject: RE: [dita] Normative and non-normative references


 
We do say that that the DITA addressing model uses a fragment identifier
syntax that is expressly *not* Xpointer.

I would expect to see a non-normative reference to Xpointer to
unambiguously identify the standard which DITA expressly does not
implement.

That's simply my expectation, not necessarily a request.



http://www.w3.org/TR/WD-xptr


-sp



--------------------------------------------
seth park
information architect
Freescale Semiconductor, Inc.
seth.park@freescale.com
512.895.2463

-----Original Message-----
From: Eliot Kimber [mailto:ekimber@reallysi.com] 
Sent: Thursday, June 03, 2010 2:16 PM
To: Kristen James Eberlein; dita
Subject: Re: [dita] Normative and non-normative references

Standards that DITA depends on and does/should conform to:

- XML 1.x
- URIs
- XML namespaces
- XNI

DITA does not use, and has no normative or non-normative relationship to
XPointer or XLink (that is, those two standards are not relevant to any
likely use of DITA, unlike, say XSLT or XQuery, which are both commonly
used for implementing DITA processing and to which the spec makes
constructive non-normative reference).

Probably appropriate to have non-normative references to:

- XSLT
- XQuery
- CSS
- XHTML
- XSL-FO
- XTM/XLIFF (I think those are the right localization-related standards)
- IMS-QTI (Assessment markup, reflected in L&T design)
- Standards reflected in Machine Industry specializations

Cheers,

E.


On 6/3/10 11:26 AM, "Kristen James Eberlein"
<kris@eberleinconsulting.com>
wrote:

> Dear TC members:
> 
> In order to make the DITA 1.2 spec compliant with the OASIS template, 
> we need to add topics about normative and non-normative references. 
> Accordingly, I am asking active TC members to consider what we want to
add to the specification.
> Here is what we have currently:
> 
> Normative references:
> S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, 
> http://www.ietf.org/rfc/rfc2119.txt, IETF RFC 2119, March 1997.
> 
> Non-normative references:
> None
> 
> If you want to look at what sort of references other OASIS 
> specifications contain, you can view a complete list of OASIS 
> specification at http://www.oasis-open.org/specs/ . Be sure and scroll

> down to the table, so that you can make sure that you are looking at 
> specifications that have been approved recently (2008 or later).
> 
> Here are links directly to the normative reference sections in some 
> relevant other OASIS specs:
> Docbook: 
> http://docs.oasis-open.org/docbook/specs/docbook-5.0-spec-os.html#norm
> ative.re
> fs
> UIMA: 
> http://docs.oasis-open.org/uima/v1.0/os/uima-spec-os.html#_Toc20520103
> 5
> 
> Best,
> 
> Kris
> 
> Kristen James Eberlein
> Principal consultant, Eberlein Consulting Secretary, OASIS DITA 
> Technical Committee Charter member, OASIS DITA Adoption Committee 
> www.eberleinconsulting.com <http://www.eberleinconsulting.com/>
> +1 919 682-2290; keberlein (skype)

--
Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 512.554.9368
www.reallysi.com
www.rsuitecms.com


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 




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