[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [tm-pubsubj] Jan 29 agenda: Documentation formats
* Steve Pepper I | | (c) We should describe best practices for both eventualities. For example, | we will say that the published subject indicator should explicitly state | which URL is to be used as the published subject identifier. (This is done | in the existing core.xtm, but not the country.xtm or language.xtm.) * Steve Pepper II | | and then I provided an example that flouted my own best practice: * Steve Pepper I | | <topic id="abugida"> | <subjectIdentity> | <subjectIndicatorRef | xlink:href="http://psi.ontopia.net/i18n/i18n.xtm#abugida"/> You did not, actually. The PS identifier is given right there. * Steve Pepper II | | I changed the example at the last moment and screwed things up. What I | think I would want to do is add the PSI (published subject identifier) as | another internal occurrence, in addition to the definition that is already | there: | | <occurrence> | <instanceOf> | <subjectIndicatorRef | xlink:href="http://psi.oasis-open.org/pubsubj/pubsubj.xtm#psi"/> | </instanceOf> | <resourceData>http://psi.ontopia.net/i18n/i18n.xtm#abugida</resourceData> | </occurrence> What's the point of duplicating the PS identifier like this, and turning the URI into a string like this? Software can be made to display the PS identifier if that's what we want. | This example is not fully thought through, but it does indicate the | direction of our thinking. s/our/my/ --Lars M.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC