Graphics

• [implemented] the XML/JSON datalinqs can now search multiple attributes or elements to return a node that matches all search criteria.  e.g. players<team=NY;jersey=10>
• [implemented] the XML datalinq types can search for children elements/attributes in a level of the tree by using "childname.field=%key%".  e.g. player<info.jersey=%num%>\name

team<player.uni=%jersey%>\player\rcv is trying to return the team based on the jersey number entered ("Return the team that has a player with jersey number X"). However, \player\ is always going to return the first listed player on either team. The query is "working", it just happens that player<1> for either team is defensive, so they don't have any receiving numbers that would be nested within \rcv.  

team<vh=%team%;player.uni=%jersey%>\player\rcv is doing the same thing; you're just additionally filtering by away/home ("Return the team that has a player with jersey number X, and has the vh designation of V/H").  In both cases the query is trying to return the first player listed on the team.

• [implemented] the XML/JSON datalinqs can now search multiple attributes or elements to return a node that matches all search criteria.  e.g. players<team=NY;jersey=10>
• [implemented] the XML datalinq types can search for children elements/attributes in a level of the tree by using "childname.field=%key%".  e.g. player<info.jersey=%num%>\name

team<player.uni=%jersey%>\player\rcv is trying to return the team based on the jersey number entered ("Return the team that has a player with jersey number X"). However, \player\ is always going to return the first listed player on either team. The query is "working", it just happens that player<1> for either team is defensive, so they don't have any receiving numbers that would be nested within \rcv.  

team<vh=%team%;player.uni=%jersey%>\player\rcv is doing the same thing; you're just additionally filtering by away/home ("Return the team that has a player with jersey number X, and has the vh designation of V/H").  In both cases the query is trying to return the first player listed on the team.

• [implemented] the XML/JSON datalinqs can now search multiple attributes or elements to return a node that matches all search criteria.  e.g. players<team=NY;jersey=10>
• [implemented] the XML datalinq types can search for children elements/attributes in a level of the tree by using "childname.field=%key%".  e.g. player<info.jersey=%num%>\name

team<player.uni=%jersey%>\player\rcv is trying to return the team based on the jersey number entered ("Return the team that has a player with jersey number X"). However, \player\ is always going to return the first listed player on either team. The query is "working", it just happens that player<1> for either team is defensive, so they don't have any receiving numbers that would be nested within \rcv.  

team<vh=%team%;player.uni=%jersey%>\player\rcv is doing the same thing; you're just additionally filtering by away/home ("Return the team that has a player with jersey number X, and has the vh designation of V/H").  In both cases the query is trying to return the first player listed on the team.

• [implemented] the XML/JSON datalinqs can now search multiple attributes or elements to return a node that matches all search criteria.  e.g. players<team=NY;jersey=10>
• [implemented] the XML datalinq types can search for children elements/attributes in a level of the tree by using "childname.field=%key%".  e.g. player<info.jersey=%num%>\name

team<player.uni=%jersey%>\player\rcv is trying to return the team based on the jersey number entered ("Return the team that has a player with jersey number X"). However, \player\ is always going to return the first listed player on either team. The query is "working", it just happens that player<1> for either team is defensive, so they don't have any receiving numbers that would be nested within \rcv.  

team<vh=%team%;player.uni=%jersey%>\player\rcv is doing the same thing; you're just additionally filtering by away/home ("Return the team that has a player with jersey number X, and has the vh designation of V/H").  In both cases the query is trying to return the first player listed on the team.

• [implemented] the XML/JSON datalinqs can now search multiple attributes or elements to return a node that matches all search criteria.  e.g. players<team=NY;jersey=10>
• [implemented] the XML datalinq types can search for children elements/attributes in a level of the tree by using "childname.field=%key%".  e.g. player<info.jersey=%num%>\name

team<player.uni=%jersey%>\player\rcv is trying to return the team based on the jersey number entered ("Return the team that has a player with jersey number X"). However, \player\ is always going to return the first listed player on either team. The query is "working", it just happens that player<1> for either team is defensive, so they don't have any receiving numbers that would be nested within \rcv.  

team<vh=%team%;player.uni=%jersey%>\player\rcv is doing the same thing; you're just additionally filtering by away/home ("Return the team that has a player with jersey number X, and has the vh designation of V/H").  In both cases the query is trying to return the first player listed on the team.

• [implemented] the XML/JSON datalinqs can now search multiple attributes or elements to return a node that matches all search criteria.  e.g. players<team=NY;jersey=10>
• [implemented] the XML datalinq types can search for children elements/attributes in a level of the tree by using "childname.field=%key%".  e.g. player<info.jersey=%num%>\name

team<player.uni=%jersey%>\player\rcv is trying to return the team based on the jersey number entered ("Return the team that has a player with jersey number X"). However, \player\ is always going to return the first listed player on either team. The query is "working", it just happens that player<1> for either team is defensive, so they don't have any receiving numbers that would be nested within \rcv.  

team<vh=%team%;player.uni=%jersey%>\player\rcv is doing the same thing; you're just additionally filtering by away/home ("Return the team that has a player with jersey number X, and has the vh designation of V/H").  In both cases the query is trying to return the first player listed on the team.