XSDs: exemplos soltos

Transcription

1 XSDs: exemplos soltos <xsd:complextype name="tdetalhestcpd"> <xsd:complexcontent> <xsd:extension base="tdetalhesgeral"> «expande o tipo base» <xsd:sequence> <xsd:element name="composição" type="xsd:string"/> <xsd:element name="tamanho" type="ttamanho" minoccurs="0" maxoccurs="unbounded"/> «the default value for minoccurs and maxoccurs is 1» </xsd:sequence> </xsd:extension> </xsd:complexcontent> <xsd:attribute name="modelo" type="xsd:string" use="required" default="pt"/> «The attribute can only be present within complextype/content elements» «An attribute declaration associates a name with a type definition, which can be a built-in data type or a simpletype» «If the attribute is declared as global (its parent element is schema), this attribute is required on all elements in the schema» <xsd:simpletype name="valor"> <xsd:restriction base="xsd:float"> <xsd:pattern value="[0-9]+.[0-9]{2}"/> </xsd:restriction> </xsd:simpletype> «The following example declares a complextype, "shoesize", with its content defined as an integer data type and with a country attribute» <xsd:element name="shoesize"/> <xsd:simplecontent> <xsd:extension base="xsd:integer"> <xsd:attribute name="country" type="xsd:string"/> </xsd:extension> </xsd:simplecontent> «complextype and simpletype both define types.» «Complex types can have element descendants and attributes while simple types can't.» «Complex types can have simple or complex content.» «Types with complexcontent can contain child elements while those with simplecontent can only contain characters.»

2 «Forçando identificadores únicos» <xsd:element name="flights"> <xsd:sequence> <xsd:element ref="flight" maxoccurs="unbounded"/> </xsd:sequence> <xsd:element name="flight"> <xsd:attribute name="flightid" use="required" type="xsd:id"/> «flightid só validará com IDs distintos, iniciados por uma letra, tipo: [A-Za-z][A-Za-z0-9]*» <xsd:include schemalocation="relatoriosimpletypes.xsd"/> <xsd:import schemalocation="relatoriocomplextypes.xsd"/>

3 XSLs: exemplos soltos <xsl:template and Preco<4]"> <xsl:template «equivalente» <xsl:if <xsl:if test="artigo/preco > 20.00">... <xsl:when <xsl:value-of select='format-number(preco - (Preco/@Desconto), "#.00")'/> </xsl:when> <xsl:template match="@disponivel"> <xsl:choose> <xsl:when test="current()='sim'">temos</xsl:when> <xsl:when test=".='nao'">não temos</xsl:when> <xsl:otherwise>nim</xsl:otherwise> </xsl:choose> <xsl:if test="fn:string(data)"> «pressupõe: xmlns:fn= Final em: <xsl:value-of select="data"/> <xsl:if test="not(fn:string(data))"> Final em: indefinido! <xsl:if test="fn:number(preço) > fn:number(24.89)">... <xsl:template match="toalhas Gravatas Lenços"> Género: <xsl:value-of select="local-name()"/> «mostra nó associado com o match» <xsl:if test=".='toalha' or.='lenço'">... <xsl:attribute name="quantidade"> <xsl:value-of select="count(loja/catalogo/produto[@tipo='cachecol'])"/> </xsl:attribute> <xsl:stylesheet... xmlns:tns=" <xsl:template match="tns:casa/tns:quarto"> <xsl:value-of select="tns:dimensao"/> <xsl:text>, </xsl:text> «is used to write literal text to the output»

4 «Note: A variable is global if it's declared as a top-level element, and local if it's declared within a template.» «Note: Once you have set a variable's value, you cannot change or modify that value!» «Tip: You can add a value to a variable by the content of the <xsl:variable> element OR by the select attribute!» <xsl:variable name="limite" select="60"/> «global» <xsl:template match="/"> <xsl:variable name="page_descr"> «local» Vendas superiores a <xsl:copy-of select="$limite"/> euros </xsl:variable>... <xsl:for-each select="catalog/cd"> <xsl:sort select="." order="descending"/> <xsl:sort select="artist"/> <xsl:element name="qtdade_total"> <xsl:value-of select="sum(/v:empresa/v:venda/v:peca[@id_peca=current()]/v:qtdade_peca)"/> </xsl:element> «Parameters» «The param instruction is just like variable with one important difference: its value is only treated as a default value and can be overridden at runtime» <xsl:template name="titles"> <xsl:param name="headerelement">h4</xsl:param> <xsl:element name="{$headerelement}"> <xsl:apply-templates/> </xsl:element> <xsl:template match="chapter/title"> <xsl:call-template name="titles"> <xsl:with-param name="headerelement">h1</xsl:with-param> </xsl:call-template> <xsl:template match="section/title"> <xsl:call-template name="titles"> <xsl:with-param name="headerelement" select="'h2'"/> </xsl:call-template> <xsl:include href="xsl_precototal.xsl" /> <xsl:import href="xsl_html_header.xsl" />

5 <xsl:template match="*"/> <xsl:template match="text()"/> <!-- para que servem? --> o XSLT tem templates implícitas (built-in) : Aplicando templates num elemento processa os seus filhos Aplicando templates num nó texto resulta o seu valor Ou seja: Aplicando templates a um elemento que não tenha template explícita provoca o seu processamento e pode resultar no texto contido nele. Portanto: Podemos reescrever (override) templates implícitas para nós texto definindo uma template que faz NADA! Nada como experimentar: com e sem!