-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apresentação de referências XSL #38
Comments
Como está o XML neste trecho? |
Oi Robs, Está assim: Bom retorno!! Bjs, Javani Araujo Avenida Onze de Junho, 269 Em 30/07/2013 09:19, Roberta Takenaka escreveu:
http://www.scielo15.org/ |
É necessário adotar um padrão. Por favor, cheque a documentação do PMC como deve ficar no XML o elemento xref para intervalos. |
Há diferenças entre a JATS e a v3.0 como segue. Segue a sample da JATS. Já na versão 3.0 sence of the CCR5 mutation. Because some parameters (e.g., rate constants) are difficult to estimate based on available data, we implement an uncertainty analysis to assess the variability in the model outcomes caused by any inaccuracies in estimates of the parameter values with regard to the effect of the allelic mutation. For these analyses we use Latin hypercube sampling, as described in refs.52–56, Our uncertainty and sensitivity analyses focus on infectivity vs. duration of infectiousness. To this end, we assess the effects on the dynamics of the epidemic for a range of values of the parameters governing transmission and progression rates:βîıı^^,^^,k http://www.ncbi.nlm.nih.gov/pmc/articles/PMC56941/ Javani Araujo Avenida Onze de Junho, 269 Em 30/07/2013 09:38, Roberta Takenaka escreveu:
http://www.scielo15.org/ |
Javani Veja
"Tag ranges of cross references by including an for the first item, an en-dash (–), and an for the last item. PMC will display the range as tagged." Se assim, for feito, acredito que ficará correto no site, sem necessidade de corrigir a XSL. |
Nas citações em bloco, a apresentação das referências é duplicada.
The text was updated successfully, but these errors were encountered: