Search results

Jump to navigation Jump to search

Page title matches

  • ...an XML element definition. Two elements with the same name but different namespaces are considered two completely different entities (or should be) by software ...locally (that is, within the XML document) defining abbreviations to make namespaces easier for human eyes to track.
    6 KB (991 words) - 22:53, 21 June 2018

Page text matches

  • ...an XML element definition. Two elements with the same name but different namespaces are considered two completely different entities (or should be) by software ...locally (that is, within the XML document) defining abbreviations to make namespaces easier for human eyes to track.
    6 KB (991 words) - 22:53, 21 June 2018
  • * [[HHG to Namespaces in PDS4]]
    520 bytes (81 words) - 19:52, 3 August 2017
  • === Specify Namespaces and Prefixes === ...l namespaces, if you like. You can also change, add and delete additional namespaces and prefixes after you create the label, if needed (although changing a pre
    8 KB (1,274 words) - 20:08, 3 August 2017
  • ...standard and avoid re-defining the wheel. That is why, for example, the ''Namespaces in XML'' standard is not just part of the ''XML 1.0'' standard - because th == Namespaces in XML ==
    9 KB (1,388 words) - 22:17, 21 June 2018
  • == Namespaces == ...e of that namespace will be a URI (Uniform Resource Identifier). For PDS4 namespaces, URIs are in the form of a URL. PDS maintains the dictionary collection at
    15 KB (2,429 words) - 16:29, 8 April 2015
  • PDS-controlled namespaces will almost always be defined by a pair of related schema files: an XML Sch ...iers) are used to identify both namespaces and the files that define those namespaces. While it is easy, given the notational conventions described below, to co
    22 KB (3,638 words) - 23:50, 2 May 2019
  • ...they identify. (You can see examples of namespace referencing in [[HHG to Namespaces in PDS4]].) To turn the namespace reference into a reference to a specific Here's what the example from the [[HHG to Namespaces in PDS4]] might look like if you also include the ''schemaLocation'' attrib
    6 KB (943 words) - 22:58, 21 June 2018
  • The PDS and discipline namespaces employ a simple naming convention with these features: ...ons, but on the whole these are followed pretty consistently in the shared namespaces. There is no requirement that you use these conventions in your attribute
    10 KB (1,680 words) - 20:16, 30 July 2020
  • ...e top of a PDS4 XML label to reference the schemas that define the various namespaces that will be used. There are also potential variations in how this set-up ...reference because the XML Catalog file standard routinely used to convert namespaces to physical references necessarily returns a single value; it is not possib
    13 KB (2,180 words) - 14:58, 4 August 2017
  • So in the <code><Product_Collection></code> we see references to two namespaces: ...'', references mock-ups for three local namespaces. The schemas for these namespaces are included in the test file package in the ''Dictionaries/'' subdirectory
    8 KB (1,376 words) - 20:29, 3 August 2017
  • ''Any'' blocks are used within the shared PDS4 namespaces to pass validation control from one dictionary to another within a defined ...eviewers will require that they only reference attributes and classes from namespaces for which PDS administers the defining schema.
    14 KB (2,481 words) - 20:14, 30 July 2020
  • ...ve is triggered when a ''&lt;pds:Array_2D_Image&gt;'' tag is encountered. (Namespaces are defined in Schematron files as they are in the labels, so it is not nec
    4 KB (679 words) - 23:07, 21 June 2018
  • ...- These XML Schema files can be used to try out validation across multiple namespaces:
    5 KB (854 words) - 15:51, 3 August 2017
  • ...emonstrate how XML files can reference multiple schemas defining different namespaces.
    6 KB (935 words) - 14:16, 3 June 2015
  • ...re was (presumably still is) at least one registration authority to assign namespaces to insure that unique FPIs can be formulated by diverse organizations. So t ...use a <code>delegateURI</code> statement to trap references to all mission namespaces and pass them off to a different catalog file, while the rest fall through
    18 KB (2,948 words) - 20:27, 3 August 2017
  • The PDS shared namespaces follow this convention: If an attribute is required to appear in a class, b In PDS discipline namespaces, an attribute can either be optional or nillable, but is never both in the
    27 KB (4,289 words) - 19:55, 29 July 2020
  • ...the schemas on this page, serving the same functions for their respective namespaces as the above files do for the ''pds'' namespace.
    8 KB (1,343 words) - 15:56, 8 April 2015
  • ...plicated, depending on how you've set up your label to reference different namespaces. See the [[Using Local Dictionaries]] page on this wiki for gory details o
    11 KB (1,718 words) - 13:03, 31 July 2018
  • ...d ''xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"'' to the list of namespaces in the ''&lt;Product_*&gt;'' tag. See the "[[Schema Referencing in PDS4 Lab
    17 KB (2,705 words) - 15:29, 13 April 2022
  • ...you need to further subdivide your mission namespace into several smaller namespaces, then you may need to manually edit the namespace identifiers in your schem
    20 KB (3,247 words) - 20:12, 11 March 2018

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)