I’d probably be inclined to go with Bartek’s* namespace solution, but a general xpath solution is: //*[local-name()=’ProjectGuid’] **since Bartek’s answer has disappeared, I recommend Teun’s (which is actually more thorough)*
I think the question needs to be split into two parts – what is a triple and what makes an “RDF triple” so special? Firstly, a triple is, as most of the other commenters here have already pointed out, a statement in “subject/predicate/object” form – i.e. a statement linking one object (subject) to another object(object) … Read more
The basic point (as pointed out by Kev, above), is that the namespace URI is the important part of the namespace, rather than the namespace prefix, the prefix is an “arbitrary convenience” As for why you need a namespace manager, rather than there being some magic that works it out using the document, I can … Read more
They’re for allowing multiple markup languages to be combined, without having to worry about conflicts of element and attribute names. For example, look at any bit of XSLT code, and then think what would happen if you didn’t use namespaces and were trying to write an XSLT where the output has to contain “template”, “for-each”, … Read more
targetNamespace is an XML Schema “artifact”; its purpose: to indicate what particular XML namespace the schema file describes. xmlns – because the XML Schema is an XML document, it is then possible to define a default XML namespace for the XML file itself (this is what xmlns attribute does); the implications are multiple: authoring, and … Read more
Namespace related attributes in XML and XML Schema (XSD) xmlns is part of the W3C Namespaces in XML Recommendation: The prefix xmlns is used only to declare namespace bindings and is by definition bound to the namespace name http://www.w3.org/2000/xmlns/. In your example, it declares that http://maven.apache.org/POM/4.0.0 is the default namespace for the elements in your … Read more
@skyl practically provoked me to write this answer so please mind the redundancy. NCName stands for “non-colonized name”. NCName can be defined as an XML Schema regular expression [\i-[:]][\c-[:]]* …and what does that regex mean? \i and \c are multi-character escapes defined in XML Schema definition. http://www.w3.org/TR/xmlschema-2/#dt-ccesN \i is the escape for the set of … Read more
ElementFormDefault has nothing to do with namespace of the types in the schema, it’s about the namespaces of the elements in XML documents which comply with the schema. Here’s the relevent section of the spec: Element Declaration Schema Component Property {target namespace} Representation If form is present and its ·actual value· is qualified, or if … Read more
I also have the following xPath: /List/Fields/Field When I remove the xmlns from my XML the xPath works fine. When it’s in there my xPath finds nothing If you cannot register a namespace binding and cannot use (assuming the registered prefix is “x”): /x:List/x:Fields/x:Field then there is another way: /*[name()=’List’]/*[name()=’Fields’]/*[name()=’Field’]
Ahh… nevermind. It’s always the search after the question is posed that yields the answer. My object that is being serialized is obj and has already been defined. Adding an XMLSerializerNamespace with a single empty namespace to the collection does the trick. In VB like this: Dim xs As New XmlSerializer(GetType(cEmploymentDetail)) Dim ns As New … Read more